From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Sparse Mailing-list <linux-sparse@vger.kernel.org>
Subject: Re: [PATCH] casts should drop qualifiers
Date: Thu, 19 Nov 2020 09:11:37 +0100 [thread overview]
Message-ID: <20201119081137.lxmry66fbww3rhrz@ltop.local> (raw)
In-Reply-To: <CAHk-=wgYd+L_FVX7uny9_i2hNqB6=EryCKV4wtFwa+scaYnmHw@mail.gmail.com>
On Wed, Nov 18, 2020 at 04:58:26PM -0800, Linus Torvalds wrote:
> On Wed, Nov 18, 2020 at 1:30 PM Luc Van Oostenryck
> <luc.vanoostenryck@gmail.com> wrote:
> >
> > If I read the standard correctly (big 'if'), in:
> > volatile int x;
> > typeof(++x) y;
> > 'y' should have the type 'volatile int' and GCC interpret it so.
>
> That sounds extremely odd to me. I think it should have the same type
> as "x += 1" or "x = x+1", no?
Yes, but both cases are explicitly excluded from C's 6.3.2.1 where
lvalue-conversion is defined. This whole section was very confusing
to me but the note 112) in n1570's 6.5.16.1 is somehow clearer.
So yes, I'll drop this patch (I should have tagged it as RFC anyway).
Thanks for the feedback.
-- Luc.
prev parent reply other threads:[~2020-11-19 8:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1605437478.5370.9.camel@med.uni-goettingen.de>
[not found] ` <CAFiYyc1-qtU+4Tj3mkz=c608zeP8feyuD6UyRhQv19qjKjJcvg@mail.gmail.com>
[not found] ` <20201116111056.GA3121378@hirez.programming.kicks-ass.net>
[not found] ` <CAHk-=wh_kn11vXfi2Ns8E4F0GgmUprQtD-=RnU6Eg+N7coY5gw@mail.gmail.com>
2020-11-17 19:47 ` Re: typeof and operands in named address spaces Linus Torvalds
2020-11-17 21:28 ` [PATCH] casts should drop qualifiers Luc Van Oostenryck
2020-11-17 23:22 ` Linus Torvalds
2020-11-17 23:50 ` Luc Van Oostenryck
2020-11-18 18:31 ` Linus Torvalds
2020-11-18 19:17 ` Luc Van Oostenryck
2020-11-18 19:51 ` Linus Torvalds
2020-11-18 21:30 ` Luc Van Oostenryck
2020-11-19 0:58 ` Linus Torvalds
2020-11-19 8:11 ` Luc Van Oostenryck [this message]
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=20201119081137.lxmry66fbww3rhrz@ltop.local \
--to=luc.vanoostenryck@gmail.com \
--cc=linux-sparse@vger.kernel.org \
--cc=torvalds@linux-foundation.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 NNTP newsgroup(s).