public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
* Re: optimization/8361: [3.3/3.4 regression] C++ compile-time performance regression
@ 2003-03-23 9:16 Steven Bosscher
0 siblings, 0 replies; 5+ messages in thread
From: Steven Bosscher @ 2003-03-23 9:16 UTC (permalink / raw)
To: nobody; +Cc: gcc-prs
The following reply was made to PR optimization/8361; it has been noted by GNATS.
From: Steven Bosscher <s.bosscher@student.tudelft.nl>
To: pfeifer@dbai.tuwien.ac.at, gcc-gnats@gcc.gnu.org,
gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-prs@gcc.gnu.org
Cc:
Subject: Re: optimization/8361: [3.3/3.4 regression] C++ compile-time performance
regression
Date: Sun, 23 Mar 2003 10:10:03 +0100
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8361
Janis did some more timing:
http://gcc.gnu.org/ml/gcc/2003-03/msg01425.html
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: optimization/8361: [3.3/3.4 regression] C++ compile-time performance regression
@ 2003-05-01 11:36 Andrew Pinski
0 siblings, 0 replies; 5+ messages in thread
From: Andrew Pinski @ 2003-05-01 11:36 UTC (permalink / raw)
To: nobody; +Cc: gcc-prs
The following reply was made to PR optimization/8361; it has been noted by GNATS.
From: Andrew Pinski <pinskia@physics.uc.edu>
To: pfeifer@dbai.tuwien.ac.at, gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org,
nobody@gcc.gnu.org, gcc-prs@gcc.gnu.org
Cc: Andrew Pinski <pinskia@physics.uc.edu>
Subject: Re: optimization/8361: [3.3/3.4 regression] C++ compile-time performance regression
Date: Thu, 1 May 2003 07:26:47 -0400
Is there any way, I can get the non-preprocessed code, because the
preprocess code produces errors in the system headers.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-
trail&database=gcc&pr=8361
Thanks,
Andrew Pinski
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: optimization/8361: [3.3/3.4 regression] C++ compile-time performance regression
@ 2003-03-24 15:14 Gerald Pfeifer
0 siblings, 0 replies; 5+ messages in thread
From: Gerald Pfeifer @ 2003-03-24 15:14 UTC (permalink / raw)
To: nobody; +Cc: gcc-prs
The following reply was made to PR optimization/8361; it has been noted by GNATS.
From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, gcc-bugs@gcc.gnu.org
Cc: Steven Bosscher <s.bosscher@student.tudelft.nl>
Subject: Re: optimization/8361: [3.3/3.4 regression] C++ compile-time
performance regression
Date: Mon, 24 Mar 2003 15:18:53 +0100 (CET)
I have now tested Mark's fix for PR 8361 and while that does not affect
non-optimizing performance, the difference for -O3 is noticable.
Below are the results of the 3.3-branch from 03/15 versus 03/24 (without
explicit --disable-checking):
% \time /files/pfeifer/gcc-3.3-0315/bin/g++ -c generate.ii
28.50 real 27.57 user 0.75 sys
% \time /files/pfeifer/gcc-3.3-0324/bin/g++ -c generate.ii
28.70 real 27.42 user 0.69 sys
No difference for non-optimizing compilation...
% \time /files/pfeifer/gcc-3.3-0315/bin/g++ -O3 -c generate.ii
109.55 real 105.85 user 3.06 sys
% \time /files/pfeifer/gcc-3.3-0324/bin/g++ -O3 -c generate.ii
81.28 real 77.41 user 3.55 sys
...but a nice speedup for -O3!
Gerald
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: optimization/8361: [3.3/3.4 regression] C++ compile-time performance regression
@ 2003-03-15 14:36 Steven Bosscher
0 siblings, 0 replies; 5+ messages in thread
From: Steven Bosscher @ 2003-03-15 14:36 UTC (permalink / raw)
To: nobody; +Cc: gcc-prs
The following reply was made to PR optimization/8361; it has been noted by GNATS.
From: Steven Bosscher <s.bosscher@student.tudelft.nl>
To: pfeifer@dbai.tuwien.ac.at, gcc-gnats@gcc.gnu.org,
gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-prs@gcc.gnu.org
Cc:
Subject: Re: optimization/8361: [3.3/3.4 regression] C++ compile-time performance
regression
Date: Sat, 15 Mar 2003 15:29:28 +0100
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8361
Hi Gerald,
Could you produce compile times for this PR and see how we're doing on
3.3 and
mainline? Quite a few speedup patches have gone in lately (most notably
the GC
limits patches), so the numbers really are way outdated now...
Greetz
Steven
P.S. Welcome back ;-)
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: optimization/8361: [3.3/3.4 regression] C++ compile-time performance regression
@ 2003-02-18 14:58 ebotcazou
0 siblings, 0 replies; 5+ messages in thread
From: ebotcazou @ 2003-02-18 14:58 UTC (permalink / raw)
To: gcc-bugs, gcc-prs, nobody, pfeifer
Old Synopsis: [3.3,3.4 regression] C++ compile-time performance regression
New Synopsis: [3.3/3.4 regression] C++ compile-time performance regression
State-Changed-From-To: open->analyzed
State-Changed-By: ebotcazou
State-Changed-When: Tue Feb 18 14:58:42 2003
State-Changed-Why:
Confirmed.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8361
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2003-05-01 11:36 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-03-23 9:16 optimization/8361: [3.3/3.4 regression] C++ compile-time performance regression Steven Bosscher
-- strict thread matches above, loose matches on Subject: below --
2003-05-01 11:36 Andrew Pinski
2003-03-24 15:14 Gerald Pfeifer
2003-03-15 14:36 Steven Bosscher
2003-02-18 14:58 ebotcazou
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).