public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/63704] -flto internal compiler error: in mems_in_disjoint_alias_sets_p, at alias.c:398 Date: Thu, 27 Nov 2014 09:52:00 -0000 [thread overview] Message-ID: <bug-63704-4-p24hnDAJXQ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-63704-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63704 --- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> --- Author: rguenth Date: Thu Nov 27 09:51:32 2014 New Revision: 218114 URL: https://gcc.gnu.org/viewcvs?rev=218114&root=gcc&view=rev Log: 2014-11-27 Richard Biener <rguenther@suse.de> PR middle-end/63704 * alias.c (mems_in_disjoint_alias_sets_p): Remove assert and instead return false when !fstrict-aliasing. Modified: trunk/gcc/ChangeLog trunk/gcc/alias.c
next prev parent reply other threads:[~2014-11-27 9:52 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-63704-4@http.gcc.gnu.org/bugzilla/> 2014-11-03 9:16 ` rguenth at gcc dot gnu.org 2014-11-26 13:40 ` rguenth at gcc dot gnu.org 2014-11-27 9:51 ` rguenth at gcc dot gnu.org 2014-11-27 9:52 ` rguenth at gcc dot gnu.org [this message] 2015-01-15 16:03 ` marxin at gcc dot gnu.org
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=bug-63704-4-p24hnDAJXQ@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /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: linkBe 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).