On Tue April 26 2005 11:10, Joseph S. Myers wrote:
> On Tue, 26 Apr 2005, Bruce Lilly wrote:
>
> > Demonstration code:
> > --
> > #define AAA 0x1U
> > #define BBB 0x2U
> >
> > struct foo {
> > unsigned int bar:8;
>
On Mon April 25 2005 20:52, Zack Weinberg wrote:
> Bruce Lilly <[EMAIL PROTECTED]> writes:
>
> > Earlier versions of gcc retain static character strings in object
> > files which can be used for identification via ident (RCS) or what
> > (SCCS). Gcc 4.0.0 removes t
Demonstration code:
--
#define AAA 0x1U
#define BBB 0x2U
struct foo {
unsigned int bar:8;
};
struct foo foos[] = {
{ ~(AAA) },
{ ~(BBB) },
{ ~(AAA|BBB) },
{ ~(AAA&BBB) }
};
--
compiling with gcc 3.x produced no warnings, as expe
Hi,
Earlier versions of gcc retain static character strings in object files
which can be used for identification via ident (RCS) or what (SCCS).
Gcc 4.0.0 removes them above optimization level 1. Global strings
are retained, of course, but that may lead to namespace collisions.
#ident doesn't wor
> Output from running srcdir/config.guess. Do not send that file itself, just
> the one-line output from running it.
i686-pc-linux-gnu
> The output of gcc -v for your newly installed gcc. This tells us which
> version of GCC you built and the options you passed to configure.
Using built-in s
