[Bug c/38666] New: internal compiler error: Segmentation fault

[Bug c/38666] New: internal compiler error: Segmentation fault

[sergstesh at yahoo dot com]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 3177 bytes --]

I've encountered this problem while compiling a mostly autogenerated "C" file.

Here is the screen session:

"
~/AFSWD/install/gcc-4.3.2/binsh/gcc -v -save-temps -O1 -march=native
-mtune=native -I/home/sergei/GenericBinauralFFTW/C -Wall gcc_bug.c -o gcc_bug
-lm
Using built-in specs.
Target: i686-pc-linux-gnu
Configured with: /home/sergei/AFSWD/build/gcc-4.3.2.src/configure
--enable-bootstrap --enable-threads
--enable-languages=c,c++,fortran,objc,obj-c++,treelang
--with-mpfr=/home/sergei/AFSWD/install/mpfr-2.3.2
--with-gmp=/home/sergei/AFSWD/install/gmp-4.2.2
--prefix=/home/sergei/AFSWD/install/gcc-4.3.2
Thread model: posix
gcc version 4.3.2 (GCC)
COLLECT_GCC_OPTIONS='-v' '-save-temps' '-O1'  
'-I/home/sergei/GenericBinauralFFTW/C' '-Wall' '-o' 'gcc_bug'
 /home/sergei/AFSWD/install/gcc-4.3.2/libexec/gcc/i686-pc-linux-gnu/4.3.2/cc1
-E -quiet -v -I/home/sergei/GenericBinauralFFTW/C gcc_bug.c -march=k8-sse3
-mcx16 -msahf --param l1-cache-size=64 --param l1-cache-line-size=64 -mtune=k8
-Wall -O1 -fpch-preprocess -o gcc_bug.i
ignoring nonexistent directory
"/home/sergei/AFSWD/install/gcc-4.3.2/lib/gcc/i686-pc-linux-gnu/4.3.2/../../../../i686-pc-linux-gnu/include"
#include "..." search starts here:
#include <...> search starts here:
 /home/sergei/GenericBinauralFFTW/C
 /usr/local/include
 /home/sergei/AFSWD/install/gcc-4.3.2/include
 /home/sergei/AFSWD/install/gcc-4.3.2/lib/gcc/i686-pc-linux-gnu/4.3.2/include

/home/sergei/AFSWD/install/gcc-4.3.2/lib/gcc/i686-pc-linux-gnu/4.3.2/include-fixed
 /usr/include
End of search list.
COLLECT_GCC_OPTIONS='-v' '-save-temps' '-O1'  
'-I/home/sergei/GenericBinauralFFTW/C' '-Wall' '-o' 'gcc_bug'
 /home/sergei/AFSWD/install/gcc-4.3.2/libexec/gcc/i686-pc-linux-gnu/4.3.2/cc1
-fpreprocessed gcc_bug.i -march=k8-sse3 -mcx16 -msahf --param l1-cache-size=64
--param l1-cache-line-size=64 -mtune=k8 -quiet -dumpbase gcc_bug.c -auxbase
gcc_bug -O1 -Wall -version -o gcc_bug.s
GNU C (GCC) version 4.3.2 (i686-pc-linux-gnu)
        compiled by GNU C version 4.3.2, GMP version 4.2.2, MPFR version 2.3.2.
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
Compiler executable checksum: 59348dc68d2c7c94f733394a90fbab10
gcc_bug.c: In function ‘main’:
gcc_bug.c:23030: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
".

I am about to upload 'gcc_bug.i' file generated by the above command.


-- 
           Summary: internal compiler error: Segmentation fault
           Product: gcc
           Version: 4.3.2
            Status: UNCONFIRMED
          Severity: major
          Priority: P3
         Component: c
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: sergstesh at yahoo dot com
 GCC build triplet: Linux amdam2 2.6.22.19-0.1-default #1 SMP 2008-10-14
                    22:17:43 +0
  GCC host triplet: Linux amdam2 2.6.22.19-0.1-default #1 SMP 2008-10-14
                    22:17:43 +0
