gcc reports Internal Error

Stuart MacDonald stuartm@connecttech.com
Thu Jul 11 16:34:00 GMT 2002

From: "Zack Weinberg" <zack@codesourcery.com>
> For GCC, a much more efficient technique is to make use of the -dM
> option.  See the manual.

I'm aware of that, but it is gcc specific. I'm looking for a general
solution. (And ignoring the problem that the search space seems to
large to brute force. :-))

Also, -dM wasn't a complete answer; __FILE__ wasn't in the output

> > # bfdefines 4 | gcc -E - > results
> >
> GCC attempts to read the entire file into memory before processing it.

Interesting. Perhaps this shouldn't be the case when reading stdin. It
would be nice to compile what's available instead of waiting for a
long time for all of the code to come through the pipe, then
compiling. Parallelism vs serialisation.

> This may change in the future, but has not been a problem for normal
> use so far.  Presumably, your program generates more data than will
> fit in memory at once.

I'm certain that's the case.


More information about the Gcc-bugs mailing list