On Nov 27, 2007 12:03 PM, Joe Buck <[EMAIL PROTECTED]> wrote: > gcc-3.3 is quite old and is no longer maintained, though if the bug you > found is still present in current sources, it should be reported.
I know. Debian's fresh releases are always full of really old stuff. Anyway, 4.1 too: $ /usr/bin/gcc-4.1 -I../../tpd-include -E -DKERNEL_26 emlib.c -o emlib.i <built-in>:0: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. For Debian GNU/Linux specific bug reporting instructions, see <URL:file:///usr/share/doc/gcc-4.1/README.Bugs>. > > Sending the output to stdout instead, I get this: > > To do anything about a bug, the developers will need a complete test > case that produces the bug. Changes to the test case that *don't* > produce a bug are not interesting. If it is worth chasing. It is not worth chasing if someone readily recognizes the symptom and says, "Yes, I've fixed something like that." Since the trivial trim of the sources yielded something that did not fault, creating something that still fails will wind up taking serious work. It would need a reasonable prospect of being useful before I would afford the time. Thanks - Bruce
