From: Jakub Jelinek <jakub@redhat.com>
To: Richard Biener <rguenther@suse.de>
Cc: Bernd Edlinger <bernd.edlinger@hotmail.de>,
Jonathan Wakely <jwakely@redhat.com>,
Florian Weimer <fweimer@redhat.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
Jason Merrill <jason@redhat.com>,
Jeff Law <law@redhat.com>
Subject: Re: [PATCH] Add a new type attribute always_alias (PR79671)
Date: Thu, 06 Apr 2017 07:51:00 -0000 [thread overview]
Message-ID: <20170406075104.GA17461@tucnak> (raw)
In-Reply-To: <alpine.LSU.2.20.1704060925130.30715@zhemvz.fhfr.qr>
On Thu, Apr 06, 2017 at 09:47:10AM +0200, Richard Biener wrote:
> @@ -955,6 +960,7 @@ get_alias_set (tree t)
> Just be pragmatic here and make sure the array and its element
> type get the same alias set assigned. */
> else if (TREE_CODE (t) == ARRAY_TYPE
> + && ! TYPE_TYPELESS_STORAGE (t)
> && (!TYPE_NONALIASED_COMPONENT (t)
> || TYPE_STRUCTURAL_EQUALITY_P (t)))
> set = get_alias_set (TREE_TYPE (t));
> @@ -1094,6 +1100,15 @@ get_alias_set (tree t)
>
> TYPE_ALIAS_SET (t) = set;
>
> + if (TREE_CODE (t) == ARRAY_TYPE
> + && TYPE_TYPELESS_STORAGE (t))
Shouldn't TYPE_TYPELESS_STORAGE apply even for non-array types?
If somebody chooses to store anything in long long
__attribute__((typeless_storage)), so be it. Or what kind of complications
do you see for that?
Jakub
next prev parent reply other threads:[~2017-04-06 7:51 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
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 [this message]
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=20170406075104.GA17461@tucnak \
--to=jakub@redhat.com \
--cc=bernd.edlinger@hotmail.de \
--cc=fweimer@redhat.com \
--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).