From: "David Mosberger-Tang" <dmosberger@gmail.com>
To: linux-ia64@vger.kernel.org
Subject: Re: Inquiry about brl statement
Date: Fri, 27 Apr 2007 16:18:52 +0000 [thread overview]
Message-ID: <ed5aea430704270918l3968ad2bn242bdbbe587b2f2@mail.gmail.com> (raw)
In-Reply-To: <200704271716.57969.christian.kandeler@hob.de>
As I remember it, a taken branch acts as a stop whereas a non-taken
branch doesn't (so if no explicit stop bit is following a branch, then
it must be OK for the entire group to be executed in parallel). I
suppose it's possible the definition changed or that my (admittedly
bad) memory is playing tricks on me. ;-)
--david
On 4/27/07, Christian Kandeler <christian.kandeler@hob.de> wrote:
> Hello,
>
> in the definition of the BRL_COND_FSYS_BUBBLE_DOWN macro in
> arch/ia64/kernel/gate.S, shouldn't there be a stop bit after the brl.cond
> instruction? According to the Intel specs, the current definition (which has
> no stop bit) triggers undefined behavior.
>
>
> Regards,
> Christian Kandeler
> -
> To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Mosberger Consulting LLC, http://www.mosberger-consulting.com/
next prev parent reply other threads:[~2007-04-27 16:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-27 15:16 Inquiry about brl statement Christian Kandeler
2007-04-27 16:18 ` David Mosberger-Tang [this message]
2007-04-27 18:49 ` Luck, Tony
2007-04-27 20:00 ` David Mosberger-Tang
2007-04-28 0:20 ` Jim Hull
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=ed5aea430704270918l3968ad2bn242bdbbe587b2f2@mail.gmail.com \
--to=dmosberger@gmail.com \
--cc=linux-ia64@vger.kernel.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