public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Volker Reichelt <reichelt@igpm.rwth-aachen.de> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: optimization/6798: [3.2/3.3/3.4 regression] very long compile time with large case-statement Date: Wed, 12 Mar 2003 12:16:00 -0000 [thread overview] Message-ID: <20030312121600.10076.qmail@sources.redhat.com> (raw) The following reply was made to PR optimization/6798; it has been noted by GNATS. From: Volker Reichelt <reichelt@igpm.rwth-aachen.de> To: s.bosscher@student.tudelft.nl, gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, eggert@twinsun.com Cc: bangerth@ticam.utexas.edu Subject: Re: optimization/6798: [3.2/3.3/3.4 regression] very long compile time with large case-statement Date: Wed, 12 Mar 2003 13:07:05 +0100 (CET) On 11 Mar, Steven Bosscher wrote: > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6798 > > Volker, you said you saw this on Linux? I don't see this bug on > i586-linux, > so I hope you can confirm this so we can close this PR, or else we > should try > to find out if this is a target-specific problem. > > Greetz > Steven Sorry, but that was Wolfgang and not me (I just put the code into an attachment): | State-Changed-From-To: feedback->open | State-Changed-By: reichelt | State-Changed-When: Wed Jan 15 02:18:06 2003 | State-Changed-Why: | Attachment received. | State-Changed-From-To: open->analyzed | State-Changed-By: bangerth | State-Changed-When: Wed Jan 15 08:27:38 2003 | State-Changed-Why: | I can also reproduce this on a Linux machine. The testcase | is basically an enormous yacc-generated switch-statement, | with about 2000 cases and a lot of cross-jumping. I killed | the compilation after about 10 minutes. Regards, Volker
next reply other threads:[~2003-03-12 12:16 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-12 12:16 Volker Reichelt [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-03-12 14:46 Wolfgang Bangerth 2003-03-11 20:56 Steven Bosscher 2003-02-19 13:16 Steven Bosscher 2003-01-15 16:27 bangerth
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=20030312121600.10076.qmail@sources.redhat.com \ --to=reichelt@igpm.rwth-aachen.de \ --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).