[Bug c/38358] New: Could not compile gcc using large include files

[Bug c/38358] New: Could not compile gcc using large include files

[ahjiefreak at yahoo dot com]

I am trying to compile a typical c file with include option turned on. The
include option includes .h file as part of the array element declaration for
the c file.

When I did compile:-

gcc c.c -include myfile.h -D STS
In file included from /usr/include/sys/cdefs.h:0,
                 from /usr/include/features.h:33,
                 from /usr/include/stdio.h:9,
                 from c.c:19:
/usr/include/bits/wordsize.h:1: internal compiler error: Aborted
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://bugzilla.redhat.com/bugzilla> for instructions.

I have checked the c.c:19 and they are commentation without any code before and
after that line. My exact code only starts at line 40. I included the same .h
file but with smaller size of .h file. It works perfectly and compilable.This
file size is around 1-2MB. But the previous .h file which gives the above error
has 1GB of file size.

Is this a bug or do i need to specify any extra options to handle this special
case?


Please advise.


Thanks.


-- 
           Summary: Could not compile gcc using large include files
           Product: gcc
           Version: 4.1.2
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: ahjiefreak at yahoo dot com


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

[Bug middle-end/38358] Could not compile gcc using large include files

[pinskia at gcc dot gnu dot org]

------- Comment #1 from pinskia at gcc dot gnu dot org  2008-12-02 00:03 -------
Did you see:
See <URL:http://bugzilla.redhat.com/bugzilla> for instructions.

??


-- 

pinskia at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|c                           |middle-end


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

[Bug middle-end/38358] Could not compile gcc using large include files

[ahjiefreak at yahoo dot com]

------- Comment #2 from ahjiefreak at yahoo dot com  2008-12-02 00:26 -------
(In reply to comment #1)
> Did you see:
> See <URL:http://bugzilla.redhat.com/bugzilla> for instructions.
> 
> ??
> 

Yes. I am using Debian and I could not find any suitable class to lodge a bug
report under RedHat bugzilla. I figured it out that this is the closest match.


-- 

ahjiefreak at yahoo dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ahjiefreak at yahoo dot com


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

[Bug middle-end/38358] Could not compile gcc using large include files

[pinskia at gcc dot gnu dot org]

------- Comment #3 from pinskia at gcc dot gnu dot org  2008-12-02 00:29 -------
Wait how are you using debain but using Redhat's modified GCC ?


-- 


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

[Bug middle-end/38358] Could not compile gcc using large include files

[rguenth at gcc dot gnu dot org]

------- Comment #4 from rguenth at gcc dot gnu dot org  2008-12-02 11:10 -------
If you are having a large array initializer you may run into memory problems
and/or internal limitations.  Without a testcase it's hard to tell.


-- 


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

[Bug middle-end/38358] Could not compile gcc using large include files

[ahjiefreak at yahoo dot com]

------- Comment #5 from ahjiefreak at yahoo dot com  2008-12-02 13:07 -------
Hi,

Thanks for your prompt reply.

Is there any suggestion or workaround in this case in order for gcc to compile
it successfully?

I would have think its not wise to attach quite a big file over the email.

Please advise. Thanks.



(In reply to comment #4)
> If you are having a large array initializer you may run into memory problems
> and/or internal limitations.  Without a testcase it's hard to tell.
> 


-- 


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