From: Roland Dreier <roland@topspin.com>
To: Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc: William Lee Irwin III <wli@holomorphy.com>,
Pete Zaitcev <zaitcev@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: s390(64) per_cpu in modules (ipv6)
Date: Wed, 30 Jun 2004 09:07:08 -0700 [thread overview]
Message-ID: <52oen1jahf.fsf@topspin.com> (raw)
In-Reply-To: <20040630130442.GA2440@mschwid3.boeblingen.de.ibm.com> (Martin Schwidefsky's message of "Wed, 30 Jun 2004 15:04:42 +0200")
Martin> __attribute_used__ isn't really what we want. If a
Martin> statically defined per cpu variable isn't used in the C
Martin> file then gcc should be allowed to remove it. It's not
Martin> used after all. What we need is a way to tell the
Martin> compiler that an inline assembly uses a variable without
Martin> passing any kind of address of the variable to it.
Actually my understanding is that __attribute_used__ is intended for
exactly that: to let the compiler know that something that is
apparently unused by the C code is actually used by inline assembly.
I'm sure your solution is fine as well but I think this type of
situation is exactly what __attribute_used__ is for. For example it
is attached to the modversions ____versions array so that it is not
discarded by the compiler.
Best,
Roland
next prev parent reply other threads:[~2004-06-30 16:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-30 13:04 s390(64) per_cpu in modules (ipv6) Martin Schwidefsky
2004-06-30 16:07 ` Roland Dreier [this message]
2004-06-30 20:55 ` Pete Zaitcev
2004-07-01 13:05 ` Arnd Bergmann
[not found] <OFC25D1557.60BFB654-ON42256F2E.00327ABF-42256F2E.0032D239@de.ibm.com>
2004-10-17 2:51 ` Rusty Russell
-- strict thread matches above, loose matches on Subject: below --
2004-06-30 6:35 Pete Zaitcev
2004-06-30 6:45 ` William Lee Irwin III
2004-06-30 6:46 ` Roland Dreier
2004-10-15 1:41 ` Rusty Russell
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=52oen1jahf.fsf@topspin.com \
--to=roland@topspin.com \
--cc=linux-kernel@vger.kernel.org \
--cc=schwidefsky@de.ibm.com \
--cc=wli@holomorphy.com \
--cc=zaitcev@redhat.com \
/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