[Bug c/31741] New: dfp tests failing - internal compiler error

[Bug c/31741] New: dfp tests failing - internal compiler error

[rob1weld at aol dot com]

It looks like ALL the DFP tests are failing.

This is an early notification. I will e-mail full "make -i check" results after
all the tests have completed. There are also a few errors in "C" we did not
have
last week.

                === gcc Summary ===

# of expected passes            42626
# of unexpected failures        124      <--- Ouch, was only a few before
# of expected failures          116
# of unresolved testcases       87
# of untested testcases         28
# of unsupported tests          287


#/opt/gcc-4_2-build# gcc/xgcc -v
Using built-in specs.
Target: i686-pc-linux-gnu
Configured with: ../gcc-4_2-branch/configure --verbose
--enable-languages=c,ada,c++,fortran,java,objc,obj-c++ --with-tune=athlon-xp
--prefix=/usr --enable-objc-gc --enable-concept-checks --disable-multilib
--with-gxx-include-dir=/usr/include/c++/4.2 --enable-libstdcxx-debug
--enable-static --enable-shared --enable-initfini-array --enable-__cxa_atexit
--enable-threads=posix --enable-version-specific-runtime-libs --enable-libssp
--enable-libmudflap --enable-libgomp --disable-werror --enable-nls
--with-included-gettext --enable-decimal-float --with-long-double-128
--enable-debug --disable-sjlj-exceptions --enable-java-gc=boehm --with-x
--x-includes=/usr/X11R6/include --x-libraries=/usr/X11R6/lib
--enable-java-awt=gtk,xlib --enable-gtk-cairo --enable-qt-peer --enable-xmlj
--enable-gconf-peer --enable-tool-wrappers --with-gjdoc
--enable-portable-native-sync --enable-libgcj-multifile --with-stabs
--enable-hash-synchronization --enable-gc-debug --enable-interpreter
--with-system-zlib --enable-libada --with-tls --with-cpu=athlon-xp
--with-arch=athlon-xp --enable-checking
Thread model: posix
gcc version 4.2.0 20070427 (prerelease)

(Note: you'll need a lot of new libraries to actually compile with all those
options enabled - you might try just using --enable-decimal-float (possibly
--with-long-double-128 too)).


Here is a _small_ portion of gcc.log :

PASS: gcc.dg/compat/scalar-by-value-dfp c_compat_main_tst.o compile
Executing on host: /opt/gcc-4_2-build/gcc/xgcc -B/opt/gcc-4_2-build/gcc/   
-fno-show-column -c  -o c_compat_x_tst.o /r$
/root/downloads/gcc-4_2-branch/gcc/testsuite/gcc.dg/compat/scalar-by-value-dfp_x.c:
In function 'checkd128':
/root/downloads/gcc-4_2-branch/gcc/testsuite/gcc.dg/compat/scalar-by-value-dfp_x.c:149:
error: unrecognizable insn:
(insn 24 23 25 3 (set (subreg:TI (reg:TD 68) 0)
        (subreg:TI (const_double:TD 0 [0x0] 123.456 [N/A]) 0)) -1 (nil)
    (insn_list:REG_LIBCALL 32 (nil)))
/root/downloads/gcc-4_2-branch/gcc/testsuite/gcc.dg/compat/scalar-by-value-dfp_x.c:149:
internal compiler error: in ext$
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
compiler exited with status 1
output is:
/root/downloads/gcc-4_2-branch/gcc/testsuite/gcc.dg/compat/scalar-by-value-dfp_x.c:
In function 'checkd128':
/root/downloads/gcc-4_2-branch/gcc/testsuite/gcc.dg/compat/scalar-by-value-dfp_x.c:149:
error: unrecognizable insn:
(insn 24 23 25 3 (set (subreg:TI (reg:TD 68) 0)
        (subreg:TI (const_double:TD 0 [0x0] 123.456 [N/A]) 0)) -1 (nil)
    (insn_list:REG_LIBCALL 32 (nil)))
/root/downloads/gcc-4_2-branch/gcc/testsuite/gcc.dg/compat/scalar-by-value-dfp_x.c:149:
internal compiler error: in ext$
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
...(many more)...


-- 
           Summary: dfp tests failing - internal compiler error
           Product: gcc
           Version: 4.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: rob1weld at aol dot com
 GCC build triplet: i686-pc-linux-gnu
  GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu


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

