From: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
To: carlos@systemhalted.org (Carlos O'Donell)
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] input constraints in atomic.h too loose ?
Date: Sun, 11 Feb 2007 12:36:56 -0500 (EST) [thread overview]
Message-ID: <200702111736.l1BHav1a028394__24370.5841283829$1416624284$gmane$org@hiauly1.hia.nrc.ca> (raw)
In-Reply-To: <119aab440702110918k1aca7744rc8abb50949a22069@mail.gmail.com> from "Carlos O'Donell" at Feb 11, 2007 12:18:54 pm
> > /tmp/ccvCRbqg.s:43: Error: bad expression
> What *is* the bad assembly here. Please don't make me count assembly
> line numbers, just point me at the bad asm.
The problem is the "m" constraint is too broad for ldw and stw insns.
These instructions don't accept any memory address. As suggested,
the "o" constraint should work. Alternatively, the address of the
variables could be forced to a register.
Dave
--
J. David Anglin dave.anglin@nrc-cnrc.gc.ca
National Research Council of Canada (613) 990-0752 (FAX: 952-6602)
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
next parent reply other threads:[~2007-02-11 17:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <119aab440702110918k1aca7744rc8abb50949a22069@mail.gmail.com>
2007-02-11 17:36 ` John David Anglin [this message]
[not found] <119aab440702111029h147c9ad5u602262ede5ea64d6@mail.gmail.com>
2007-02-11 18:48 ` [parisc-linux] input constraints in atomic.h too loose ? John David Anglin
[not found] <119aab440702110947u418c907eu19c3044230874df4@mail.gmail.com>
2007-02-11 17:59 ` John David Anglin
[not found] <200702102101.l1AL11Ai017315@hiauly1.hia.nrc.ca>
2007-02-11 4:42 ` Mike Frysinger
[not found] <200702022215.50914.vapier@gentoo.org>
2007-02-10 21:01 ` John David Anglin
2007-02-03 3:15 Mike Frysinger
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='200702111736.l1BHav1a028394__24370.5841283829$1416624284$gmane$org@hiauly1.hia.nrc.ca' \
--to=dave@hiauly1.hia.nrc.ca \
--cc=carlos@systemhalted.org \
--cc=parisc-linux@lists.parisc-linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.