public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Daniel Berlin <dberlin@dberlin.org> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c/7344: performance regression on huge case statements Date: Thu, 10 Oct 2002 19:16:00 -0000 [thread overview] Message-ID: <20021011021603.27194.qmail@sources.redhat.com> (raw) The following reply was made to PR c/7344; it has been noted by GNATS. From: Daniel Berlin <dberlin@dberlin.org> To: Nathanael Nerode <neroden@twcny.rr.com> Cc: gcc-gnats@gcc.gnu.org, rschiele@uni-mannheim.de, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org, jh@suse.cz Subject: Re: c/7344: performance regression on huge case statements Date: Thu, 10 Oct 2002 22:08:47 -0400 On Thursday, October 10, 2002, at 10:04 PM, Nathanael Nerode wrote: > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit- > trail&database=gcc&pr=7344 > > I'm tired of investigating this, but it seems likely that the problem > was introduced with the introduction of et-forest.c, since that's > where the loop is. This was introduced by Pavel Nejedly and committed > to mainline by Jan Hubicka (along with most of the surrounding code). > > (So that's why I'm ccing you; it looks like you caused it, so maybe > you can figure out how to fix it. :-/) > As I mentioned, this is likely a known problem, with a known fix. Jan, if you don't have plans to make it constant time soon, i suggest we cache the info using the patch that is on the tree-ssa branch. > --Nathanael > >
next reply other threads:[~2002-10-11 2:16 UTC|newest] Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-10-10 19:16 Daniel Berlin [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-04-08 13:15 hubicka 2003-01-08 2:00 bangerth 2002-10-18 6:56 Robert Schiele 2002-10-18 6:16 Nathanael Nerode 2002-10-17 6:46 Robert Schiele 2002-10-17 6:36 Nathanael Nerode 2002-10-17 6:36 Jan Hubicka 2002-10-17 6:26 Michael Matz 2002-10-17 6:06 Nathanael Nerode 2002-10-15 12:16 Jan Hubicka 2002-10-15 11:56 Kaveh R. Ghazi 2002-10-11 13:26 Richard Henderson 2002-10-11 12:56 Jan Hubicka 2002-10-11 10:26 Richard Henderson 2002-10-11 8:06 Jan Hubicka 2002-10-11 7:26 Jan Hubicka 2002-10-11 2:26 Jan Hubicka 2002-10-10 19:56 Nathanael Nerode 2002-10-10 19:26 Daniel Berlin 2002-10-10 19:16 Nathanael Nerode 2002-10-10 19:16 Daniel Berlin 2002-10-10 19:06 Nathanael Nerode 2002-10-10 19:06 Nathanael Nerode 2002-10-10 18:56 Nathanael Nerode 2002-07-17 13:16 Gerald Pfeifer 2002-07-17 10:46 rschiele
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=20021011021603.27194.qmail@sources.redhat.com \ --to=dberlin@dberlin.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).