public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "aoliva at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/52001] [4.7 Regression] Huge compile-time regression with var-tracking Date: Sat, 25 Feb 2012 12:29:00 -0000 [thread overview] Message-ID: <bug-52001-4-L9qZ9y8rW6@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-52001-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52001 --- Comment #6 from Alexandre Oliva <aoliva at gcc dot gnu.org> 2012-02-25 12:09:48 UTC --- Author: aoliva Date: Sat Feb 25 12:09:41 2012 New Revision: 184572 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=184572 Log: PR debug/52001 * alias.c (refs_newer_value_cb, refs_newer_value_p): New. (get_addr): Walk canonical value's locs. Avoid returning VALUEs and locs that reference values newer than the non-canonical value at hand. Return the canonical value as a worst case. (memrefs_conflict_p): Walk canonical value's locs. Modified: trunk/gcc/ChangeLog trunk/gcc/alias.c
next prev parent reply other threads:[~2012-02-25 12:11 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-01-25 20:20 [Bug debug/52001] New: [4.7 reegression] " rsandifo at gcc dot gnu.org 2012-01-25 20:23 ` [Bug debug/52001] " pinskia at gcc dot gnu.org 2012-01-25 20:24 ` pinskia at gcc dot gnu.org 2012-01-26 16:13 ` [Bug debug/52001] [4.7 Regression] " jakub at gcc dot gnu.org 2012-01-27 10:07 ` jakub at gcc dot gnu.org 2012-01-27 10:08 ` jakub at gcc dot gnu.org 2012-02-25 12:11 ` aoliva at gcc dot gnu.org 2012-02-25 12:29 ` aoliva at gcc dot gnu.org [this message] 2012-02-29 11:36 ` gjl at gcc dot gnu.org 2012-03-01 17:00 ` aoliva 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-52001-4-L9qZ9y8rW6@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).