[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131118040100.GE8043@ringworld.MIT.EDU>
Date: Sun, 17 Nov 2013 23:01:00 -0500
From: Greg Price <price@....EDU>
To: Joe Perches <joe@...ches.com>
Cc: Al Viro <viro@...IV.linux.org.uk>,
Christopher Li <sparse@...isli.org>,
Erico Nunes <nunes.erico@...il.com>,
linux-sparse@...r.kernel.org, dwmw2 <dwmw2@...radead.org>,
linux-mtd <linux-mtd@...ts.infradead.org>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] Clarify error on directive in macro arguments (Re:
[PATCH] jffs2: fix sparse errors: directive in argument list)
On Sun, Nov 17, 2013 at 06:15:32PM -0800, Joe Perches wrote:
> On Sun, 2013-11-17 at 21:07 -0500, Greg Price wrote:
> > Perhaps the following tweak to the error message would make this
> > subtlety clearer?
>
> Maybe, but this case isn't a macro. It's a function.
> Dunno if differentiating when it's a macro or a
> function is difficult though.
Yeah, this error message is already only emitted for directives in
macro arguments -- in this case, pr_info. It's in sparse's
preprocessor code; the error arises when a directive is spotted while
parsing a macro's arguments. By the time sparse (or an idealized C
compiler) parses the arguments of a real function, the token stream is
already the output of the preprocessor and any directives are gone.
Cheers,
Greg
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists