public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "giovannibajo at libero dot it" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/21485] BYTEmark numsort: performance regression 3.4.3 -> 4.0.0 with -O3 optimization
Date: Tue, 10 May 2005 09:45:00 -0000 [thread overview]
Message-ID: <20050510094526.4362.qmail@sourceware.org> (raw)
In-Reply-To: <20050510090336.21485.jbucata@tulsaconnect.com>
------- Additional Comments From giovannibajo at libero dot it 2005-05-10 09:45 -------
Jason: thanks for this! Even better would be to let the testcase do a fixed
number of iterations (like 1000 or so), and then we'll be using "time"
externally to measure performance. Maybe you can do this for other testcases
you are going to submit, thanks!
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21485
next prev parent reply other threads:[~2005-05-10 9:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-10 9:03 [Bug rtl-optimization/21485] New: " jbucata at tulsaconnect dot com
2005-05-10 9:05 ` [Bug rtl-optimization/21485] " jbucata at tulsaconnect dot com
2005-05-10 9:10 ` jbucata at tulsaconnect dot com
2005-05-10 9:15 ` steven at gcc dot gnu dot org
2005-05-10 9:27 ` rguenth at gcc dot gnu dot org
2005-05-10 9:45 ` giovannibajo at libero dot it [this message]
2005-05-10 9:46 ` steven at gcc dot gnu dot org
2005-05-10 9:51 ` steven at gcc dot gnu dot org
2005-05-10 10:22 ` steven at gcc dot gnu dot org
2005-05-10 12:58 ` bonzini at gcc dot gnu dot org
2005-05-10 16:38 ` [Bug rtl-optimization/21485] [4.0/4.1 Regression] BYTEmark numsort: codegen regression with -O3 giovannibajo at libero dot it
2005-05-10 20:03 ` pinskia at gcc dot gnu dot org
2005-07-08 1:41 ` mmitchel at gcc dot gnu dot org
2005-09-27 16:21 ` mmitchel at gcc dot gnu dot org
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=20050510094526.4362.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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: link
Be 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).