From: Scott Robert Ladd <coyote@coyotegulch.com>
To: Giovanni Bajo <giovannibajo@libero.it>
Cc: gcc@gcc.gnu.org
Subject: Re: GCC Benchmarks (coybench), AMD64 and i686, 14 August 2004
Date: Mon, 16 Aug 2004 15:51:00 -0000 [thread overview]
Message-ID: <4120D634.9010004@coyotegulch.com> (raw)
In-Reply-To: <003201c48301$964dbee0$51b82997@bagio>
Giovanni Bajo wrote:
> Can you please file a bugreport with a preprocessed version of the
mole test?
> We can flag it as a regression and hopefully have it fixed before the release.
Filed as 17050, with -save-temps source file.
This problem is unique to either 64-bit or Opteron code generation,
given that my Pentium 4 does not show the same regression. On the other
hand, Intel produces code that is 6X faster on Pentium 4, suggesting
that GCC's code generation may be weak there as well.
--
Scott Robert Ladd
Coyote Gulch Productions (http://www.coyotegulch.com)
Software Invention for High-Performance Computing
next prev parent reply other threads:[~2004-08-16 15:44 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-15 15:35 Scott Robert Ladd
2004-08-15 20:48 ` Giovanni Bajo
2004-08-16 15:51 ` Scott Robert Ladd [this message]
2004-08-17 19:28 ` Marcel Cox
2004-08-17 21:26 ` Scott Robert Ladd
2004-08-17 22:21 ` Joe Buck
2004-08-17 22:39 ` Mike Stump
2004-08-17 22:54 ` Scott Robert Ladd
2004-08-17 23:53 ` Robert Dewar
2004-08-18 0:28 ` Joe Buck
2004-08-18 0:41 ` Robert Dewar
2004-08-18 0:44 ` Robert Dewar
2004-08-18 0:58 ` Joe Buck
2004-08-18 1:04 ` Robert Dewar
2004-08-18 1:18 ` Joe Buck
2004-08-18 1:27 ` Robert Dewar
2004-08-18 1:34 ` Scott Robert Ladd
2004-08-18 1:45 ` Zack Weinberg
2004-08-18 18:25 ` Laurent GUERBY
2004-08-18 18:45 ` Zack Weinberg
2004-08-18 2:04 ` Scott Robert Ladd
2004-08-18 8:37 ` Richard Henderson
2004-08-18 16:25 ` Scott Robert Ladd
2004-08-18 18:48 ` Toon Moene
2004-08-18 11:14 ` Marcel Cox
2004-08-17 5:14 ` Natros
2004-08-18 1:35 ` Kaveh R. Ghazi
2004-08-18 13:14 ` Arnaud Desitter
2004-08-18 15:37 ` Kaveh R. Ghazi
2004-08-18 17:05 ` Scott Robert Ladd
2004-08-18 18:05 ` Kaveh R. Ghazi
2004-08-18 18:05 ` Scott Robert Ladd
2004-08-17 22:44 Richard Kenner
2004-08-18 0:13 ` Robert Dewar
2004-08-18 0:21 ` Joe Buck
2004-08-18 1:32 ` Daniel Berlin
2004-08-18 1:46 ` Daniel Berlin
2004-08-18 2:10 ` Daniel Berlin
2004-08-18 10:25 Uros Bizjak
2004-08-18 12:11 ` Paolo Bonzini
2004-08-18 13:09 ` Daniel Berlin
2004-08-18 13:48 ` Uros Bizjak
2004-08-18 13:24 Wolfgang Bangerth
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=4120D634.9010004@coyotegulch.com \
--to=coyote@coyotegulch.com \
--cc=gcc@gcc.gnu.org \
--cc=giovannibajo@libero.it \
/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).