public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: dougk71@comcast.net To: gcc-gnats@gcc.gnu.org Subject: preprocessor/10102: preprocessor runs out of stack space ..internal segment error in gcc Date: Sat, 15 Mar 2003 16:56:00 -0000 [thread overview] Message-ID: <20030315165337.6971.qmail@sources.redhat.com> (raw) >Number: 10102 >Category: preprocessor >Synopsis: preprocessor runs out of stack space ..internal segment error in gcc >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Sat Mar 15 16:56:01 UTC 2003 >Closed-Date: >Last-Modified: >Originator: dougk71@comcast.net >Release: msp-gcc 030306 >Organization: >Environment: Windows 98 SE gcc msp430 >Description: the test program test1.c bombs with a segmentation error most of the time. Also after making absolutely no changes to the source or the make files msp430-gcc will avoid the segmnetation error and begin to flag the #ifend type directives after processing them siccessfully a good way into the tree as if it ran out of stack space or something. msp430-gcc.exe test1.c -mmcu=msp430x1121 -o test1 Same is true in Win ME latest build 030306 >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2003-03-15 16:56 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-15 16:56 dougk71 [this message] 2003-03-16 2:56 Zack Weinberg 2003-03-25 2:33 bangerth 2003-04-07 7:16 neil
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=20030315165337.6971.qmail@sources.redhat.com \ --to=dougk71@comcast.net \ --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: linkBe 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).