aboutsummaryrefslogtreecommitdiff
path: root/gcc/value-range.cc
diff options
context:
space:
mode:
authorAldy Hernandez <aldyh@redhat.com>2022-08-31 14:41:29 +0200
committerAldy Hernandez <aldyh@redhat.com>2022-09-01 13:19:08 +0200
commit0550e306d4b5aaf7bdb6e908d265dbaa63344271 (patch)
treee61be0d9aa862d268cae28a2f69c4bcf8f89aed0 /gcc/value-range.cc
parente9b0dd2afe7a9e8a3033340dfa26ec606930eef5 (diff)
downloadgcc-0550e306d4b5aaf7bdb6e908d265dbaa63344271.zip
gcc-0550e306d4b5aaf7bdb6e908d265dbaa63344271.tar.gz
gcc-0550e306d4b5aaf7bdb6e908d265dbaa63344271.tar.bz2
Implement ranger folder for __builtin_signbit.
Now that we keep track of the signbit, we can use it to fold __builtin_signbit. I am assuming I don't have try too hard to get the actual signbit number and 1 will do. Especially, since we're inconsistent in trunk whether we fold the builtin or whether we calculate it at runtime. abulafia:~$ cat a.c float nzero = -0.0; main(){ printf("0x%x\n", __builtin_signbit(-0.0)); printf("0x%x\n", __builtin_signbit(nzero)); } abulafia:~$ gcc a.c -w && ./a.out 0x1 0x80000000 It is amazing that we've been failing to fold something as simple as this: if (x > 5.0) num = __builtin_signbit (x); It does the right thing now :-P. gcc/ChangeLog: * gimple-range-fold.cc (fold_using_range::range_of_builtin_int_call): Add case for CFN_BUILT_IN_SIGNBIT. gcc/testsuite/ChangeLog: * gcc.dg/tree-ssa/vrp-float-signbit-1.c: New test.
Diffstat (limited to 'gcc/value-range.cc')
0 files changed, 0 insertions, 0 deletions