[Bug bootstrap/16177] [3.5 Regression] Strange memory requirements when bootstrapping GCC 3.5 with GCC 3.5
pinskia at gcc dot gnu dot org
gcc-bugzilla@gcc.gnu.org
Thu Jun 24 17:16:00 GMT 2004
------- Additional Comments From pinskia at gcc dot gnu dot org 2004-06-24 16:52 -------
I see the same problem on i686-unknown-openbsd3.1, this happened after Steven B. committed his
patch for adding the K6 (or was it the pentiumpro one) dfa scheduler patch. And then when the tree-
ssa merged it was even higher but in stage1 this time instead of stage2. And the memory for right
after tree-ssa merge came from the switch tables were huge.
--
What |Removed |Added
----------------------------------------------------------------------------
CC| |steven at gcc dot gnu dot
| |org
Status|UNCONFIRMED |NEW
Ever Confirmed| |1
GCC build triplet|i386-unknown-freebsd4.10 |
GCC host triplet|i386-unknown-freebsd4.10 |
GCC target triplet|i386-unknown-freebsd4.10 |
Keywords| |build, memory-hog
Last reconfirmed|0000-00-00 00:00:00 |2004-06-24 16:52:11
date| |
Summary|Strange memory requirements |[3.5 Regression] Strange
|when bootstrapping GCC 3.5 |memory requirements when
|with GCC 3.5 |bootstrapping GCC 3.5 with
| |GCC 3.5
Target Milestone|--- |3.5.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16177
More information about the Gcc-bugs
mailing list