GCC target triplet: Linux amdam2 2.6.22.19-0.1-default #1 SMP 2008-10-14
                    22:17:43 +0


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

[Bug c/38666] internal compiler error: Segmentation fault

[sergstesh at yahoo dot com]

------- Comment #2 from sergstesh at yahoo dot com  2008-12-29 21:53 -------
The bug is data-dependent. If inside the 'for' loop I replace all the
coefficients with 1.0, the failure is graceful:

cc1: out of memory allocating 4054207356 bytes after a total of 105562112 bytes
.


-- 


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

[Bug c/38666] internal compiler error: Segmentation fault

[sergstesh at yahoo dot com]

------- Comment #1 from sergstesh at yahoo dot com  2008-12-29 21:50 -------
Created an attachment (id=17005)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=17005&action=view)
'gcc_bug.i.gz' file produced by 'gcc' and 'gzip' from the input 'gcc_bug.c' one

Source with all the files included. I had to 'gzip' it because otherwise
Bugzilla doesn't accept it because of size.


-- 


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

[Bug c/38666] internal compiler error: Segmentation fault

[sergstesh at yahoo dot com]

------- Comment #3 from sergstesh at yahoo dot com  2008-12-29 21:57 -------
No problem occurs with -O0; with -O2, -O3 'gcc' also exits gracefully:

cc1: out of memory allocating 4283978752 bytes after a total of 228749312 bytes
.


-- 


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

[Bug middle-end/38666] internal compiler error: Segmentation fault

[pinskia at gcc dot gnu dot org]

-- 

pinskia at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|major                       |normal
          Component|c                           |middle-end
  GCC build triplet|Linux amdam2 2.6.22.19-0.1- |x86_64-linux-gnu
                   |default #1 SMP 2008-10-14   |
                   |22:17:43 +0                 |
   GCC host triplet|Linux amdam2 2.6.22.19-0.1- |x86_64-linux-gnu
                   |default #1 SMP 2008-10-14   |
                   |22:17:43 +0                 |
 GCC target triplet|Linux amdam2 2.6.22.19-0.1- |x86_64-linux-gnu
                   |default #1 SMP 2008-10-14   |
                   |22:17:43 +0                 |
           Keywords|                            |memory-hog


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

[Bug c/38666] internal compiler error: Segmentation fault

[sergstesh at yahoo dot com]

------- Comment #4 from sergstesh at yahoo dot com  2008-12-29 22:45 -------
Just to make sure - my OS is 32 bits SUSE-10.3, though the CPU is 64 bits
capable.


-- 

sergstesh at yahoo dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|normal                      |major
          Component|middle-end                  |c


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

[Bug middle-end/38666] internal compiler error: Segmentation fault

[pinskia at gcc dot gnu dot org]

-- 

pinskia at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |pinskia at gcc dot gnu dot
                   |                            |org
           Severity|major                       |normal
          Component|c                           |middle-end


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

[Bug middle-end/38666] internal compiler error: Segmentation fault

[rguenth at gcc dot gnu dot org]

------- Comment #5 from rguenth at gcc dot gnu dot org  2008-12-29 23:42 -------
The function is simply too big and we likely use most of the memory computing
and storing the const reals.  A case for closer investigation.


-- 

rguenth at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |rguenth at gcc dot gnu dot
                   |                            |org


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

[Bug c/38666] internal compiler error: Segmentation fault

[sergstesh at yahoo dot com]

