From: David Lamparter <equinox@diac24.net>
To: Martin Sebor <msebor@gmail.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] c: don't drop typedef information in casts
Date: Wed, 10 Mar 2021 20:06:18 +0100 [thread overview]
Message-ID: <YEkYqmKvcZ7jrGDY@eidolon.nox.tf> (raw)
In-Reply-To: <YEkXuFKXHb9rsIH5@eidolon.nox.tf>
On Wed, Mar 10, 2021 at 08:02:16PM +0100, David Lamparter wrote:
> Also, in seeing your response re. the volatile, it occured to me that
> stripping qualifiers on a typedef and still calling it the typedef is
> unhelpful. Ideally, my goal is:
>
> typedef int i;
> typedef const int ci;
> typeof((i)x) = i
> typeof((ci)x) = int (<-- w/ my patch = ci; this is confusing)
Clarification: with the current patch, the type of (ci)x is *called*
"ci", but doesn't actually have the const qualifier. That's the
confusing part. The const (or volatile) is stripped off the typedef in
the added build_qualified_type() call, but that now-different type is
still referred to as "ci"...
> typeof((const i)x) = i
next prev parent reply other threads:[~2021-03-10 19:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 1:28 David Lamparter
2021-03-10 1:46 ` David Lamparter
2021-03-10 17:01 ` Martin Sebor
2021-03-10 19:02 ` David Lamparter
2021-03-10 19:06 ` David Lamparter [this message]
2021-03-12 3:08 ` [PATCH v2] " David Lamparter
2021-03-12 8:35 ` Jakub Jelinek
2021-03-15 18:14 ` David Lamparter
2021-03-15 18:16 ` [PATCH v3] " David Lamparter
2021-05-07 16:09 [PATCH] " David Lamparter
2021-05-18 11:13 ` David Lamparter
2021-05-18 20:32 ` Joseph Myers
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=YEkYqmKvcZ7jrGDY@eidolon.nox.tf \
--to=equinox@diac24.net \
--cc=gcc-patches@gcc.gnu.org \
--cc=msebor@gmail.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 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).