linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: linux-sparse@vger.kernel.org
Cc: will.deacon@arm.com, Ard Biesheuvel <ard.biesheuvel@linaro.org>
Subject: [PATCH] sparse: treat function pointers as pointers to const data
Date: Sun,  7 Sep 2014 13:37:39 +0200	[thread overview]
Message-ID: <1410089859-22957-1-git-send-email-ard.biesheuvel@linaro.org> (raw)

This code snippet:

static void bar(void const *arg)
{
	int (*foo)(void) = arg;
}

produces the following warning:

test.c:4:28: warning: incorrect type in initializer (different modifiers)
test.c:4:28:    expected int ( *foo )( ... )
test.c:4:28:    got void const *arg

which is caused by the fact that the function pointer 'foo' is not annotated
as being a pointer to const data. However, dereferencing a function pointer
does not produce an lvalue, so a function pointer points to const data by
definition, and we should treat it accordingly.

Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
---
 evaluate.c | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/evaluate.c b/evaluate.c
index 66556150ddac..6428312f3e61 100644
--- a/evaluate.c
+++ b/evaluate.c
@@ -794,6 +794,14 @@ static unsigned long target_qualifiers(struct symbol *type)
 	unsigned long mod = type->ctype.modifiers & MOD_IGN;
 	if (type->ctype.base_type && type->ctype.base_type->type == SYM_ARRAY)
 		mod = 0;
+
+	/*
+	 * Dereferencing a function pointer does not produce an lvalue,
+	 * which means its target is implicitly 'const', and assigning
+	 * a pointer-to-const value to it is ok.
+	 */
+	if (type->ctype.base_type && type->ctype.base_type->type == SYM_FN)
+		mod |= MOD_CONST;
 	return mod;
 }
 
-- 
1.8.3.2


                 reply	other threads:[~2014-09-07 11:37 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1410089859-22957-1-git-send-email-ard.biesheuvel@linaro.org \
    --to=ard.biesheuvel@linaro.org \
    --cc=linux-sparse@vger.kernel.org \
    --cc=will.deacon@arm.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;
as well as URLs for NNTP newsgroup(s).