From: Jamie Lokier <jamie@shareable.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Linus Torvalds <torvalds@osdl.org>, Arnd Bergmann <arnd@arndb.de>,
Nikita Danilov <Nikita@Namesys.COM>,
linux-kernel@vger.kernel.org
Subject: Re: const versus __attribute__((const))
Date: Tue, 9 Dec 2003 19:15:30 +0000 [thread overview]
Message-ID: <20031209191530.GA30766@mail.shareable.org> (raw)
In-Reply-To: <3FD5FD8C.7010608@zytor.com>
H. Peter Anvin wrote:
> Agreed. It's just a bit ugly that the "m" in "rm" has a different
> meaning than just "m".
Oh? What does the "m" in "m,m" mean then?
(I don't have GCC 3.3 to try it here).
Sometimes that's useful, when used with differing multi-alternative
constraints on the other arguments, and 99% of the time you _do_ want
the "m,m" constraint to use the actual lvalue's address just like "m".
-- Jamie
next prev parent reply other threads:[~2003-12-09 20:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-08 15:46 const versus __attribute__((const)) Arnd Bergmann
2003-12-08 17:50 ` H. Peter Anvin
2003-12-08 18:27 ` Nikita Danilov
2003-12-08 18:31 ` H. Peter Anvin
2003-12-09 2:59 ` Jamie Lokier
2003-12-09 3:21 ` H. Peter Anvin
2003-12-09 3:49 ` Jamie Lokier
2003-12-09 5:37 ` H. Peter Anvin
2003-12-09 7:26 ` Linus Torvalds
2003-12-09 7:40 ` H. Peter Anvin
2003-12-09 11:56 ` Arnd Bergmann
2003-12-09 15:42 ` H. Peter Anvin
2003-12-09 16:44 ` Linus Torvalds
2003-12-09 16:51 ` H. Peter Anvin
2003-12-09 19:15 ` Jamie Lokier [this message]
2003-12-09 7:19 ` Linus Torvalds
-- strict thread matches above, loose matches on Subject: below --
2003-12-08 1:19 H. Peter Anvin
2003-12-08 12:32 ` Nikita Danilov
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=20031209191530.GA30766@mail.shareable.org \
--to=jamie@shareable.org \
--cc=Nikita@Namesys.COM \
--cc=arnd@arndb.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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 NNTP newsgroup(s).