public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "william dot crocker at analog dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug optimization/13712] Executable runs 25% slower than when compiled with INTEL compiler Date: Thu, 29 Jan 2004 13:10:00 -0000 [thread overview] Message-ID: <20040129131057.23876.qmail@sources.redhat.com> (raw) In-Reply-To: <20040116211131.13712.william.crocker@analog.com> ------- Additional Comments From william dot crocker at analog dot com 2004-01-29 13:10 ------- Subject: Re: Executable runs 25% slower than when compiled with INTEL compiler > From dberlin@gcc.gnu.org Thu Jan 22 14:48:06 2004 > Date: 22 Jan 2004 19:48:04 -0000 > From: "bangerth at dealii dot org" <gcc-bugzilla@gcc.gnu.org> > To: william.crocker@analog.com > Subject: [Bug optimization/13712] Executable runs 25% slower than when compiled with INTEL compiler > X-Bugzilla-Reason: Reporter > X-Spam-Status: No, hits=0.0 required=10.0 > tests=none > version=2.60 > X-Spam-Level: > X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) > X-Scanned-By: MIMEDefang 2.38 > > > ------- Additional Comments From bangerth at dealii dot org 2004-01-22 19:48 ------- > That would be a good first step. The testcase doesn't have to be particularly > small as a first attempt, but it should be selfcontained. The testcase also > doesn't have to do something particularly useful. > I sent in my test case, but the bugzilla data base implies that you are still "waiting". Did you get my test case or should I send it again ? Do you have any email filters which would have rejected my email ? Bill > W. > > -- > > > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13712 > > ------- You are receiving this mail because: ------- > You reported the bug, or are watching the reporter. > -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13712
next prev parent reply other threads:[~2004-01-29 13:10 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-01-16 21:11 [Bug c++/13712] New: " william dot crocker at analog dot com 2004-01-16 22:54 ` [Bug c++/13712] " pinskia at gcc dot gnu dot org 2004-01-22 19:42 ` william dot crocker at analog dot com 2004-01-22 19:45 ` [Bug optimization/13712] " pinskia at gcc dot gnu dot org 2004-01-22 19:48 ` bangerth at dealii dot org 2004-01-29 13:10 ` william dot crocker at analog dot com [this message] 2004-01-29 13:16 ` falk dot hueffner at student dot uni-tuebingen dot de 2004-01-29 13:29 ` william dot crocker at analog dot com 2004-01-29 16:01 ` falk at debian dot org 2004-01-29 16:27 ` william dot crocker at analog dot com 2004-01-29 16:48 ` falk at debian dot org 2004-02-03 21:34 ` william dot crocker at analog dot com 2004-02-16 14:55 ` uros at kss-loka dot si 2005-01-23 18:39 ` [Bug rtl-optimization/13712] " steven at gcc dot gnu dot org 2005-01-24 11:16 ` uros at kss-loka dot si 2005-04-24 14:18 ` steven at gcc dot gnu dot org 2005-05-07 15:27 ` steven 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=20040129131057.23876.qmail@sources.redhat.com \ --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: 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).