From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <jit-return-759-listarch-jit=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 54082 invoked by alias); 9 Jul 2015 21:23:01 -0000
Mailing-List: contact jit-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Post: <mailto:jit@gcc.gnu.org>
List-Help: <mailto:jit-help@gcc.gnu.org>
List-Subscribe: <mailto:jit-subscribe@gcc.gnu.org>
Sender: jit-owner@gcc.gnu.org
Received: (qmail 54070 invoked by uid 89); 9 Jul 2015 21:23:01 -0000
Authentication-Results: sourceware.org; auth=none
X-Virus-Checked: by ClamAV 0.98.7 on sourceware.org
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-1.5 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RP_MATCHES_RCVD,SPF_HELO_PASS autolearn=no version=3.3.2
X-Spam-Status: No, score=-1.5 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RP_MATCHES_RCVD,SPF_HELO_PASS autolearn=no version=3.3.2
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on sourceware.org
X-Spam-Level: 
X-HELO: mx1.redhat.com
Message-ID: <1436476508.24803.168.camel@surprise>
Subject: Re: Filed PR jit/66812 for the code generation issue
From: David Malcolm <dmalcolm@redhat.com>
To: Dibyendu Majumdar <mobile@majumdar.org.uk>
Cc: jit@gcc.gnu.org
Date: Thu, 01 Jan 2015 00:00:00 -0000
In-Reply-To: <1436476001.24803.165.camel@surprise>
References: 
	<CACXZuxc3z92zKFWhNBU4a0LDxhyNRiZcbMf83HVYkOn-7CScDQ@mail.gmail.com>
	 <CACXZuxfKRkEzSjzPCvpSvL0EcryEofyL-xjgJLxByNQDNpBjTg@mail.gmail.com>
	 <CACXZuxez_fzRYnmZ-traUo2uOr5fU4kC3VrEbWYC8UWDnvEa_A@mail.gmail.com>
	 <CACXZuxfb+OOW6Mc4GPBfUaE4VSAhOmy=f1KCXxLmXq=Mw7DdyQ@mail.gmail.com>
	 <1436365266.24803.65.camel@surprise> <1436367926.24803.71.camel@surprise>
	 <1436369443.24803.75.camel@surprise> <1436377619.24803.97.camel@surprise>
	 <CACXZuxdi+M+Ttgszi9hqDvT1V-NrQKxD3dTM6TOO2m3dzaz34g@mail.gmail.com>
	 <1436382217.24803.101.camel@surprise>
	 <CACXZuxcj_CRjOUy6TfexL9S9TmVRUB1Zpd9J8-Awj4ritUUbFA@mail.gmail.com>
	 <1436385256.24803.107.camel@surprise>
	 <CACXZuxcs0Zex=jsRubnNZ+HXPORULn8_j4vH4aw1tNnmJrErhQ@mail.gmail.com>
	 <CACXZuxcbfdAmsvcLx_nFC3PynjcDBTgF1D=tZnHaJtF1_jfpPg@mail.gmail.com>
	 <1436469764.24803.156.camel@surprise>
	 <CACXZuxdP=W1dmW_=xoY2u60Wafku_oOtBfLPZP+rub2N_qrLhQ@mail.gmail.com>
	 <1436476001.24803.165.camel@surprise>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.68 on 10.5.11.27
X-SW-Source: 2015-q3/txt/msg00059.txt.bz2

On Thu, 2015-07-09 at 17:06 -0400, David Malcolm wrote:

(snip)

> The fix will be to implement the LANG_HOOKS_GET_ALIAS_SET internal GCC
> API thus giving libgccjit some rules about aliasing.  Some options:
> 
> (i) make it identical to C.
> (ii) give the client code some control over this
> 
> My initial gut feeling is to go with (i).

...or possibly to do what the link-time optimizer does, which is to use
this internal API:

/* Return the typed-based alias set for T, which may be an expression
   or a type.  Return -1 if we don't do anything special.  */

alias_set_type
gimple_get_alias_set (tree t)

which does almost all of what the C frontend does.  I'll try to cook up
a patch.