[Bug c++/70768] [6/7 Regression] Increased compilation time

2017-03-09 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70768

Jakub Jelinek  changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution|--- |INVALID

--- Comment #11 from Jakub Jelinek  ---
Closing as not a bug, if you compare the same preprocessed sources, there is no
regression, if you compare different sources, the headers are changing, new
templates etc. are being added all the time.

[Bug c++/70768] [6/7 Regression] Increased compilation time

2017-01-25 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70768

--- Comment #10 from Jakub Jelinek  ---
When comparing r224581 (the first cc1plus that doesn't ICE on the gcc5
preprocessed source) with r244763 cc1plus on the same source (though, both are
checking builds), the latter eats less memory, not more.

[Bug c++/70768] [6/7 Regression] Increased compilation time

2017-01-25 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70768

Jakub Jelinek  changed:

   What|Removed |Added

 CC||jakub at gcc dot gnu.org

--- Comment #9 from Jakub Jelinek  ---
Well, you are comparing apples and oranges here, given that for each gcc
version you have different preprocessed source, and libstdc++ keeps changing,
it might very well be that in the headers there is just more templates etc.  It
can be even seen on the size of the preprocessed sources, the 5.3 is 300KB
shorter.
Trying to bisect the memory consumption is not possible, because r222000 up to
r224000 + plus something all ICE on the gcc 5 preprocessed source.

[Bug c++/70768] [6/7 Regression] Increased compilation time

2016-12-21 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70768

Jakub Jelinek  changed:

   What|Removed |Added

   Target Milestone|6.3 |6.4

--- Comment #8 from Jakub Jelinek  ---
GCC 6.3 is being released, adjusting target milestone.

[Bug c++/70768] [6/7 Regression] Increased compilation time

2016-08-22 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70768

--- Comment #7 from Richard Biener  ---
GCC 6.2 is being released, adjusting target milestone.

[Bug c++/70768] [6/7 Regression] Increased compilation time

2016-08-22 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70768

Richard Biener  changed:

   What|Removed |Added

   Target Milestone|6.2 |6.3

--- Comment #6 from Richard Biener  ---
GCC 6.2 is being released, adjusting target milestone.

[Bug c++/70768] [6/7 Regression] Increased compilation time

2016-07-08 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70768

Richard Biener  changed:

   What|Removed |Added

   Priority|P3  |P2

[Bug c++/70768] [6/7 Regression] Increased compilation time

2016-04-25 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70768

Richard Biener  changed:

   What|Removed |Added

   Keywords||compile-time-hog,
   ||memory-hog
 Status|RESOLVED|REOPENED
   Last reconfirmed||2016-04-25
 Resolution|INVALID |---
   Target Milestone|--- |6.2
Summary|Increased compilation time  |[6/7 Regression] Increased
   ||compilation time
 Ever confirmed|0   |1

--- Comment #5 from Richard Biener  ---
I think this kind of memory usage increase is a bug.