From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25281 invoked by alias); 16 Mar 2003 02:56:00 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 25254 invoked by uid 71); 16 Mar 2003 02:56:00 -0000 Date: Sun, 16 Mar 2003 02:56:00 -0000 Message-ID: <20030316025600.25251.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Zack Weinberg Subject: Re: preprocessor/10102: preprocessor runs out of stack space ..internal segment error in gcc Reply-To: Zack Weinberg X-SW-Source: 2003-03/txt/msg01046.txt.bz2 List-Id: The following reply was made to PR preprocessor/10102; it has been noted by GNATS. From: Zack Weinberg To: dougk71@comcast.net Cc: gcc-gnats@gcc.gnu.org Subject: Re: preprocessor/10102: preprocessor runs out of stack space ..internal segment error in gcc Date: Sat, 15 Mar 2003 18:47:42 -0800 dougk71@comcast.net writes: > 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 I'm afraid this problem description makes no sense to me. Furthermore, you did not provide the file test1.c in your bug report, and you appear to be using a version of gcc which is not distributed by the FSF. Thus, it is impossible for me to attempt to reproduce the problem. Please clarify the situation. zw