[Bug lto/60779] -fcx-fortran-rules ignored when using -flto

2025-04-28 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60779 Richard Biener changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug lto/60779] -fcx-fortran-rules ignored when using -flto

2025-04-28 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60779 --- Comment #7 from GCC Commits --- The master branch has been updated by Richard Biener : https://gcc.gnu.org/g:e543eaa671d40868575385360d13ef37d87fb2a0 commit r16-188-ge543eaa671d40868575385360d13ef37d87fb2a0 Author: Richard Biener Date: T

[Bug lto/60779] -fcx-fortran-rules ignored when using -flto

2016-07-25 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60779 --- Comment #6 from Richard Biener --- Yes. But only -fcx-limited-range is looked at by the inliner, -fcx-fortran-rules is not (via flag_complex_method). And flag_complex_method is _not_ saved per-function, only -fcx-limited-range or -fcx-fortr

[Bug lto/60779] -fcx-fortran-rules ignored when using -flto

2016-07-21 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60779 --- Comment #5 from Andrew Pinski --- Hasn't this been fixed by using the optimize attribute infrastructure for LTO now?

[Bug lto/60779] -fcx-fortran-rules ignored when using -flto

2014-04-08 Thread rguenth at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60779 --- Comment #4 from Richard Biener --- Note this applies to the case where you don't specify any -fcx-* flag on the linker command-line (or on any of the input TUs, but merging conflicting flags there doesn't work).

[Bug lto/60779] -fcx-fortran-rules ignored when using -flto

2014-04-08 Thread rguenth at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60779 Richard Biener changed: What|Removed |Added Keywords||lto, missed-optimization Sta