From: Basile Starynkevitch <basile@starynkevitch.net>
To: Paul Koning <paul_koning@dell.com>
Cc: Andi Kleen <andi@firstfloor.org>,
Jakub Jelinek <jakub@redhat.com>,
Richard Guenther <richard.guenther@gmail.com>,
Andrew Haley <aph@redhat.com>, "H.J. Lu" <hjl.tools@gmail.com>,
<gcc-patches@gcc.gnu.org>
Subject: Re: PATCH: Add pause intrinsic
Date: Thu, 26 May 2011 21:56:00 -0000 [thread overview]
Message-ID: <20110526213748.fc5bf65b.basile@starynkevitch.net> (raw)
In-Reply-To: <BAE3F7E9-A3F2-4239-B21C-3956259369B4@dell.com>
On Thu, 26 May 2011 13:48:13 -0400
Paul Koning <paul_koning@dell.com> wrote:
> Relax? Weird. "Pause" is just as weird. It might be an ia32 instruction,
> so as an ia32 builtin it is a reasonable name But if you want a generic
> builtin, you need a name that actually has some plausible connection with
> what it does, and neither "pause" nor "relax" do that.
I still think that having a builtin which do a "compiler flush" that is
which spill all registers to memory is useful, eg a
builtin_compiler_flush()
And I even think there is another reason to use it. If you are
debugging a program compiled with -O2 -g, and if you know where there
could be a bug or a fault, temporarily adding a call to that
builtin_compiler_flush () would probably help the gdb debugger a lot.
Regards.
--
Basile STARYNKEVITCH http://starynkevitch.net/Basile/
email: basile<at>starynkevitch<dot>net mobile: +33 6 8501 2359
8, rue de la Faiencerie, 92340 Bourg La Reine, France
*** opinions {are only mine, sont seulement les miennes} ***
next prev parent reply other threads:[~2011-05-26 19:38 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-24 19:35 H.J. Lu
2011-05-25 12:36 ` Andrew Haley
2011-05-25 13:20 ` Richard Guenther
2011-05-25 13:45 ` H.J. Lu
2011-05-25 13:40 ` H.J. Lu
2011-05-25 14:51 ` Andrew Haley
2011-05-25 15:19 ` H.J. Lu
2011-05-25 15:31 ` Andrew Haley
2011-05-25 15:32 ` Richard Guenther
2011-05-25 16:05 ` Andrew Haley
2011-05-25 16:16 ` Richard Guenther
2011-05-25 16:32 ` Michael Matz
2011-05-25 16:39 ` Richard Guenther
2011-05-25 16:53 ` H.J. Lu
2011-05-25 17:30 ` Andrew Haley
2011-05-25 17:56 ` H.J. Lu
2011-05-25 18:09 ` Andrew Pinski
2011-05-25 18:16 ` Andrew Haley
2011-05-26 10:49 ` Richard Guenther
2011-05-26 13:51 ` Andrew Haley
2011-05-26 14:39 ` Richard Guenther
2011-05-26 14:45 ` Andrew Haley
2011-05-26 15:19 ` Richard Guenther
2011-05-26 15:37 ` Jakub Jelinek
2011-05-26 15:42 ` Richard Guenther
2011-05-26 15:43 ` Andrew Haley
2011-05-26 15:58 ` Michael Matz
2011-05-26 17:36 ` Andi Kleen
2011-05-26 17:40 ` Jakub Jelinek
2011-05-26 18:23 ` Andi Kleen
2011-05-26 18:37 ` Paul Koning
2011-05-26 19:05 ` Andi Kleen
2011-05-26 21:56 ` Basile Starynkevitch [this message]
2011-05-30 10:39 ` Andrew Haley
2011-05-25 15:31 ` Richard Guenther
2011-05-25 19:53 ` Basile Starynkevitch
2011-05-25 20:03 ` H.J. Lu
2011-05-25 21:10 ` Basile Starynkevitch
2011-05-26 9:35 ` Andrew Haley
2011-05-26 17:37 ` Andi Kleen
2011-05-26 17:48 ` Basile Starynkevitch
2011-05-25 14:08 ` Uros Bizjak
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=20110526213748.fc5bf65b.basile@starynkevitch.net \
--to=basile@starynkevitch.net \
--cc=andi@firstfloor.org \
--cc=aph@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
--cc=jakub@redhat.com \
--cc=paul_koning@dell.com \
--cc=richard.guenther@gmail.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).