On Tue, Nov 27, 2007 at 12:19:40PM -0800, Bruce Korb wrote:
> > 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
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/
On Tue, Nov 27, 2007 at 11:51:18AM -0800, Bruce Korb wrote:
> $ /usr/bin/gcc-3.3 -I../../tpd-include -E -DKERNEL_26 emlib.c -o emlib.i
> cc1: internal compiler error: Segmentation fault
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See http://gcc.gnu.org/bugs.htm
$ /usr/bin/gcc-3.3 -I../../tpd-include -E -DKERNEL_26 emlib.c -o emlib.i
cc1: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See http://gcc.gnu.org/bugs.html> for instructions.
For Debian GNU/Linux specific bug reporting instr
