This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug middle-end/27733] [4.1/4.2 Regression] Large compile time regression
- From: "sje at cup dot hp dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 8 Jun 2006 15:11:47 -0000
- Subject: [Bug middle-end/27733] [4.1/4.2 Regression] Large compile time regression
- References: <bug-27733-276@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #13 from sje at cup dot hp dot com 2006-06-08 15:11 -------
The proposed patch does fix the compilation time problem on hppa64-hp-hpux11.11
but I am confused about how the cache works. Without the patch, the compile
takes 15 to 20 minutes but I do wind up generating a sequence of instructions
instead of a call to __divdi3. With the patch, I get a very fast compilation,
but I also get a call to __divdi3 instead of the code sequence. Why does
caching results change the behaviour? Caches (in general) should speed things
up by saving previous/intermediate results, but shouldn't change the ultimate
answer. This seems to be doing something different.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27733