From: Joseph Myers <joseph@codesourcery.com>
To: "Uecker, Martin" <Martin.Uecker@med.uni-goettingen.de>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [C PATCH] Drop qualifiers during lvalue conversion
Date: Thu, 19 Nov 2020 20:53:42 +0000 [thread overview]
Message-ID: <alpine.DEB.2.22.394.2011192053290.147943@digraph.polyomino.org.uk> (raw)
In-Reply-To: <1605814464.12056.2.camel@med.uni-goettingen.de>
On Thu, 19 Nov 2020, Uecker, Martin wrote:
> Apparently I did not have enough coffee when
> generalizing this to the other qualifiers.
>
> Ok, with the following test?
OK.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2020-11-19 20:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-07 15:17 [C PATCH RFC] " Uecker, Martin
2020-11-09 23:41 ` Joseph Myers
2020-11-15 20:26 ` Uecker, Martin
2020-11-16 22:50 ` Joseph Myers
2020-11-19 6:34 ` [C PATCH] " Uecker, Martin
2020-11-19 18:58 ` Joseph Myers
2020-11-19 19:34 ` Uecker, Martin
2020-11-19 20:53 ` Joseph Myers [this message]
2020-11-23 13:55 ` Christophe Lyon
2020-11-23 15:26 ` Uecker, Martin
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=alpine.DEB.2.22.394.2011192053290.147943@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=Martin.Uecker@med.uni-goettingen.de \
--cc=gcc-patches@gcc.gnu.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).