Hello. Following patch is a backport of PR lto/63704 for GCC 4.8 and 4.9 branches. Richi preapproved me the patch and I've run regtests on x86_64-linux-pc.
I'm going to install the patch. Thanks, Martin
diff --git a/gcc/ChangeLog b/gcc/ChangeLog index 779fef7..ab916b8 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,10 @@ +2015-01-15 Richard Biener <rguent...@suse.de> + Martin Liska <mli...@suse.cz> + + PR middle-end/63704 + * alias.c (mems_in_disjoint_alias_sets_p): Remove assert + and instead return false when !fstrict-aliasing. + 2014-10-21 Jakub Jelinek <ja...@redhat.com> PR tree-optimization/63563 diff --git a/gcc/alias.c b/gcc/alias.c index 434ae7a..79a3560 100644 --- a/gcc/alias.c +++ b/gcc/alias.c @@ -383,17 +383,9 @@ get_alias_set_entry (alias_set_type alias_set) static inline int mems_in_disjoint_alias_sets_p (const_rtx mem1, const_rtx mem2) { -/* Perform a basic sanity check. Namely, that there are no alias sets - if we're not using strict aliasing. This helps to catch bugs - whereby someone uses PUT_CODE, but doesn't clear MEM_ALIAS_SET, or - where a MEM is allocated in some way other than by the use of - gen_rtx_MEM, and the MEM_ALIAS_SET is not cleared. If we begin to - use alias sets to indicate that spilled registers cannot alias each - other, we might need to remove this check. */ - gcc_assert (flag_strict_aliasing - || (!MEM_ALIAS_SET (mem1) && !MEM_ALIAS_SET (mem2))); - - return ! alias_sets_conflict_p (MEM_ALIAS_SET (mem1), MEM_ALIAS_SET (mem2)); + return (flag_strict_aliasing + && ! alias_sets_conflict_p (MEM_ALIAS_SET (mem1), + MEM_ALIAS_SET (mem2))); } /* Insert the NODE into the splay tree given by DATA. Used by