Re: indirect_ref_may_alias_decl_p fix

2019-06-14 Thread Jan Hubicka
> Hi Jan, > > > I am testing the following patch which solves the bogus warning in > > tree-ssa-forwprop.c and -m32 and plan to commit it as obvoius to unbreak > > bootstrap once testing converges. Previously we did not get here wince > > we got mismatch between TMR type and decl type but same cod

Re: indirect_ref_may_alias_decl_p fix

2019-06-13 Thread Rainer Orth
Hi Jan, > I am testing the following patch which solves the bogus warning in > tree-ssa-forwprop.c and -m32 and plan to commit it as obvoius to unbreak > bootstrap once testing converges. Previously we did not get here wince > we got mismatch between TMR type and decl type but same code is present

Re: indirect_ref_may_alias_decl_p fix

2019-06-13 Thread Jan Hubicka
Hi, I am testing the following patch which solves the bogus warning in tree-ssa-forwprop.c and -m32 and plan to commit it as obvoius to unbreak bootstrap once testing converges. Previously we did not get here wince we got mismatch between TMR type and decl type but same code is present in indirect_

Re: indirect_ref_may_alias_decl_p fix

2019-06-13 Thread Jan Hubicka
Hi, actually since Rainer's testcase has TARGET_MEM_REF I think the problem may be due to fact that we now can get TARGET_MEM_REF ofsetting the array housed in decl while previously we gave up on types mismatch. Does the following help? Index: tree-ssa-alias.c =

Re: indirect_ref_may_alias_decl_p fix

2019-06-13 Thread Rainer Orth
Hi Christophe, > Since this was committed (r272247), I've noticed a failure to build > glibc-2.29 for aarch64: > #'target_mem_ref' not supported by expression#'pmap_rmt.c: In function > 'clnt_broadcast': > pmap_rmt.c:298:19: error: may be used uninitialized in this function > [-Werror=maybe-unini

Re: indirect_ref_may_alias_decl_p fix

2019-06-13 Thread Jan Hubicka
> Hi! > > Since this was committed (r272247), I've noticed a failure to build > glibc-2.29 for aarch64: > #'target_mem_ref' not supported by expression#'pmap_rmt.c: In function > 'clnt_broadcast': > pmap_rmt.c:298:19: error: may be used uninitialized in this function > [-Werror=maybe-uninitialize

Re: indirect_ref_may_alias_decl_p fix

2019-06-13 Thread Christophe Lyon
On Thu, 13 Jun 2019 at 14:29, Jan Hubicka wrote: > > > > 1) indirect_refs_may_alias_decl_p passing ref2_is_decl as true to > > > aliasing_component_refs_p. > > > > > > This makes aliasing_component_refs_p to assume that all access paths > > > conflicting with REF2 must start by type o

Re: indirect_ref_may_alias_decl_p fix

2019-06-13 Thread Jan Hubicka
> > 1) indirect_refs_may_alias_decl_p passing ref2_is_decl as true to > > aliasing_component_refs_p. > > > > This makes aliasing_component_refs_p to assume that all access paths > > conflicting with REF2 must start by type of BASE2 or its subtype. > > > > IMO this is not quite r

Re: indirect_ref_may_alias_decl_p fix

2019-06-13 Thread Richard Biener
On Thu, 13 Jun 2019, Jan Hubicka wrote: > Hi, > after spending some time on the view converting MEM_REFs, I noticed that > most of reasons we give up on view converts is not actually MEM_REF created > but test > same_type_for_tbaa (TREE_TYPE (dbase2), TREE_TYPE (base2)) > in indirect_ref_may_alia