public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: rth@gcc.gnu.org To: eggert@twinsun.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, rth@gcc.gnu.org Subject: Re: optimization/6798: [3.2/3.3 regression] very long compile time with large case-statement Date: Sun, 16 Mar 2003 23:16:00 -0000 [thread overview] Message-ID: <20030316231652.18597.qmail@sources.redhat.com> (raw) Synopsis: [3.2/3.3 regression] very long compile time with large case-statement Responsible-Changed-From-To: unassigned->rth Responsible-Changed-By: rth Responsible-Changed-When: Sun Mar 16 23:16:52 2003 Responsible-Changed-Why: . State-Changed-From-To: analyzed->closed State-Changed-By: rth State-Changed-When: Sun Mar 16 23:16:52 2003 State-Changed-Why: Backported patch to 3.3 branch. 2003-02-15 Richard Henderson <rth@redhat.com> * cfgcleanup.c: Include params.h. (try_crossjump_bb): Use PARAM_MAX_CROSSJUMP_EDGES. Fix test for too many outgoing edges from a block. * Makefile.in (cfgcleanup.o): Depend on PARAMS_H. * params.def (max-crossjump-edges): New. * doc/invoke.texi: Document it. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6798
reply other threads:[~2003-03-16 23:16 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030316231652.18597.qmail@sources.redhat.com \ --to=rth@gcc.gnu.org \ --cc=eggert@twinsun.com \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.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).