public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c++/60779] New: -fcx-fortran-rules ignored when using -flto
@ 2014-04-07 17:02 dturnbull at gmail dot com
  2014-04-07 17:04 ` [Bug c++/60779] " pinskia at gcc dot gnu.org
                   ` (3 more replies)
  0 siblings, 4 replies; 5+ messages in thread
From: dturnbull at gmail dot com @ 2014-04-07 17:02 UTC (permalink / raw)
  To: gcc-bugs

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60779

            Bug ID: 60779
           Summary: -fcx-fortran-rules ignored when using -flto
           Product: gcc
           Version: 4.9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: dturnbull at gmail dot com

Using the following test code on g++-4.9 (GCC) 4.9.0 20140330

if (isnan((complex<float>(1,0) / complex<float>(0,0)).real())) {
    cout << "Fortran rules: \n";
} else {
    cout << "ISO rules: \n";
}

The -fcx-fortran-rules option behaves as expected. The test code indicates
Fortran rules are being used and performance indicates the NaN checking is
indeed disabled.

When enabling both -fcx-fortran-rules and -flto the test code indicates ISO
rules are being used and performance is identical to compiling without
-fcx-fortran-rules.

This happens in both the C and C++ compilers.


^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Bug c++/60779] -fcx-fortran-rules ignored when using -flto
  2014-04-07 17:02 [Bug c++/60779] New: -fcx-fortran-rules ignored when using -flto dturnbull at gmail dot com
@ 2014-04-07 17:04 ` pinskia at gcc dot gnu.org
  2014-04-07 17:11 ` dturnbull at gmail dot com
                   ` (2 subsequent siblings)
  3 siblings, 0 replies; 5+ messages in thread
From: pinskia at gcc dot gnu.org @ 2014-04-07 17:04 UTC (permalink / raw)
  To: gcc-bugs

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60779

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Can you provide the extra command line you used?


^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Bug c++/60779] -fcx-fortran-rules ignored when using -flto
  2014-04-07 17:02 [Bug c++/60779] New: -fcx-fortran-rules ignored when using -flto dturnbull at gmail dot com
  2014-04-07 17:04 ` [Bug c++/60779] " pinskia at gcc dot gnu.org
@ 2014-04-07 17:11 ` dturnbull at gmail dot com
  2014-04-08  8:48 ` [Bug lto/60779] " rguenth at gcc dot gnu.org
  2014-04-08  9:52 ` rguenth at gcc dot gnu.org
  3 siblings, 0 replies; 5+ messages in thread
From: dturnbull at gmail dot com @ 2014-04-07 17:11 UTC (permalink / raw)
  To: gcc-bugs

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60779

David Turnbull <dturnbull at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |INVALID

--- Comment #2 from David Turnbull <dturnbull at gmail dot com> ---
Sorry. My bad. Closing. Makefile bug :(


^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Bug lto/60779] -fcx-fortran-rules ignored when using -flto
  2014-04-07 17:02 [Bug c++/60779] New: -fcx-fortran-rules ignored when using -flto dturnbull at gmail dot com
  2014-04-07 17:04 ` [Bug c++/60779] " pinskia at gcc dot gnu.org
  2014-04-07 17:11 ` dturnbull at gmail dot com
@ 2014-04-08  8:48 ` rguenth at gcc dot gnu.org
  2014-04-08  9:52 ` rguenth at gcc dot gnu.org
  3 siblings, 0 replies; 5+ messages in thread
From: rguenth at gcc dot gnu.org @ 2014-04-08  8:48 UTC (permalink / raw)
  To: gcc-bugs

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60779

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |lto, missed-optimization
             Status|RESOLVED                    |ASSIGNED
   Last reconfirmed|                            |2014-04-08
          Component|c++                         |lto
         Resolution|INVALID                     |---
           Assignee|unassigned at gcc dot gnu.org      |rguenth at gcc dot gnu.org
     Ever confirmed|0                           |1

--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
Well, LTO unconditionally sets flag_complex_method to 2 currently.  It does not
yet conservatively merge TU choices and complex lowering happens too late.

Thus, confirmed and mine.


^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Bug lto/60779] -fcx-fortran-rules ignored when using -flto
  2014-04-07 17:02 [Bug c++/60779] New: -fcx-fortran-rules ignored when using -flto dturnbull at gmail dot com
                   ` (2 preceding siblings ...)
  2014-04-08  8:48 ` [Bug lto/60779] " rguenth at gcc dot gnu.org
@ 2014-04-08  9:52 ` rguenth at gcc dot gnu.org
  3 siblings, 0 replies; 5+ messages in thread
From: rguenth at gcc dot gnu.org @ 2014-04-08  9:52 UTC (permalink / raw)
  To: gcc-bugs

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60779

--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
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).


^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2014-04-08  9:52 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-04-07 17:02 [Bug c++/60779] New: -fcx-fortran-rules ignored when using -flto dturnbull at gmail dot com
2014-04-07 17:04 ` [Bug c++/60779] " pinskia at gcc dot gnu.org
2014-04-07 17:11 ` dturnbull at gmail dot com
2014-04-08  8:48 ` [Bug lto/60779] " rguenth at gcc dot gnu.org
2014-04-08  9:52 ` rguenth at gcc dot gnu.org

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).