Date:	Wed, 13 Jun 2001 13:41:42 +0300 (IDT)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Andris Pavenis <pavenis AT latnet DOT lv>
cc:	djgpp-workers AT delorie DOT com
Subject:	Re: GCC-3.0 related problem with src/libc/stubs/stubXXXX.S
In-Reply-To:	<200106130926.f5D9QAX03971@hal.astr.lu.lv>
Message-ID:	<Pine.SUN.3.91.1010613133805.17089B@is>
MIME-Version:	1.0
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Wed, 13 Jun 2001, Andris Pavenis wrote:

> stubXXXX.S files generated by mkstubs triggers gcc-3.0 preprocessor bug
> (See http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=3081&database=gcc):
> 
> preprocessor errorously merges first 2 lines (if these are not preprocessor 
> instructions) when -imacros command line option is being used. It's rather
> harmless for most real life situations (we have #include ... at start of 
> program), but it causes syntax errors in this case (stubXXXX.S)
> 
> I got a respsonse that it's rather unlikely to be fixed in gcc-3.0 release
> Fortunatelly it's easy to workaround this bug by simply adding
> blank line at start of .S file:

I don't like this solution: I think a library shouldn't have to work 
around such blatant bugs (are they serious about not fixing it in 3.0 
release??).

Does it help to use -traditional when compiling stub*.S files?  If it 
does, I'd prefer to use tradcpp for the stubs until they fix this in the 
mainline version.

- Raw text -