From: Andrew Haley <aph@redhat.com>
To: Ian Lance Taylor <iant@google.com>
Cc: gcc@gcc.gnu.org, pinskia@gcc.gnu.org
Subject: Re: The reincarnation of PR15242
Date: Wed, 09 Sep 2009 09:17:00 -0000 [thread overview]
Message-ID: <4AA772BA.6060405@redhat.com> (raw)
In-Reply-To: <m3bpllxhj6.fsf@google.com>
Ian Lance Taylor wrote:
> Andrew Haley <aph@redhat.com> writes:
>
>> This seems to be an an old bug that has come back. We're generating
>>
>> L1210:
>> jmp *%eax
>> .L4:
>> .L5:
>> ...
>> jmp .L1210
>> .L1171:
>> .L1172:
>> ...
>> jmp .L1210
>> .L1168:
>> .L1169:
>> ...
>> jmp .L1210
>>
>>
>> instead of
>>
>> .L1210:
>> jmp *%eax
>> .L4:
>> .L5:
>> ...
>> jmp *%eax
>> .L1171:
>> .L1172:
>> ...
>> jmp *%eax
>> .L1168:
>> .L1169:
>> ...
>> jmp *%eax
>>
>> Current gcc trunk, x86, gcc -O3 ef.i -S -m32.
>>
>> Attachment in old Bugzilla entry at
>> http://gcc.gnu.org/bugzilla/attachment.cgi?id=6206&action=view
>
>
> We should have something like this in the testsuite.
I've been thinking about that. How would one go about writing a testcase?
I guess we're looking for a lot of jmp instrs all bracnhing to the same
label.
Andrew.
next prev parent reply other threads:[~2009-09-09 9:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-07 16:12 Andrew Haley
2009-09-08 21:18 ` Ian Lance Taylor
2009-09-09 9:17 ` Andrew Haley [this message]
2009-09-09 14:16 ` Ian Lance Taylor
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=4AA772BA.6060405@redhat.com \
--to=aph@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=iant@google.com \
--cc=pinskia@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).