[Bug regression/50999] New: [4.7 Regression]: g++.dg/lto/20081109 execute -O2 -flto -flto-partition=1to1 -fno-use-linker-plugin

[hp at gcc dot gnu.org]

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

             Bug #: 50999
           Summary: [4.7 Regression]: g++.dg/lto/20081109 execute -O2
                    -flto -flto-partition=1to1 -fno-use-linker-plugin
    Classification: Unclassified
           Product: gcc
           Version: 4.7.0
            Status: UNCONFIRMED
          Keywords: wrong-code
          Severity: normal
          Priority: P3
         Component: regression
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: hp@gcc.gnu.org
                CC: amodra@gcc.gnu.org, rguenth@gcc.gnu.org
              Host: x86_64-unknown-linux-gnu
            Target: cris-axis-elf


This test previously passed, now it fails.
Revision r180827 introduced this regression.  (Formally, triaged to either
r180826 or r180827 but trivially only the latter could be the cause.  Further,
the regression was introduced while masked by fallout from the libgcc move,
fixed by revision r180854.)
Since then, up till and including at least r181026, it fails as follows:

...
Running /tmp/hpautotest-gcc1/gcc/gcc/testsuite/g++.dg/lto/lto.exp ...
FAIL: g++.dg/lto/20081109 cp_lto_20081109_0.o-cp_lto_20081109_1.o execute -O2
-flto -flto-partition=1to1 -fno-use-linker-plugin 
...

The messages in g++.log are similar:
...
Executing on host:
/tmp/hpautotest-gcc1/cris-elf/gccobj/gcc/testsuite/g++/../../g++
-B/tmp/hpautotest-gcc1/cris-elf/gccobj/gcc/testsuite/g++/../../
cp_lto_20081109_0.o cp_lto_20081109_1.o   -nostdinc++
-I/tmp/hpautotest-gcc1/cris-elf/gccobj/cris-elf/libstdc++-v3/include/cris-elf
-I/tmp/hpautotest-gcc1/cris-elf/gccobj/cris-elf/libstdc++-v3/include
-I/tmp/hpautotest-gcc1/gcc/libstdc++-v3/libsupc++
-I/tmp/hpautotest-gcc1/gcc/libstdc++-v3/include/backward
-I/tmp/hpautotest-gcc1/gcc/libstdc++-v3/testsuite/util -fmessage-length=0 -O2
-flto -flto-partition=1to1 -fno-use-linker-plugin      -isystem
/tmp/hpautotest-gcc1/cris-elf/gccobj/cris-elf/./newlib/targ-include -isystem
/tmp/hpautotest-gcc1/gcc/newlib/libc/include
-B/tmp/hpautotest-gcc1/cris-elf/gccobj/cris-elf/./libgloss/cris/
-L/tmp/hpautotest-gcc1/cris-elf/gccobj/cris-elf/./libgloss/cris
-L/tmp/hpautotest-gcc1/gcc/libgloss/cris 
-B/tmp/hpautotest-gcc1/cris-elf/gccobj/cris-elf/./newlib/
-L/tmp/hpautotest-gcc1/cris-elf/gccobj/cris-elf/./newlib -sim3  
-L/tmp/hpautotest-gcc1/cris-elf/gccobj/cris-elf/./libstdc++-v3/src/.libs 
-B/tmp/hpautotest-gcc1/cris-elf/gccobj/cris-elf/./libstdc++-v3/src/.libs     
-o g++-dg-lto-20081109-31.exe    (timeout = 300)
PASS: g++.dg/lto/20081109 cp_lto_20081109_0.o-cp_lto_20081109_1.o link, -O2
-flto -flto-partition=1to1 -fno-use-linker-plugin 
terminate called after throwing an instance of 'int'

program stopped with signal 6.

FAIL: g++.dg/lto/20081109 cp_lto_20081109_0.o-cp_lto_20081109_1.o execute -O2
-flto -flto-partition=1to1 -fno-use-linker-plugin 
...

Author of suspect patch in revision range CC:ed.

Also CC:ed Alan Modra, as he might have observed the same for powerpc-linux,
mentioned on IRC.  That's supported by
<http://gcc.gnu.org/ml/gcc-testresults/2011-11/msg00620.html> for -m32,
compared to <http://gcc.gnu.org/ml/gcc-testresults/2011-11/msg00153.html>.  A
quick look in g++.log would help verify whether it's an identical (the same)
regression.