public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: woodfin@intersystems.com
To: gcc-gnats@gcc.gnu.org
Subject: c/10344: Internal compiler error on large struct
Date: Mon, 07 Apr 2003 22:46:00 -0000 [thread overview]
Message-ID: <20030407224117.3077.qmail@sources.redhat.com> (raw)
>Number: 10344
>Category: c
>Synopsis: Internal compiler error on large struct
>Confidential: no
>Severity: serious
>Priority: low
>Responsible: unassigned
>State: open
>Class: ice-on-legal-code
>Submitter-Id: net
>Arrival-Date: Mon Apr 07 22:46:01 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator: Tom Woodfin
>Release: gcc version 3.2 20020927 (prerelease)
>Organization:
>Environment:
Cygwin on Windows XP SP1. P4 Xeon with Hyperthreading enabled.
>Description:
gcc seg faults when compiling a return statement which calls an identity function on a static struct containing a large array.
>How-To-Repeat:
The code attached causes a gcc seg fault while compiling the line noted. A substantially smaller array in the space struct compiles (and runs) successfully. A larger one crashes. In a particular magic range around 1050000 (at least on this machine), compilation seems to go into some kind of loop.
Command line was:
gcc -v -save-temps teststruct.c >& teststruct.log
Not repeatable on gcc version 2.95.3 20010315 (SuSE)
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/x-gzip-compressed; name="teststruct.tgz"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="teststruct.tgz"
H4sIANb9kT4AA+1X62/bNhDPV+mvINIOs9Ho4UedzK0LNA+0ATInSNLHMAwaTVEyA4rSRCq2N+x/
31EPW3a8xcCWdB90CCLyxx+PxzvekVZUKqnSjCibx+Hek4jbcd3BYLDnum7n8HUv/8Kf/mrpD/ow
djjo93uHg0HfBX5v0O/uIfdpzFmXTCqcIrR3G0foSxz7ARNbeeNY0Oew55nlmmKfiRDJhBKJghS8
4GQydTibOCEhlv6ywdHASohFFuGMCadnd52cbp7EImBhllIfzZiaDpEjqEopd2RK8tlAtXoOqWjI
sqjAE04tjkWY4ZDKETkgr14dBIeHB3f4HtcYbBKSu1VfTVMwVY6SWLI5wHpBSy6kopH1O5BXTMFl
OR5nymKC8MynvhVSpehcrXhMKJomKYX/APpM5qi843cWnROaKBYLWRu5p6kEyNJ7ZwEjVpoJxaLc
VLlSK6dYO8SyJhnj/qhyHmci03ZPY6lG6x4FFM4g2PcQL3VOMQu0b8DagM1HOkJ6cE7JBgQO0d72
WTpyqCKAgHF5rwwqIJVHNCrgVM8ZOFEop8SLOVr3cp6cMGHe5gFAUexTPkR5GEyIMSrdgiDWqOu6
XfeH7iFqgVlwECiWtG3udKJIkrg2rIrys2GB6ffIOvW8D+NPJ5436q06P56PL68B6q6gq/e3Jx8v
zj6fXQDuFvjXr97743Pv89n1zfnleNRxc/7Xo4E36tRb74tDNAJDhMqnji+98/HF+fjM8/L+ze3p
iffx8ub2DDr5FJJkI9Y7GkAzwmTKBC27p+XH89YapSKVCerpvdf7CfieZVGSxlvQ7hasV2JS+QRz
PvI8rFTKJpmintdqLQc8r93OiQGWajuzGllSiU/JFl4OV6Rd19192V1W9XRHp15r3t6kzktKzdVL
95/89OHL+bhXObLo5p1M6EICmG6UwwXGiiOx07m17dVfmUHOrNfFCfsXetaH9YytC6jV5U3qHWZC
VqCTq6vHkxO1IPFgAWgcueCzA3R8c4rkQig8b5ssFHGqr4danUBQFihRcbpA+8XGYohlZdr+bnM2
dvhwsp+BVQQr+tjUv3POvvmiKmj7tm3vI0lxSqZIX/dKoil4YLiivAXKu62UInjruneraOWcdQ3m
mfBRHFRLcfCPvWOBJJ2iPgYQPqgWhEoJ90w97Mj6LWMUipgP9WQC4V0/IdUNhqy4PiD/q9OSq9lF
yfru2qZB4ihhHHYzWaAdtdhmfW9DdC5QkAmiL230K9ylx1kQ0PT74Tqt0xui/N4XmCOapnE6RDc0
jOCM4nxqgDOuzKt8DSSzScQUwqCZczTJQgSej1N1YOrXBVqLg4yzlFDEAoQTQJOUweG1zRsKh+vT
9cVwqlQydJzZbGaHIrPjNHRkHKgZPBZ01B3QLu2pivg7FMQpGFnYrN8gtvl077/68XmqNR55/7v9
h+//nttr3v/PIS9QB+3XUwTqpobe6terfj2/qwDI0QhD8YKHLK3A9Ylm0YTfEhgy4Q8TIQJvYeRj
hX/uuK91qH95Y/75ZoNI4mRRZGtrDZ/kWDtXBK/0LBUlBDrMDR3LhG8VfKnTmaA1DqRkFKc+w/y4
VLPUWzNhk9XWq33rKD2d1O+Bp1rjsfw/7DzM/87rJv+fQww7gIvX2Mhkw9Y/leGDObzIUNe0Qx5P
OPJWiQKDPg2MGvLGsCXhRhe+apFQo6dbVADLrLGGppFkcsqN7+gkMY0ovtdNmRygAlgOzk0D7l9u
vOy6ekxW5KOWJrZz/nypYDLXAAYArm5udLorll+xXpZFSINkNRXD1JZeoL2EfID6GxgB7KjC9K8X
w4toRJLFFhuw768ZnsRJtaeqCSgUH+Nl37S5Lq3I26w8tntQGlz5uljvH/z8rU9TI4000kgjjTTS
SCONNNJII4000kgjjTTyf5K/APP61pYAKAAA
reply other threads:[~2003-04-07 22:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030407224117.3077.qmail@sources.redhat.com \
--to=woodfin@intersystems.com \
--cc=gcc-gnats@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).