public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: optimization/8361: [3.3/3.4 regression] C++ compile-time performance regression Date: Mon, 24 Mar 2003 15:14:00 -0000 [thread overview] Message-ID: <20030324142600.25675.qmail@sources.redhat.com> (raw) 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
next reply other threads:[~2003-03-24 14:26 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-24 15:14 Gerald Pfeifer [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-01 11:36 Andrew Pinski 2003-03-23 9:16 Steven Bosscher 2003-03-15 14:36 Steven Bosscher 2003-02-18 14:58 ebotcazou
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20030324142600.25675.qmail@sources.redhat.com \ --to=pfeifer@dbai.tuwien.ac.at \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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).