From: Andrey Belevantsev <abel@ispras.ru>
To: Bernd Schmidt <bernds@codesourcery.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
"Vladimir N. Makarov" <vmakarov@redhat.com>
Subject: Re: Fix PR 49014
Date: Thu, 26 May 2011 13:53:00 -0000 [thread overview]
Message-ID: <4DDE5657.4000601@ispras.ru> (raw)
In-Reply-To: <4DDD20CE.4000707@codesourcery.com>
On 25.05.2011 19:31, Bernd Schmidt wrote:
> On 05/25/2011 03:29 PM, Andrey Belevantsev wrote:
>> I think the hook is a better idea than the attribute because nobody will
>> care to mark all offending insns with an attribute.
>
> I don't know. IIRC when I looked at sh or whatever the broken port was,
> it was only two insns - there would still be some value in being able to
> assert that all other insns have a reservation.
OK, I will take a look on x86-64 and will get back with more information.
Andrey
>
>
> Bernd
next prev parent reply other threads:[~2011-05-26 13:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-25 9:45 Andrey Belevantsev
2011-05-25 14:57 ` Bernd Schmidt
2011-05-25 16:42 ` Andrey Belevantsev
2011-05-25 16:49 ` Bernd Schmidt
2011-05-26 13:53 ` Andrey Belevantsev [this message]
2011-07-01 14:50 ` Andrey Belevantsev
2011-07-07 16:28 ` Vladimir Makarov
2011-07-08 8:27 ` Andrey Belevantsev
2011-07-08 15:38 ` Vladimir Makarov
2011-07-07 17:13 ` Bernd Schmidt
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=4DDE5657.4000601@ispras.ru \
--to=abel@ispras.ru \
--cc=bernds@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=vmakarov@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).