c++/10060: gcc internal compiler error

andreas@florath.net andreas@florath.net
Thu Mar 13 14:56:00 GMT 2003


>Number:         10060
>Category:       c++
>Synopsis:       gcc internal compiler error
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Mar 13 12:26:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     andreas@florath.net
>Release:        g++ (GCC) 3.2.1
>Organization:
>Environment:
config.guess: sparc-sun-solaris2.8
../gcc-3.2.1/configure --enable-threads --with-as=/opt/gcc321/bin/as --with-gnu-as
>Description:
g++ reports:
> g++ -pipe -ggdb -o t t.cc
{standard input}: Assembler messages:
{standard input}:597943: Warning: end of file not at end of a line; newline inserted
{standard input}:599822: Error: expected comma after name `a9' in .size directive
g++: Internal error: Segmentation Fault (program cc1plus)
Please submit a full bug report.
See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.

The dumped core has a size of 826761032 bytes.
> pstack core | wc
74822  748214 6808444
> pstack core | fgrep ggc_mark_rtx_children_1 | wc
74806  748060 6807318
>How-To-Repeat:
The attached file must be compiled and then executed - the resulting file (which is *LARGE*) must be compiled:
> g++ -o pw pw.cc
> ./pw 100000 >t.cc
> g++ -pipe -ggdb -o t t.cc
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="pw.cc"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="pw.cc"

Ly8gUHJvZ3JhbSB0byB3cml0ZSBwcm9ncmFtcwojaW5jbHVkZSA8aW9zdHJlYW0+CiNpbmNsdWRl
IDxjc3RkbGliPgoKaW50IG1haW4oaW50IGFyZ2MsIGNoYXIgKiBhcmd2W10pCnsKICAgbG9uZyBj
b25zdCBjbnQoYXRvaShhcmd2WzFdKSk7CgogICBzdGQ6OmNvdXQgPDwgCiAgICAgICIjaW5jbHVk
ZSA8aW9zdHJlYW0+XG4iCiAgICAgICJjbGFzcyBBIFxuIgogICAgICAieyBcbiIKICAgICAgIiAg
cHVibGljOiBcbiIKICAgICAgIiAgIEEoaW50IGkpIDogbV9pbnQoaSl7fVxuIgogICAgICAiICAg
fkEodm9pZCl7fVxuIgogICAgICAiXG4iCiAgICAgICIgIHByaXZhdGU6XG4iCiAgICAgICIgICAg
aW50IG1faW50O1xuIgogICAgICAifTtcbiI7CgogICBmb3IobG9uZyBpKDApOyBpPGNudDsgKytp
KQogICAgICBzdGQ6OmNvdXQgPDwgIkEgYSIgPDwgaSA8PCAiKCIgPDwgaSA8PCAiKTsiIDw8IHN0
ZDo6ZW5kbDsKCiAgIHN0ZDo6Y291dCA8PCAKICAgICAgImludCBtYWluKHZvaWQpXG4iCiAgICAg
ICJ7XG4iCiAgICAgICIgICBsb25nIGxvbmcgYygwKTtcbiI7CgogICBmb3IobG9uZyBpKDApOyBp
PGNudDsgKytpKQogICAgICBzdGQ6OmNvdXQgPDwKCSAiICAgZm9yKGxvbmcgaigwKTsgajwxMDA7
ICsrailcbiIKCSAiICAgICBjKz1qO1xuIjsKCiAgIHN0ZDo6Y291dCA8PCAKICAgICAgIlxuIgog
ICAgICAiICAgcmV0dXJuIDA7XG4iCiAgICAgICJ9XG4iOwoKICAgcmV0dXJuIDA7Cn0KCgo=



More information about the Gcc-bugs mailing list