Re: user-mode port 0.44-2.4.7

Rob Landley (landley@webofficenow.com)
Mon, 23 Jul 2001 13:50:37 -0400


On Monday 23 July 2001 18:27, Andrea Arcangeli wrote:
> On Mon, Jul 23, 2001 at 09:20:32AM -0400, Rob Landley wrote:
> > On Monday 23 July 2001 18:09, Andrea Arcangeli wrote:
> > > GCC will obviously _never_ introduce a BUG(), I never said that, the
> > > above example is only meant to show what GCC is _allowed_ to do and
> > > what we have to do to write correct C code.
> >
> > "Correct" C code as in portable C code? Standards compliant so it's
> > portable
>
> correct C code _mainly_ for gcc which is very aggressive.
>
> Andrea

Very aggressive and very known.

If we know how GCC is going to behave in a given situation (and have a fairly
good idea of how it's going to behave in the future), we don't have to worry
about theoretical stardards loopholes like it calling BUG(), do we?

Is there something in the current behavior that's causing trouble (in which
case, what exactly is it), or are the gcc guys (who you mentioned earlier*)
warning that the behavior of upcoming versions of gcc is likely to break
known constructs in the current kernel?

Rob

(Has the english language officially held a funeral for the word "whom" yet?)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/