This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: 3.3 compile time regression (22400%)
- From: "John David Anglin" <dave at hiauly1 dot hia dot nrc dot ca>
- To: s dot bosscher at student dot tudelft dot nl (Steven Bosscher)
- Cc: matz at suse dot de, gcc at gcc dot gnu dot org
- Date: Tue, 18 Mar 2003 19:40:24 -0500 (EST)
- Subject: Re: 3.3 compile time regression (22400%)
> > Yikes! Such behaviour would normally only be expected from fully
> > connected CFGs if at all, or CFGs with big tree-width, but normal C++ code
> > even if using exceptions doesn't result in a CFG _that_ ugly. Do you care
> > enough to reduce the file a bit (so you have a chance to play with it
> > without becoming dust), create a profileable cc1plus and post the
> > hotspots?
>
> Is there a PR for this issue now? This issue obvioulsy is quite bad for
> a 3.3 release, but I couldn't find a PR for it.
Not that I am aware of. I am doing final testing of a patch to fix
the backend problem that was the subject of PR10062 but the fix doesn't
address the above problem. We go from about a 90s compilation with
-fno-inline, to 5.4 hours with -fno-default-inline, to virtual memory
exhausted with no inline option specified. The amount of virtual memory
required for the later probably exceeds the maximum data size possible
on the PA for the 32-bit runtime. For my last try, the maximum data
size was set to 768MB.
Dave
--
J. David Anglin dave dot anglin at nrc-cnrc dot gc dot ca
National Research Council of Canada (613) 990-0752 (FAX: 952-6602)