This is the mail archive of the
libc-alpha@sourceware.cygnus.com
mailing list for the glibc project.
Re: I think I found a bug...
- To: Mark Grosberg <myg at tempest dot din dot net>
- Subject: Re: I think I found a bug...
- From: Ralf Baechle <ralf at uni-koblenz dot de>
- Date: Wed, 1 Mar 2000 13:31:07 +0100
- Cc: libc-alpha at sourceware dot cygnus dot com, bugs at gnu dot org
- References: <Pine.LNX.4.10.10002290219070.29139-100000@tempest.din.net>
On Tue, Feb 29, 2000 at 02:27:51AM -0500, Mark Grosberg wrote:
> However, the nested strcpy()'s seem to be causing the problem. At first I
> thought the GCC optimizer was being thrown into an endless loop. However,
> I discussed the problem on the gcc-bugs mailing list and they said that
> given sufficient virtual memory GCC does complete the compile.
>
> It seems that the problem really stems from glibc's inline string
> intrinsics. While the GCC compiler should not use vast amounts of virtual
> memory to compile such an itty-bitty routine, the GCC people suspect that
> something in glibc is tickling some nasty behavior in GCC.
At least some versions of glibc implement a number of string functions
as very complex inline functions. In fact the implementation is too strong
for some versions of egcs which will dump core or need vast amounts of
memory, I've seen cc1 processes of over 100mb.
Ralf