From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 88456 invoked by alias); 6 Apr 2017 07:51:13 -0000 Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org Received: (qmail 88439 invoked by uid 89); 6 Apr 2017 07:51:11 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS autolearn=ham version=3.3.2 spammy= X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 06 Apr 2017 07:51:11 +0000 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 2B16361D02; Thu, 6 Apr 2017 07:51:11 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 2B16361D02 Authentication-Results: ext-mx10.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com Authentication-Results: ext-mx10.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=jakub@redhat.com DKIM-Filter: OpenDKIM Filter v2.11.0 mx1.redhat.com 2B16361D02 Received: from tucnak.zalov.cz (ovpn-116-72.ams2.redhat.com [10.36.116.72]) by smtp.corp.redhat.com (Postfix) with ESMTPS id BE8309A35C; Thu, 6 Apr 2017 07:51:10 +0000 (UTC) Received: from tucnak.zalov.cz (localhost [127.0.0.1]) by tucnak.zalov.cz (8.15.2/8.15.2) with ESMTP id v367p87Y018750; Thu, 6 Apr 2017 09:51:08 +0200 Received: (from jakub@localhost) by tucnak.zalov.cz (8.15.2/8.15.2/Submit) id v367p5PR018749; Thu, 6 Apr 2017 09:51:05 +0200 Date: Thu, 06 Apr 2017 07:51:00 -0000 From: Jakub Jelinek To: Richard Biener Cc: Bernd Edlinger , Jonathan Wakely , Florian Weimer , GCC Patches , Jason Merrill , Jeff Law Subject: Re: [PATCH] Add a new type attribute always_alias (PR79671) Message-ID: <20170406075104.GA17461@tucnak> Reply-To: Jakub Jelinek References: <6a5109d6-81fb-c36c-e525-b2ed984760dc@redhat.com> <21E940B5-C8C4-4A86-8C15-49A86547DD87@suse.de> <20170405160333.GR4425@redhat.com> <20170405160849.GV17461@tucnak> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.7.1 (2016-10-04) X-IsSubscribed: yes X-SW-Source: 2017-04/txt/msg00265.txt.bz2 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