From: Richard Henderson <rth@redhat.com>
To: sje@cup.hp.com
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [patch 1/N][ia64] -mfused-madd cleanup
Date: Fri, 19 Nov 2010 19:30:00 -0000 [thread overview]
Message-ID: <4CE6C9D7.1060903@redhat.com> (raw)
In-Reply-To: <1290192327.9792.11.camel@hpsje.cup.hp.com>
On 11/19/2010 10:45 AM, Steve Ellcey wrote:
> So what do we do about it? I am not familiar with the -g/-g0 problem
> but I assume that it means the difference you are seeing is just in the
> debug information.
No, it's real code differences caused by the inclusion of debug info.
I'm still working on it. My ia64 box is somewhat slow single-threaded;
I probably should be doing the test case reduction on a faster machine...
r~
next prev parent reply other threads:[~2010-11-19 19:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-10 23:05 Richard Henderson
2010-11-10 23:30 ` Steve Ellcey
2010-11-11 0:02 ` Richard Henderson
2010-11-11 0:07 ` Jakub Jelinek
2010-11-12 0:58 ` Richard Henderson
2010-11-15 21:00 ` Steve Ellcey
2010-11-15 21:03 ` Andrew Pinski
2010-11-15 21:30 ` Steve Ellcey
2010-11-16 17:40 ` Steve Ellcey
2010-11-16 18:21 ` Richard Henderson
2010-11-16 19:00 ` Richard Henderson
2010-11-19 19:14 ` Steve Ellcey
2010-11-19 19:30 ` Richard Henderson [this message]
2010-11-19 23:01 ` Richard Henderson
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=4CE6C9D7.1060903@redhat.com \
--to=rth@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=sje@cup.hp.com \
/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).