public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: giovannibajo@libero.it To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, giovannibajo@libero.it, gonz@ratloop.com, nobody@gcc.gnu.org Subject: Re: middle-end/10776: [3.3/3.4 regression] Large aggregate initializers with a single relocated entry causes excessive compile time regression Date: Thu, 15 May 2003 00:00:00 -0000 [thread overview] Message-ID: <20030515000001.7957.qmail@sources.redhat.com> (raw) Old Synopsis: [3.3 regression] Large aggregate initializers cause GCC to fail New Synopsis: [3.3/3.4 regression] Large aggregate initializers with a single relocated entry causes excessive compile time regression State-Changed-From-To: open->analyzed State-Changed-By: bajo State-Changed-When: Thu May 15 00:00:00 2003 State-Changed-Why: I have attached the reduced testcase as "pr10776.cpp.bz2". There is a huge compile time regression when the code is being compiled with -O[123], in 3.3 and 3.4 (and 3.2). The same code compiles in a decent amount of time (and memory usage) with 2.95. Notice that the whole regression can be eliminated by commenting a single relocated entry in the initializers (in the code, just comment the macro COMPILE_TIME_BUG defined at the beginning of the file). It looks like the optimizer is dieing because too much code is generated in the constructor/destructor initializer function. I think this is a middle-end bug, and I moved it to the middle-end category: probably GCC should be smarter and use memcpy whenever it's possible. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10776
reply other threads:[~2003-05-15 0:00 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=20030515000001.7957.qmail@sources.redhat.com \ --to=giovannibajo@libero.it \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=gonz@ratloop.com \ --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).