linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ahmed S. Darwish" <darwish.07@gmail.com>
To: Josh Triplett <josh@kernel.org>
Cc: linux-sparse@vger.kernel.org
Subject: Warnings on global symbols accessed only from assembly code
Date: Fri, 12 Feb 2010 02:00:52 +0200	[thread overview]
Message-ID: <20100212000052.GA6837@laptop> (raw)

Hi,

Is there a way to let sparse avoid emitting warnings like:

   symbol 'X' was not declared. Should it be static?

for global methods that are only accessed from assembly files?

The reason is that a declaration for such methods - which are usually
bootstrap ones - can given the false impression of being used by some
C code 'somewhere'.

Unfortunately the current `-Wno-decl' solution is a bit extreme: it
turns off a very useful sparse feature (by design).

Thanks,

-- 
Darwish
http://darwish.07.googlepages.com

             reply	other threads:[~2010-02-12  0:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-12  0:00 Ahmed S. Darwish [this message]
2010-02-12  1:06 ` Warnings on global symbols accessed only from assembly code Christopher Li
2010-02-12  1:47   ` Ahmed S. Darwish
2010-02-12  6:43     ` Christopher Li
2010-02-14  0:48       ` Ahmed S. Darwish

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=20100212000052.GA6837@laptop \
    --to=darwish.07@gmail.com \
    --cc=josh@kernel.org \
    --cc=linux-sparse@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;
as well as URLs for NNTP newsgroup(s).