[Bug c/31741] dfp tests failing - internal compiler error

[rob1weld at aol dot com]

------- Comment #1 from rob1weld at aol dot com  2007-04-29 11:25 -------
I completed all tests. Current SVN builds on Linux "OK", but has "internal
compiler error" when build with "_similar_" (but not "same") options on Cygwin
platform (when it gets to libstdc++-v3).

Full results at this link:
http://gcc.gnu.org/ml/gcc-testresults/2007-04/msg01490.html


-- 


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

[Bug c/31741] dfp tests failing - internal compiler error

[rob1weld at aol dot com]

------- Comment #2 from rob1weld at aol dot com  2007-05-01 10:19 -------
Successfully _forced_ the compile on Cygwin platform and posted a seperate
report about the segmentation fault issue at:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31761

After running "make -i check" on Cygwin compile I also got many dfp errors.

Due to the use of the _exact_ same options for Cygwin as I used for Linux and
_forcing_ the compile to complete I got an enormous number of error messages in
other parts (not dfp) of the compile which made the "make check report" HUGE -
so it was not posted.

Suffice to say that the dfp errors occur on both platforms (when compiled with
these ./configure options).


-- 


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

[Bug c/31741] dfp tests failing - internal compiler error

[rob1weld at aol dot com]

------- Comment #3 from rob1weld at aol dot com  2007-05-03 10:00 -------
Another test results report for i686-pc-linux-gnu (4.2.0 20070501):
http://gcc.gnu.org/ml/gcc-testresults/2007-05/msg00135.html

Nearly all options are enabled. Nearly all tests pass. A few have ZERO errors!
(hurray). DFP still broken. :(

Contains a decent explanation of the many libraries needed to compile GCC.


-- 


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

[Bug c/31741] dfp tests failing - internal compiler error

[rob1weld at aol dot com]

------- Comment #4 from rob1weld at aol dot com  2007-05-05 18:55 -------
Results for Cygwin are very similar (for DFP) - other areas have differing
errors:

Results for 4.2.0 20070501 (prerelease) testsuite on i686-pc-cygwin
http://gcc.gnu.org/ml/gcc-testresults/2007-05/msg00258.html


May I suggest that this problem (on two platforms) needs to be independantly
confirmed. With this fixed we we have very few errors remaining in 4.2.0.


-- 


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

[Bug c/31741] dfp tests failing - internal compiler error

[rob1weld at aol dot com]

------- Comment #5 from rob1weld at aol dot com  2007-05-13 05:47 -------
Thanks - the most recent SVN has fewer DFP errors.

If we _really_ don't want DFP on any platform except PowerPC then we should
change ./configure for it to be prohibited. I can't see why it could not be
supported on other (modern) uP's. I'm in favour of keeping it for the Intel
chips.

Getting an "internal compiler error" is clearly not desired - supported or not.


-- 


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

[Bug c/31741] dfp tests failing - internal compiler error

[ubizjak at gmail dot com]

-- 

ubizjak at gmail dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  BugsThisDependsOn|                            |32065
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1
   Last reconfirmed|0000-00-00 00:00:00         |2007-05-26 09:07:55
               date|                            |
Bug 31741 depends on bug 32065, which changed state.

Bug 32065 Summary: Many dfp testsuite failures for -msse targets
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32065

           What    |Old Value                   |New Value
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED

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

[Bug c/31741] dfp tests failing - internal compiler error

[rob1weld at aol dot com]

------- Comment #6 from rob1weld at aol dot com  2007-06-09 03:52 -------
Changing From / To:

"Known to work: (Blank)" and "Known to fail: 4.2.0 4.2.1 4.3.0"

"Known to work: 4.3.0" and "Known to fail: 4.2.0 4.2.1"

Since 4.3.0 works on i686-pc-linux-gnu perfectly - No reason to believe 4.3.0
works on i686-pc-cygwin very well.


-- 

rob1weld at aol dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
      Known to fail|4.2.0 4.2.1 4.3.0           |4.2.0 4.2.1
      Known to work|                            |4.3.0


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

[Bug target/31741] dfp tests failing - internal compiler error

[rob1weld at aol dot com]

------- Comment #7 from rob1weld at aol dot com  2007-06-25 05:19 -------
Almost always works well. There _are_ days when there is one or two check test
that fail; but not like before when _most_ tests failed. FIXED.


-- 

rob1weld at aol dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED


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