From: David Mosberger <davidm@hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] ia64_get_dcr problem
Date: Mon, 12 Feb 2001 23:42:57 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590693005145@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590693005143@msgid-missing>
>>>>> On Mon, 12 Feb 2001 16:25:38 -0600 (CST), Jack Steiner <steiner@sgi.com> said:
Jack> Is this a GCC problem or a problem with the
Jack> asm/ia64/processor.h inline functions??
Jack> I used the ia64_set_dcr & ia64_get_dcr functions in a loop &
Jack> got bad code. I had references to both ia64_get_dcr in
Jack> ia64_set_dcr in the loop. The "get" was optimized out of the
Jack> loop & did not see the result of the "set".
Jack> If I add "volatile" to the ia64_get_dcr asm statement, I can
Jack> avoid the problem. But I am not sure whether this is the
Jack> correct solution. (I hit a similar problem with
Jack> ia64_get_irr0() earlier too).
Thanks for the report.
I fixed this now, along with a couple of other *get* macros in
processor.h.
--david
prev parent reply other threads:[~2001-02-12 23:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-12 22:25 [Linux-ia64] ia64_get_dcr problem Jack Steiner
2001-02-12 23:17 ` Jim Wilson
2001-02-12 23:42 ` David Mosberger [this message]
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=marc-linux-ia64-105590693005145@msgid-missing \
--to=davidm@hpl.hp.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