From: Neil Booth <neil@daikokuya.co.uk>
To: Linus Torvalds <torvalds@osdl.org>,
Thomas Schlichter <thomas.schlichter@web.de>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, gcc@gcc.gnu.org
Subject: Re: [PATCH] fix warning about duplicate 'const'
Date: Wed, 10 Mar 2004 06:39:00 -0000 [thread overview]
Message-ID: <20040310064001.GA7584@daikokuya.co.uk> (raw)
In-Reply-To: <20040310054918.GB4068@twiddle.net>
Richard Henderson wrote:-
> On Mon, Mar 08, 2004 at 05:32:11PM -0800, Linus Torvalds wrote:
> > Also, I'm not convinced this isn't a gcc regression. It would be stupid to
> > "fix" something that makes old gcc's complain, when they may be doing the
> > right thing.
>
> Problem is, that we're supposed to complain for
>
> const const int x;
> and
> typedef const int t;
> const t x;
>
> The proposition that we're not supposed to complain for
>
> const int a;
> const __typeof(a) x;
>
> seems dicey at best. I'm not sure what to do about this, actually.
> We might could do something with a new __nonqual_typeof(a) that
> strips outermost type qualifications, but I havn't given that much
> thought.
Or you could compile in C99 mode?
Neil.
next prev parent reply other threads:[~2004-03-10 6:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200403090043.21043.thomas.schlichter@web.de>
[not found] ` <20040308161410.49127bdf.akpm@osdl.org>
[not found] ` <Pine.LNX.4.58.0403081627450.9575@ppc970.osdl.org>
[not found] ` <200403090217.40867.thomas.schlichter@web.de>
[not found] ` <Pine.LNX.4.58.0403081728250.9575@ppc970.osdl.org>
2004-03-10 5:49 ` Richard Henderson
2004-03-10 6:39 ` Neil Booth [this message]
2004-03-10 10:15 ` Joseph S. Myers
2004-03-10 10:30 ` Gabriel Dos Reis
2004-03-10 22:22 ` Richard Henderson
2004-03-10 23:42 ` Gabriel Dos Reis
2004-03-10 8:21 ` Gabriel Dos Reis
2004-03-10 15:36 ` Linus Torvalds
2004-03-10 18:22 ` Richard Henderson
2004-03-10 18:31 ` Andrew Haley
2004-03-10 18:35 ` Paul Koning
2004-03-10 18:37 ` Richard Henderson
2004-03-16 1:46 ` Mike Stump
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=20040310064001.GA7584@daikokuya.co.uk \
--to=neil@daikokuya.co.uk \
--cc=akpm@osdl.org \
--cc=gcc@gcc.gnu.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas.schlichter@web.de \
--cc=torvalds@osdl.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).