[Bug fortran/53778] New: bad code (delivering NaN instead of proper result) with -foptimize-sibling-calls

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53778 Bug #: 53778 Summary: bad code (delivering NaN instead of proper result) with -foptimize-sibling-calls Classification: Unclassified Product: gcc Version: 4.6.3 Status

[Bug fortran/53778] bad code (delivering NaN instead of proper result) with -foptimize-sibling-calls

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53778 --- Comment #2 from Thomas Orgis 2012-06-27 08:58:57 UTC --- Created attachment 27710 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=27710 tarball with complete source to reproduce the issue Ok, then, I feared as much. After taking too much

[Bug fortran/53778] bad code (delivering NaN instead of proper result) with -foptimize-sibling-calls

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53778 --- Comment #3 from Thomas Orgis 2012-06-27 09:03:25 UTC --- ... and not to forget profiles.f90 ... that module links the perturbation in dat_init_density() to the wind in dat_init_wind(). Changes in there along with moving perturb to using those

[Bug fortran/53778] bad code (delivering NaN instead of proper result) with -foptimize-sibling-calls

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53778 Thomas Orgis changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|

[Bug fortran/53778] bad code (delivering NaN instead of proper result) with -foptimize-sibling-calls

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53778 --- Comment #7 from Thomas Orgis 2012-06-27 21:34:43 UTC --- Eh, it must have been -finit-real=nan ... so only wrong in one way;-)

[Bug fortran/49103] New: local variables exchange values / wrong code with -O3

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49103 Summary: local variables exchange values / wrong code with -O3 Product: gcc Version: 4.6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assign