I see. I just read the Changes doc myself and its warnings about gcc
2.95. The no-strict-aliasing flag does nothing to fix the assembler
error. The following is from the README.Debian that comes with its gcc
package.
---
In Debian 2.2 the default C compiler was changed to gcc-2.95.2. That's
basically the unreleased and renamed egcs-1.2 compiler (The egcs
steering committee was appointed official GNU maintainer for GCC in
April 1999; the egcs team will be responsible for rolling out future
GCC releases). The old gcc-2.7.2.3 C compiler is still available for
compatibility reasons (compilation of 2.0.xx kernels).
--
I can find no Debian packages for egcs gcc 2.91. I could build it
myself, but I'm not sure what implications that has on some of the
standard libraries on my system, and I am not confident about
introducing such a major change to my otherwise good working bleeding
edge development box. I understand that this is my choice.
I wonder, but I have no clue, if there is an intention to move the
kernel to supporting gcc 2.95. Otherwise, it must be very difficult for
the Debian maintainers to continue with their approach. Even if there is
no move toward the new version, then, according to the FAQ topic, mmx.h
should still be revised simply as a matter of correctness.
Also, I looked for a flag in my version of gcc to not detect an invalid
operand clobber specifier. But I can not find one.
Stefan Lucke wrote:
>
> On Don, 07 Dez 2000, Dan Dennedy wrote:
> > Stefan wrote:
> > > The error message is the same Arne reported. Buck modified mmx.h
> > > about two weeks ago. Did you use current snapshot of libdv ?
> > > I never got such an error message (K6/2-400, K6/2+-500@550) so this
> > > is perhaps compiler/distribution dependent (SuSE 6.3).
> Checked my gcc version. It is:
> lucke@jarada:~ > gcc -v
> Reading specs from /usr/lib/gcc-lib/i486-linux/egcs-2.91.66/specs
> gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)
>
> >From kernel Documentaion/Changes this is recommended/minimal gcc version.
> There is also a hint for gcc 2.95 to use -fno-strict-aliasing.
>
> >
> > I checked out from CVS just last night. I'm running Debian woody (unstable),
> > which I upgrade every other week. My gcc is version 2.95.2.
> >
> > READ THIS gcc FAQ NOTE (Problems with invalid 'asm' statements) -->
> > http://gcc.gnu.org/cgi-bin/fom.cgi?_highlightWords=egcs&file=23
>
> --
>
> mfg
>
> Stefan Lucke (lu...@sn...)
|