From: Daniel Jacobowitz <dan@debian.org>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Invalid compilation without -fno-strict-aliasing
Date: Thu, 27 Feb 2003 15:35:12 -0500 [thread overview]
Message-ID: <20030227203512.GA12623@nevyn.them.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0302271157380.9696-100000@home.transmeta.com>
On Thu, Feb 27, 2003 at 12:00:46PM -0800, Linus Torvalds wrote:
>
> On Thu, 27 Feb 2003, Daniel Jacobowitz wrote:
> > >
> > > My personal opinion is (and was several years ago when this started
> > > coming up) that a cast (any cast) should do it. But I don't are _what_
> > > it is, as long as it is syntactically sane and isn't limited to special
> > > cases like unions.
> >
> > Well, if that's all you're asking for, it's easy - I don't know if
> > you'll agree that the syntax is sane, but it's there. From the GCC 3.3
> > manual:
> >
> > `may_alias'
>
> Halleluja. It still leaves us with all other compilers unaccounted for,
> but yes, this will allow fixing the problem for us in the future.
>
> Too bad the current gcc-3.3 is apparently not useful for the kernel for
> other reasons right now (ie the inlining issue which is being discussed on
> the gcc lists, and that annoying sign warning), but that may well be
> resolved by the time it gets released.
We could work around both of these: disable the sign compare warning,
and use check_gcc to set a high number for -finline-limit...
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-02-27 20:26 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-25 23:46 Invalid compilation without -fno-strict-aliasing Jean Tourrilhes
2003-02-26 15:38 ` Horst von Brand
2003-02-26 16:04 ` Falk Hueffner
2003-02-26 20:47 ` Horst von Brand
2003-02-26 20:57 ` Daniel Jacobowitz
2003-02-26 22:22 ` Jakub Jelinek
2003-02-27 19:30 ` Linus Torvalds
2003-02-27 19:45 ` Daniel Jacobowitz
2003-02-27 20:00 ` Linus Torvalds
2003-02-27 20:35 ` Daniel Jacobowitz [this message]
2003-02-27 20:38 ` Linus Torvalds
2003-02-27 23:55 ` H. Peter Anvin
2003-03-01 8:29 ` Anton Blanchard
2003-02-26 17:22 ` Jean Tourrilhes
2003-02-26 21:07 ` Horst von Brand
2003-02-27 4:41 ` Daniel Phillips
2003-02-26 17:26 ` Linus Torvalds
-- strict thread matches above, loose matches on Subject: below --
2003-02-26 4:33 Albert Cahalan
2003-02-26 17:20 ` Jean Tourrilhes
2003-02-26 18:23 ` Richard B. Johnson
2003-02-26 19:22 ` Daniel Jacobowitz
2003-02-26 19:40 ` Richard B. Johnson
2003-02-26 19:42 ` Daniel Jacobowitz
2003-02-26 20:19 ` Richard B. Johnson
2003-02-26 21:30 ` Albert Cahalan
2017-11-03 1:54 Yubin Ruan
2017-11-03 12:27 ` Paul E. McKenney
2017-11-03 13:33 ` Yubin Ruan
2017-11-03 14:03 ` Paul E. McKenney
2017-11-03 14:12 ` Yubin Ruan
2017-11-03 14:38 ` Paul E. McKenney
2017-11-03 23:26 ` Yubin Ruan
2017-11-03 23:55 ` Paul E. McKenney
2017-11-04 0:24 ` Yubin Ruan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030227203512.GA12623@nevyn.them.org \
--to=dan@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.