[Bug tree-optimization/53922] [4.6 Regression] VRP: semantic conflict between range_includes_zero_p and value_inside_range
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53922 Jakub Jelinek jakub at gcc dot gnu.org changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution||FIXED Target Milestone|4.6.4 |4.7.2 --- Comment #14 from Jakub Jelinek jakub at gcc dot gnu.org 2013-04-12 16:27:41 UTC --- The 4.6 branch has been closed, fixed in GCC 4.7.2.
[Bug tree-optimization/53922] [4.6 Regression] VRP: semantic conflict between range_includes_zero_p and value_inside_range
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53922 David Fang fang at csl dot cornell.edu changed: What|Removed |Added CC||fang at csl dot cornell.edu --- Comment #13 from David Fang fang at csl dot cornell.edu 2012-09-27 21:28:16 UTC --- http://gcc.gnu.org/ml/gcc-testresults/2012-09/msg02736.html (4.7.2 test-results) shows similar failures on powerpc-darwin8
[Bug tree-optimization/53922] [4.6 Regression] VRP: semantic conflict between range_includes_zero_p and value_inside_range
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53922 --- Comment #12 from Dominique d'Humieres dominiq at lps dot ens.fr 2012-09-23 10:32:11 UTC --- The new gcc.dg/torture/pr53922.c testcase fails on darwin. ... This is pr54083.
[Bug tree-optimization/53922] [4.6 Regression] VRP: semantic conflict between range_includes_zero_p and value_inside_range
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53922 Jack Howarth howarth at nitro dot med.uc.edu changed: What|Removed |Added CC||howarth at nitro dot ||med.uc.edu --- Comment #11 from Jack Howarth howarth at nitro dot med.uc.edu 2012-09-22 23:46:14 UTC --- The new gcc.dg/torture/pr53922.c testcase fails on darwin. The darwin linker developer had the following comments... --- This is a feature that darwin does not support: int y(int a) __attribute__ ((weak)); This is a function prototype marked weak. In the linux world, this tells the static linker it is ok for there to be no definition +of the function y - just make a PLT entry as if it was found is some shared object, and somehow it will be magically found at +runtime. Darwin uses two-level namespace where the static linker needs to record in which dylib (shared object) each undefined symbol was +found. If the symbol cannot be found at static link time, it is an error. You can make this example work by adding -undefined dynamic_lookup to the link line which tells the static linker to assume any unresolved symbol will be magically found at runtime. - Adding... /* { dg-options -Wl,-undefined,dynamic_lookup { target *-*-darwin* } } */ is confirmed to allow all of the gcc.dg/torture/pr53922.c tests to pass at -m32/-m64 on x86_64-apple-darwin11.
[Bug tree-optimization/53922] [4.6 Regression] VRP: semantic conflict between range_includes_zero_p and value_inside_range
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53922 Richard Guenther rguenth at gcc dot gnu.org changed: What|Removed |Added Known to work||4.7.2 Summary|[4.6/4.7 Regression] VRP: |[4.6 Regression] VRP: |semantic conflict between |semantic conflict between |range_includes_zero_p and |range_includes_zero_p and |value_inside_range |value_inside_range --- Comment #10 from Richard Guenther rguenth at gcc dot gnu.org 2012-09-07 13:05:53 UTC --- And 4.7.