public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug target/22382] New: cris-axis-linux-gnu cross: gfortran.fortran-torture/execute/common.f90 -O2 host difference?
@ 2005-07-09  0:35 hp at gcc dot gnu dot org
  2005-07-09  0:41 ` [Bug target/22382] " hp at gcc dot gnu dot org
  0 siblings, 1 reply; 2+ messages in thread
From: hp at gcc dot gnu dot org @ 2005-07-09  0:35 UTC (permalink / raw)
  To: gcc-bugs

With LAST_UPDATED "Thu Jun 30 14:21:26 UTC 2005",
gfortran.fortran-torture/execute/common.f90 fails:
FAIL: gfortran.fortran-torture/execute/common.f90 execution,  -O1
FAIL: gfortran.fortran-torture/execute/common.f90 execution,  -O2
FAIL: gfortran.fortran-torture/execute/common.f90 execution,  -O2
-fomit-frame-pointer -finline-functions
FAIL: gfortran.fortran-torture/execute/common.f90 execution,  -O2
-fno-repack-arrays
FAIL: gfortran.fortran-torture/execute/common.f90 execution,  -Os

whereas cross from i686-pc-linux-gnu with "Mon Jul  4 10:24:52 UTC 2005"
shows no fail for that case.  (Results from previous tests has been
flushed.)  In constrast, the "nearby" in-pack.f90 fails with -Os
on both hosts, regardless of -fpic:y options.

Lots of apples and oranges regarding source dates, but this is just
a public note that I need to investigate, particularly since (1) it
does not fail *at all* when adding (just) -fpic, (2) a target patch
will cause it to fail when -O2 -fpic.  It also fails baseline with
-mno-gotplt -fPIC and -mno-gotplt *without* -fpic/-fPIC!

Also marked "target" so nobody thinks I'm implying there's a bug elsewhere,
like in libgfortran.  I suspect a "64-bit bug" lurking somewhere.

For the record, random people wanting to repeat this, need to install
the glibc from cris-dist-1.62 (developer.axis.com, use the rpm, the dpkg,
or follow the instructions and gcc in that distribution to compile it)
and use --prefix=/usr/local/cris with the current tree to be able to repeat
the observations noted above.

-- 
           Summary: cris-axis-linux-gnu cross: gfortran.fortran-
                    torture/execute/common.f90 -O2 host difference?
           Product: gcc
           Version: 4.1.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: target
        AssignedTo: hp at gcc dot gnu dot org
        ReportedBy: hp at gcc dot gnu dot org
                CC: gcc-bugs at gcc dot gnu dot org
  GCC host triplet: x86_64-unknown-linux-gnu
GCC target triplet: cris-axis-linux-gnu


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


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

* [Bug target/22382] cris-axis-linux-gnu cross: gfortran.fortran-torture/execute/common.f90 -O2 host difference?
  2005-07-09  0:35 [Bug target/22382] New: cris-axis-linux-gnu cross: gfortran.fortran-torture/execute/common.f90 -O2 host difference? hp at gcc dot gnu dot org
@ 2005-07-09  0:41 ` hp at gcc dot gnu dot org
  0 siblings, 0 replies; 2+ messages in thread
From: hp at gcc dot gnu dot org @ 2005-07-09  0:41 UTC (permalink / raw)
  To: gcc-bugs



-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |ASSIGNED
     Ever Confirmed|                            |1
   Last reconfirmed|0000-00-00 00:00:00         |2005-07-09 00:35:00
               date|                            |


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


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

end of thread, other threads:[~2005-07-09  0:35 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2005-07-09  0:35 [Bug target/22382] New: cris-axis-linux-gnu cross: gfortran.fortran-torture/execute/common.f90 -O2 host difference? hp at gcc dot gnu dot org
2005-07-09  0:41 ` [Bug target/22382] " hp at gcc dot gnu dot 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).