[Bug tree-optimization/48475] New: gcc.dg/initpri3.c FAILs with -flto -O2 --param partial-inlining-entry-probability=100

[Bug tree-optimization/48475] New: gcc.dg/initpri3.c FAILs with -flto -O2 --param partial-inlining-entry-probability=100

[zsojka at seznam dot cz]

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

           Summary: gcc.dg/initpri3.c FAILs with -flto -O2 --param
                    partial-inlining-entry-probability=100
           Product: gcc
           Version: 4.7.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: zsojka@seznam.cz
              Host: x86_64-pc-linux-gnu
            Target: x86_64-pc-linux-gnu


Created attachment 23892
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=23892
preprocessed source

Output:
$ gcc -flto -O2 --param partial-inlining-entry-probability=100 initpri3.i
$ ./a.out
Aborted

(gdb) bt
#0  0x00007ffff7a98c05 in raise () from /lib/libc.so.6
#1  0x00007ffff7a9a5b6 in abort () from /lib/libc.so.6
#2  0x0000000000400657 in main () at
/mnt/svn/gcc-trunk/gcc/testsuite/gcc.dg/initpri3.c:62

Tested revisions:
r171998 - fail
4.6 r171597 - fail
4.5 - doesn't know --param partial-inlining-entry-probability

[Bug lto/48475] gcc.dg/initpri3.c FAILs with -flto -O2 --param partial-inlining-entry-probability=100

[pinskia at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48475

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |marxin at gcc dot gnu.org
      Known to work|                            |4.7.3
          Component|tree-optimization           |lto

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
It seems to be working in GCC 4.7.3+.
I can reproduce the failure in GCC 4.6.4.

Someone would need to go back and figure out what fixed this if it is a still
latent bug or not.