From: Jakub Jelinek <jakub@redhat.com>
To: Bernd Edlinger <bernd.edlinger@hotmail.de>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
Jason Merrill <jason@redhat.com>,
"Marc Glisse <marc.glisse@inria.fr>; Jakub Jelinek
<jakub@redhat.com>; Jonathan Wakely" <jwakely@redhat.com>,
Richard Biener <rguenther@suse.de>,
Jeff Law <law@redhat.com>
Subject: Re: [PATCH] Add a new type attribute always_alias (PR79671)
Date: Wed, 05 Apr 2017 13:28:00 -0000 [thread overview]
Message-ID: <20170405132832.GS17461@tucnak> (raw)
In-Reply-To: <AM4PR0701MB216292327A207737064C3CA3E40A0@AM4PR0701MB2162.eurprd07.prod.outlook.com>
On Wed, Apr 05, 2017 at 09:46:09AM +0000, Bernd Edlinger wrote:
> this is related to the P1 codegen bug PR79671:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79671
>
> Therefore I would like to add this now although
> the trunk is already at in stage 4.
>
> I propose to add a new type attribute always_alias that
> works like may_alias but unlike may_alias it should
> also make instances alias anything. It is also exposed
> in C/C++ as __attribute__((always_alias)).
I have just two small comments, for review IMHO want agreement
between Jason and Richard on this.
One thing is whether it is a good idea to keep this info in the IL
as an attribute, especially when you add it automatically in the
C++ FE. I see e.g. 25 spare bits in tree_type_common. Don't say we
need to waste them, but I'd say in C++ unsigned char arrays are fairly
common and thus not having to create the attribute for them each time
and look it up might be beneficial.
Also, wonder if you need to mark all types containing such arrays,
if you couldn't just set that flag in C++ on unsigned char/std::byte
arrays (and on anything with that attribute), have that imply alias set
0 on it and then let the rest of alias machinery handle aggregate types
containing such fields.
Jakub
next prev parent reply other threads:[~2017-04-05 13:28 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-05 9:46 Bernd Edlinger
2017-04-05 13:28 ` Jakub Jelinek [this message]
2017-04-05 15:20 ` Richard Biener
2017-04-05 17:41 ` Bernd Edlinger
2017-04-05 20:18 ` Jason Merrill
2017-04-05 20:46 ` Bernd Edlinger
2017-04-05 22:54 ` Pedro Alves
2017-04-06 10:08 ` Jonathan Wakely
2017-04-06 7:23 ` Richard Biener
2017-04-05 15:27 ` Bernd Edlinger
2017-04-05 15:29 ` Jakub Jelinek
2017-04-05 14:50 ` Florian Weimer
2017-04-05 15:23 ` Richard Biener
2017-04-05 15:38 ` Bernd Edlinger
2017-04-05 16:03 ` Jonathan Wakely
2017-04-05 16:08 ` Jakub Jelinek
2017-04-05 17:23 ` Bernd Edlinger
2017-04-05 21:02 ` Bernd Edlinger
2017-04-05 23:17 ` Sandra Loosemore
2017-04-06 5:40 ` Jakub Jelinek
2017-04-06 7:47 ` Richard Biener
2017-04-06 7:51 ` Jakub Jelinek
2017-04-06 7:55 ` Richard Biener
2017-04-06 14:11 ` Bernd Edlinger
2017-04-06 14:17 ` Florian Weimer
2017-04-06 14:23 ` Richard Biener
2017-04-06 14:43 ` Jonathan Wakely
2017-04-06 14:51 ` Florian Weimer
2017-04-06 15:05 ` Jakub Jelinek
2017-04-06 15:10 ` Florian Weimer
2017-04-06 19:13 ` Richard Biener
2017-04-11 10:43 ` Florian Weimer
2017-04-11 10:48 ` Richard Biener
2017-04-06 17:39 ` Bernd Edlinger
2017-04-06 17:48 ` Florian Weimer
2017-04-06 18:12 ` Bernd Edlinger
2017-04-06 18:19 ` Florian Weimer
2017-04-06 18:49 ` Bernd Edlinger
2017-04-06 19:05 ` Florian Weimer
2017-04-06 19:20 ` Bernd Edlinger
2017-04-07 6:47 ` Richard Biener
2017-04-07 12:58 ` Bernd Edlinger
2017-04-06 19:16 ` Richard Biener
2017-04-07 6:56 ` Florian Weimer
2017-04-07 8:01 ` Richard Biener
2017-04-06 19:14 ` Richard Biener
2017-04-06 19:51 ` Bernd Edlinger
2017-04-06 14:22 ` Richard Biener
2017-04-06 21:00 ` Bernd Edlinger
2017-04-07 6:54 ` Richard Biener
2017-04-07 13:37 ` Bernd Edlinger
2017-04-07 15:10 ` Richard Biener
2017-04-07 15:33 ` Bernd Edlinger
2017-04-07 20:22 ` Jason Merrill
2017-04-10 12:50 ` Richard Biener
2017-04-10 14:41 ` Jason Merrill
2017-04-10 15:31 ` Richard Biener
2017-04-10 16:35 ` Jason Merrill
2017-04-11 10:32 ` Richard Biener
2017-04-11 11:53 ` Richard Biener
2017-04-11 13:35 ` Richard Biener
2017-04-11 18:47 ` Jason Merrill
2017-04-10 21:40 ` Pedro Alves
2017-04-11 7:37 ` Richard Biener
2017-04-06 20:20 ` Bernd Edlinger
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=20170405132832.GS17461@tucnak \
--to=jakub@redhat.com \
--cc=bernd.edlinger@hotmail.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.com \
--cc=jwakely@redhat.com \
--cc=law@redhat.com \
--cc=rguenther@suse.de \
/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).