------- Comment #6 from sergstesh at yahoo dot com  2008-12-30 00:00 -------
(In reply to comment #5)
> The function is simply too big and we likely use most of the memory computing
> and storing the const reals.  A case for closer investigation.
> 

(In reply to comment #5)
> The function is simply too big and we likely use most of the memory computing
> and storing the const reals.  A case for closer investigation.
> 

My primary concern is segmentation fault, not the cases when 'gcc' can't
allocate enough memory and reports the problem clearly.

It also appears gcc-3.4.6 is much less memory-hungry - I'm checking it right
now.


-- 

sergstesh at yahoo dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|normal                      |major
          Component|middle-end                  |c


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

[Bug middle-end/38666] internal compiler error: Segmentation fault

[pinskia at gcc dot gnu dot org]

------- Comment #7 from pinskia at gcc dot gnu dot org  2008-12-30 00:01 -------
(In reply to comment #6)
> My primary concern is segmentation fault, not the cases when 'gcc' can't
> allocate enough memory and reports the problem clearly.

The seg fault is most likely some recursive function gone wrong.


-- 

pinskia at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|major                       |normal
          Component|c                           |middle-end


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

[Bug c/38666] internal compiler error: Segmentation fault

[sergstesh at yahoo dot com]

------- Comment #8 from sergstesh at yahoo dot com  2008-12-30 00:08 -------
(In reply to comment #7)
> (In reply to comment #6)
> > My primary concern is segmentation fault, not the cases when 'gcc' can't
> > allocate enough memory and reports the problem clearly.
> 
> The seg fault is most likely some recursive function gone wrong.
> 

I guess the recursive function is in 'gcc'.

Anyway, if you look at the code (probably you've already looked), you'll find
that though it's long, it's simple. I mean, there is a whole lot of similar
relatively simple expressions like this one:

____accumulator[sample_number] += 5.37523999999999973e-09 *
exp(-5.40939200000000003e-06 * d_sample_number) * cos(1.95404999999999995e-01 *
two_pi_times_sample_number - (1.32515999999999989e+00));
.

So, simplistically, because the expressions are simple and the optimization
level is low, I do not see too much place for deep recursion, but I'm
unfamiliar with 'gcc' internals.


-- 

sergstesh at yahoo dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|normal                      |major
          Component|middle-end                  |c


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

[Bug c/38666] internal compiler error: Segmentation fault

[rguenth at gcc dot gnu dot org]

------- Comment #9 from rguenth at gcc dot gnu dot org  2008-12-30 10:17 -------
I expect there to be a "simple" memleak regarding to floating point constant
handling.


-- 


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

[Bug middle-end/38666] internal compiler error: Segmentation fault

[pinskia at gcc dot gnu dot org]

-- 

pinskia at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|major                       |normal
          Component|c                           |middle-end


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

[Bug middle-end/38666] [4.3 Regression] internal compiler error: Segmentation fault

[ubizjak at gmail dot com]

------- Comment #10 from ubizjak at gmail dot com  2009-01-08 13:03 -------
Confirmed, attached testcase fails with -O1 on 4.3 branch, works OK for 4.4
branch.


-- 

ubizjak at gmail dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1
 GCC target triplet|x86_64-linux-gnu            |i686-linux-gnu
      Known to fail|                            |4.3.3
      Known to work|                            |4.4.0
   Last reconfirmed|0000-00-00 00:00:00         |2009-01-08 13:03:12
               date|                            |
            Summary|internal compiler error:    |[4.3 Regression] internal
                   |Segmentation fault          |compiler error: Segmentation
                   |                            |fault
   Target Milestone|---                         |4.3.3


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

[Bug middle-end/38666] [4.3 Regression] internal compiler error: Segmentation fault

[ubizjak at gmail dot com]

------- Comment #11 from ubizjak at gmail dot com  2009-01-08 13:10 -------
Program received signal SIGSEGV, Segmentation fault.
record_one_conflict (allocnos_live=0x16103ee8, hard_regs_live=<value optimized
out>, 
    regno=390007032) at
../../gcc-svn/branches/gcc-4_3-branch/gcc/ra-conflict.c:176
176         word = conflicts[index];
(gdb) bt
#0  record_one_conflict (allocnos_live=0x16103ee8, hard_regs_live=<value
optimized out>, 
    regno=390007032) at
../../gcc-svn/branches/gcc-4_3-branch/gcc/ra-conflict.c:176
#1  0x08535fef in global_conflicts ()
    at ../../gcc-svn/branches/gcc-4_3-branch/gcc/ra-conflict.c:290
#2  0x0850b80d in rest_of_handle_global_alloc ()
    at ../../gcc-svn/branches/gcc-4_3-branch/gcc/global.c:534
#3  0x081d1d43 in execute_one_pass (pass=0x86e38c0)
    at ../../gcc-svn/branches/gcc-4_3-branch/gcc/passes.c:1122


-- 


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

[Bug middle-end/38666] [4.3 Regression] internal compiler error: Segmentation fault

[ubizjak at gmail dot com]

------- Comment #12 from ubizjak at gmail dot com  2009-01-08 13:55 -------
At the point of failure, we have:

bitnum = 1024405, index = 32012

(BTW: The function doesn't crash when index = 26677).


-- 


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

[Bug middle-end/38666] [4.3 Regression] internal compiler error: Segmentation fault in record_one_conflict, ra-conflict.c:176

[hjl dot tools at gmail dot com]

------- Comment #13 from hjl dot tools at gmail dot com  2009-01-08 18:30 -------
Gcc 4.1 gave

cc1: out of memory allocating 3644231872 bytes after a total of 50307072 bytes

on Linux/ia32.


-- 


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

[Bug middle-end/38666] [4.3 Regression] internal compiler error: Segmentation fault in record_one_conflict, ra-conflict.c:176

[hjl dot tools at gmail dot com]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1719 bytes --]



------- Comment #14 from hjl dot tools at gmail dot com  2009-01-08 20:04 -------
This is fixed in 4.4 by IRA:

gnu-3:pts/0[29]> ./xgcc -B./ -O -S /net/gnu-6/export/home/hjl/tmp/gcc_bug.i
-fno-ira
gcc_bug.c: In function ‘main’:
gcc_bug.c:23030: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
gnu-3:pts/0[30]>

When I enable checking in gcc 4.3, I got

[hjl@gnu-17 gcc]$ ./xgcc -B./ /tmp/gcc_bug.i -S -O -v
Reading specs from ./specs
Target: i686-pc-linux-gnu
Configured with: /net/gnu-13/export/gnu/src/gcc-4.3/gcc/configure
--enable-languages=c --disable-bootstrap --enable-checking
Thread model: posix
gcc version 4.3.3 20090108 (prerelease) [gcc-4_3-branch revision 143188] (GCC) 
COLLECT_GCC_OPTIONS='-B./' '-S' '-O' '-v' '-mtune=generic'
 ./cc1 -fpreprocessed /tmp/gcc_bug.i -quiet -dumpbase gcc_bug.i -mtune=generic
-auxbase gcc_bug -O -version -o gcc_bug.s
GNU C (GCC) version 4.3.3 20090108 (prerelease) [gcc-4_3-branch revision
143188] (i686-pc-linux-gnu)
        compiled by GNU C version 4.3.2 20081105 (Red Hat 4.3.2-7), GMP version
4.2.2, MPFR version 2.3.2.
GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096
Compiler executable checksum: 98cd2bcb358a704593004b875ff80d57
gcc_bug.c: In function ‘main’:
gcc_bug.c:23030: internal compiler error: in global_alloc, at global.c:438
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
[hjl@gnu-17 gcc]$ 

We had an overflow in max_bitnum and things went downhill after that.


-- 


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

[Bug middle-end/38666] [4.3 Regression] internal compiler error: Segmentation fault in record_one_conflict, ra-conflict.c:176

[sergstesh at yahoo dot com]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2483 bytes --]



------- Comment #15 from sergstesh at yahoo dot com  2009-01-08 22:18 -------
(In reply to comment #14)
> This is fixed in 4.4 by IRA:
> 
> gnu-3:pts/0[29]> ./xgcc -B./ -O -S /net/gnu-6/export/home/hjl/tmp/gcc_bug.i
> -fno-ira
> gcc_bug.c: In function ‘main’:
> gcc_bug.c:23030: internal compiler error: Segmentation fault
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <http://gcc.gnu.org/bugs.html> for instructions.
> gnu-3:pts/0[30]>
> 
> When I enable checking in gcc 4.3, I got
> 
> [hjl@gnu-17 gcc]$ ./xgcc -B./ /tmp/gcc_bug.i -S -O -v
> Reading specs from ./specs
> Target: i686-pc-linux-gnu
> Configured with: /net/gnu-13/export/gnu/src/gcc-4.3/gcc/configure
> --enable-languages=c --disable-bootstrap --enable-checking
> Thread model: posix
> gcc version 4.3.3 20090108 (prerelease) [gcc-4_3-branch revision 143188] (GCC) 
> COLLECT_GCC_OPTIONS='-B./' '-S' '-O' '-v' '-mtune=generic'
>  ./cc1 -fpreprocessed /tmp/gcc_bug.i -quiet -dumpbase gcc_bug.i -mtune=generic
> -auxbase gcc_bug -O -version -o gcc_bug.s
> GNU C (GCC) version 4.3.3 20090108 (prerelease) [gcc-4_3-branch revision
> 143188] (i686-pc-linux-gnu)
>         compiled by GNU C version 4.3.2 20081105 (Red Hat 4.3.2-7), GMP version
> 4.2.2, MPFR version 2.3.2.
> GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096
> Compiler executable checksum: 98cd2bcb358a704593004b875ff80d57
> gcc_bug.c: In function ‘main’:
> gcc_bug.c:23030: internal compiler error: in global_alloc, at global.c:438
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <http://gcc.gnu.org/bugs.html> for instructions.
> [hjl@gnu-17 gcc]$ 
> 
> We had an overflow in max_bitnum and things went downhill after that.
> 

I do not quite understand the

"
This is fixed in 4.4 by IRA:

gnu-3:pts/0[29]> ./xgcc -B./ -O -S /net/gnu-6/export/home/hjl/tmp/gcc_bug.i
-fno-ira
gcc_bug.c: In function ‘main’:
gcc_bug.c:23030: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
gnu-3:pts/0[30]>
"

part, i.e. on the one hand there is a statement that the problem is fixed in
4.4, on the other hand the example still shows "internal compiler error:
Segmentation fault" - is this example from 4.4 ?

If yes, how does "Segmentation fault" indicate that the problem is fixed ?


-- 


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

[Bug middle-end/38666] [4.3 Regression] internal compiler error: Segmentation fault in record_one_conflict, ra-conflict.c:176

[hjl dot tools at gmail dot com]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 887 bytes --]



------- Comment #16 from hjl dot tools at gmail dot com  2009-01-08 22:23 -------
(In reply to comment #15)
> This is fixed in 4.4 by IRA:
> 
> gnu-3:pts/0[29]> ./xgcc -B./ -O -S /net/gnu-6/export/home/hjl/tmp/gcc_bug.i
> -fno-ira
> gcc_bug.c: In function ‘main’:
> gcc_bug.c:23030: internal compiler error: Segmentation fault
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <http://gcc.gnu.org/bugs.html> for instructions.
> gnu-3:pts/0[30]>
> "
> 
> part, i.e. on the one hand there is a statement that the problem is fixed in
> 4.4, on the other hand the example still shows "internal compiler error:
> Segmentation fault" - is this example from 4.4 ?
> 
> If yes, how does "Segmentation fault" indicate that the problem is fixed ?
> 

You only see "Segmentation fault" with -fno-ira.


-- 


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

[Bug middle-end/38666] [4.3 Regression] internal compiler error: Segmentation fault in record_one_conflict, ra-conflict.c:176

[sergstesh at yahoo dot com]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1012 bytes --]



------- Comment #17 from sergstesh at yahoo dot com  2009-01-08 22:26 -------
(In reply to comment #16)
> (In reply to comment #15)
> > This is fixed in 4.4 by IRA:
> > 
> > gnu-3:pts/0[29]> ./xgcc -B./ -O -S /net/gnu-6/export/home/hjl/tmp/gcc_bug.i
> > -fno-ira
> > gcc_bug.c: In function ‘main’:
> > gcc_bug.c:23030: internal compiler error: Segmentation fault
> > Please submit a full bug report,
> > with preprocessed source if appropriate.
> > See <http://gcc.gnu.org/bugs.html> for instructions.
> > gnu-3:pts/0[30]>
> > "
> > 
> > part, i.e. on the one hand there is a statement that the problem is fixed in
> > 4.4, on the other hand the example still shows "internal compiler error:
> > Segmentation fault" - is this example from 4.4 ?
> > 
> > If yes, how does "Segmentation fault" indicate that the problem is fixed ?
> > 
> 
> You only see "Segmentation fault" with -fno-ira.
> 

Am I supposed to encounter "Segmentation fault" at all ?


-- 


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

[Bug middle-end/38666] [4.3 Regression] internal compiler error: Segmentation fault in record_one_conflict, ra-conflict.c:176

[rguenth at gcc dot gnu dot org]

------- Comment #18 from rguenth at gcc dot gnu dot org  2009-01-08 23:02 -------
So, only the ICE is a regression, not the memory-hog, correct?


-- 

rguenth at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |ice-on-valid-code


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

[Bug middle-end/38666] [4.3 Regression] internal compiler error: Segmentation fault in record_one_conflict, ra-conflict.c:176

[ubizjak at gmail dot com]

------- Comment #19 from ubizjak at gmail dot com  2009-01-09 07:20 -------
(In reply to comment #18)
> So, only the ICE is a regression, not the memory-hog, correct?

Yes.


-- 

ubizjak at gmail dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|memory-hog                  |


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

[Bug middle-end/38666] [4.3 Regression] internal compiler error: Segmentation fault in record_one_conflict, ra-conflict.c:176

[rguenth at gcc dot gnu dot org]

-- 

rguenth at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P3                          |P2


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

[Bug middle-end/38666] [4.3 Regression] internal compiler error: Segmentation fault in record_one_conflict, ra-conflict.c:176

[rguenth at gcc dot gnu dot org]

------- Comment #20 from rguenth at gcc dot gnu dot org  2009-01-24 10:21 -------
GCC 4.3.3 is being released, adjusting target milestone.


-- 

rguenth at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|4.3.3                       |4.3.4


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

[Bug middle-end/38666] [4.3 Regression] internal compiler error: Segmentation fault in record_one_conflict, ra-conflict.c:176

[rguenth at gcc dot gnu dot org]

------- Comment #21 from rguenth at gcc dot gnu dot org  2009-08-04 12:29 -------
GCC 4.3.4 is being released, adjusting target milestone.


-- 

rguenth at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|4.3.4                       |4.3.5


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

[Bug middle-end/38666] [4.3 Regression] internal compiler error: Segmentation fault in record_one_conflict, ra-conflict.c:176

[rguenth at gcc dot gnu dot org]

------- Comment #22 from rguenth at gcc dot gnu dot org  2010-05-22 18:13 -------
GCC 4.3.5 is being released, adjusting target milestone.


-- 

rguenth at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|4.3.5                       |4.3.6


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

[Bug middle-end/38666] [4.3 Regression] internal compiler error: Segmentation fault in record_one_conflict, ra-conflict.c:176

[sergstesh at yahoo dot com]

------- Comment #23 from sergstesh at yahoo dot com  2010-05-23 04:49 -------
Just wondering after so many adjustments - is the bug going to be fixed ?


-- 


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

[Bug middle-end/38666] [4.3 Regression] internal compiler error: Segmentation fault in record_one_conflict, ra-conflict.c:176

[rguenth at gcc dot gnu dot org]

------- Comment #24 from rguenth at gcc dot gnu dot org  2010-05-24 12:56 -------
(In reply to comment #23)
> Just wondering after so many adjustments - is the bug going to be fixed ?

Very unlikely.  If there is a small patch that fixed it for 4.4.0 then
that can possibly be back-ported (but nobody tried to bisect the svn for that
sofar).  But I guess that the thing that fixed it was the merge of the
new register allocator.


-- 


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