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 ipa/68035] ipa performance issue when no procedures are present Date: Wed, 21 Oct 2015 08:18:00 -0000 [thread overview] Message-ID: <bug-68035-4-R9euViMGva@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-68035-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68035 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mliska at suse dot cz --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- We try to remove equivalent static const globals (thus unify them). But we should quickly arrive to the conclusion they are not equal, sth that doesn't work here. Eventually the hashing is also bad.
next prev parent reply other threads:[~2015-10-21 8:18 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-10-20 20:46 [Bug ipa/68035] New: " ncahill_alt at yahoo dot com 2015-10-21 8:18 ` rguenth at gcc dot gnu.org [this message] 2015-10-21 8:19 ` [Bug ipa/68035] [5/6 Regression] " rguenth 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-68035-4-R9euViMGva@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).