From: Alexandre Oliva <aoliva@redhat.com>
To: Richard Sandiford <rsandifo@redhat.com>
Cc: Kazu Hirata <kazu@cs.umass.edu>, gcc-patches@gcc.gnu.org
Subject: Re: add h8sx support to h8300
Date: Thu, 08 Jul 2004 18:16:00 -0000 [thread overview]
Message-ID: <or658ypheg.fsf@free.redhat.lsd.ic.unicamp.br> (raw)
In-Reply-To: <87zn6aevpa.fsf@redhat.com>
On Jul 8, 2004, Richard Sandiford <rsandifo@redhat.com> wrote:
> Alexandre Oliva <aoliva@redhat.com> writes:
>> gcc.c-torture/execute/builtin-setjmp.c. It *still* fails at -O3
>> -fomit-frame-pointer, but not at lower optimization levels, which it
>> did before.
> Are you sure it's still needed? Is it possible that whatever was
> causing the failure was fixed by another patch?
I don't think so.
> I tried the attached, both with and without the h8300.md bit,
> and it didn't make any difference to the results for this testcase.
> Like you say, -O3 -fomit-frame-pointer fails either way.
Right. But lower optimization levels failed before the patch, and
passed with it.
> I just remember this making quite a big difference to quality of the
> output
It would make a bigger difference if I hadn't changed the patterns
that used !D to use ??D instead.
--
Alexandre Oliva http://www.ic.unicamp.br/~oliva/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}
next prev parent reply other threads:[~2004-07-08 16:56 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-21 14:24 Alexandre Oliva
2004-06-21 17:12 ` Kazu Hirata
2004-06-23 2:23 ` Alexandre Oliva
2004-07-07 22:11 ` Alexandre Oliva
2004-07-08 6:08 ` Richard Sandiford
2004-07-08 7:41 ` Alexandre Oliva
2004-07-08 9:39 ` Richard Sandiford
2004-07-08 18:16 ` Alexandre Oliva [this message]
2004-07-08 18:16 ` Richard Sandiford
2004-07-08 20:23 ` Alexandre Oliva
2004-07-12 20:14 ` Richard Sandiford
2004-07-14 12:49 ` Alexandre Oliva
2004-07-14 17:16 ` Richard Sandiford
2004-07-15 4:11 ` Alexandre Oliva
2004-07-15 5:22 ` Richard Sandiford
2004-07-15 16:25 ` Alexandre Oliva
2004-07-15 17:14 ` Richard Sandiford
2004-07-15 17:25 ` Richard Sandiford
2004-07-15 22:23 ` Alexandre Oliva
2004-07-08 21:20 ` Alexandre Oliva
2004-07-06 20:56 ` Alexandre Oliva
2004-07-07 2:37 ` Richard Henderson
2004-07-07 7:06 ` Alexandre Oliva
2004-07-07 9:06 ` Richard Henderson
2004-07-08 0:14 ` Alexandre Oliva
2004-07-08 1:22 ` Richard Henderson
2004-07-08 1:26 ` Alexandre Oliva
2004-07-08 2:01 ` Richard Henderson
2004-07-08 4:39 ` Alexandre Oliva
2004-07-08 18:59 ` Alexandre Oliva
2004-07-07 9:13 ` Joseph S. Myers
2004-07-07 19:44 ` Alexandre Oliva
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=or658ypheg.fsf@free.redhat.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=kazu@cs.umass.edu \
--cc=rsandifo@redhat.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).