From: Segher Boessenkool <segher@kernel.crashing.org>
To: "Zvilius, Mark" <Mark.Zvilius@fluke.com>
Cc: "'gcc-help@gcc.gnu.org'" <gcc-help@gcc.gnu.org>
Subject: Re: asm constraints
Date: Fri, 27 Aug 2004 11:16:00 -0000 [thread overview]
Message-ID: <E0FCBE0F-F809-11D8-9C51-000A95A4DC02@kernel.crashing.org> (raw)
In-Reply-To: <732BE51FE9901143AE04411A11CC46560484AAB5@evtexc02.tc.fluke.com>
> unsigned int tbl;
> __asm__("mftbl %0" : "=r" (tbl));
[side note: mftbl is not a PowerPC insn, nor an assembler
extended mnemonic. I have no idea why libopcodes accepts
it].
> I'm wondering why it's wasting a register.
Did you compile with optimization on? If so, what compiler
version did you use? I tried with 3.4.1 and it works just
fine. If you still have problems, please show the exact code
(full routine, compilable as-is).
> Am I specifying the constraint incorrectly?
No, it's fine.
Segher
prev parent reply other threads:[~2004-08-27 9:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-27 6:58 Zvilius, Mark
2004-08-27 11:16 ` Segher Boessenkool [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=E0FCBE0F-F809-11D8-9C51-000A95A4DC02@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=Mark.Zvilius@fluke.com \
--cc=gcc-help@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).