From: kugan <kugan.vivekanandarajah@linaro.org>
To: Arnd Bergmann <arnd@arndb.de>, Kees Cook <keescook@google.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Randy Dunlap <rdunlap@infradead.org>,
Olof Johansson <olof@lixom.net>, Mark Brown <broonie@kernel.org>,
info@kernelci.org, Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Will Deacon <will.deacon@arm.com>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
LKML <linux-kernel@vger.kernel.org>,
Linux-Next <linux-next@vger.kernel.org>,
Fengguang Wu <fengguang.wu@intel.com>,
Andrew Donnellan <andrew.donnellan@au1.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Laura Abbott <labbott@redhat.com>,
"x86@kernel.org" <x86@kernel.org>,
PaX Team <pageexec@freemail.hu>, Emese Revfy <re.emese@gmail.com>,
maxim.kuvyrkov@linaro.org,
Kugan Vivekanandarajah <kuganv@linaro.org>
Subject: Re: enabling COMPILE_TEST support for GCC plugins in v4.11
Date: Sat, 10 Dec 2016 08:08:54 +1100 [thread overview]
Message-ID: <864d5aa6-245c-0b60-4862-f3eb172305b3@linaro.org> (raw)
In-Reply-To: <4284516.VtSFlm1aM8@wuerfel>
On 10/12/16 07:35, Arnd Bergmann wrote:
> On Friday, December 9, 2016 11:13:20 AM CET Kees Cook wrote:
>> On Fri, Dec 9, 2016 at 3:33 AM, Arnd Bergmann <arnd@arndb.de> wrote:
>>> On Thursday, December 8, 2016 11:00:42 AM CET Kees Cook wrote:
>>>> If you have a moment, applying 215e2aa6c024[1] and reverting
>>>> a519167e753e for an allyesconfig/allmodconfig build should let you
>>>> know if things are working correctly with headers installed. If anyone
>>>> sees any problems, please let me know and I can queue up fixes.
>>>>
>>> This is what I got on x86-64 with a gcc-7.0.0 snapshot:
>>>
>>> In file included from /git/arm-soc/scripts/gcc-plugins/gcc-common.h:42:0,
>>> from <stdin>:1:
>>> /home/arnd/cross-gcc/lib/gcc/x86_64-linux/7.0.0/plugin/include/emit-rtl.h:371:41: error: use of enum ‘memmodel’ without previous declaration
>>> extern bool need_atomic_barrier_p (enum memmodel, bool);
>>> ^
>>> In file included from /git/arm-soc/scripts/gcc-plugins/gcc-common.h:94:0,
>>> from <stdin>:1:
>>> /home/arnd/cross-gcc/lib/gcc/x86_64-linux/7.0.0/plugin/include/tree-ssanames.h:70:40: error: use of enum ‘value_range_type’ without previous declaration
>>> extern void set_range_info (tree, enum value_range_type, const wide_int_ref &,
>>> ^
>>> /home/arnd/cross-gcc/lib/gcc/x86_64-linux/7.0.0/plugin/include/tree-ssanames.h:73:13: error: use of enum ‘value_range_type’ without previous declaration
>>> extern enum value_range_type get_range_info (const_tree, wide_int *,
>>> ^
>>> /home/arnd/cross-gcc/lib/gcc/x86_64-linux/7.0.0/plugin/include/tree-ssanames.h:98:55: error: use of enum ‘value_range_type’ without previous declaration
>>> extern void duplicate_ssa_name_range_info (tree, enum value_range_type,
>>> ^
>>> Cannot use CONFIG_GCC_PLUGINS: your gcc installation does not support plugins, perhaps the necessary headers are missing?
>>> scripts/Makefile.gcc-plugins:51: recipe for target 'gcc-plugins-check' failed
>>>
>>> I manually fixed up the gcc header files to include the ones with the
>>> definition for now, to address those, but I don't know if that change is
>>> correct.
>>
>> What was needed?
>
> I added '#include "memmodel.h"' and '#include "tree-vrp.h"', respectively, to
> the headers that failed to get compiled.
>
> This might be the correct solution, or the headers might not be meant to
> be used standalone and instead require being included in the right order.
>
> Gcc commit svn+ssh://gcc.gnu.org/svn/gcc/trunk@239638 moved
> value_range_type from tree-ssanames.h to tree-vrp.h, I've added
> Kugan to Cc, maybe he can clarify what that means for plugins.
Looks to me that in gcc-common.h tree-vrp.h should be included before
tree-ssanames.h as it is done in gcc now.
Thanks,
Kugan
prev parent reply other threads:[~2016-12-09 21:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-08 19:00 enabling COMPILE_TEST support for GCC plugins in v4.11 Kees Cook
2016-12-09 1:52 ` Paul Gortmaker
2016-12-09 4:15 ` Kees Cook
2017-06-23 5:43 ` Michael Ellerman
2017-06-23 18:35 ` Kees Cook
2017-06-23 21:16 ` Tony Breeds
2016-12-09 10:40 ` Arnd Bergmann
2016-12-09 19:12 ` Kees Cook
2016-12-09 19:40 ` Linus Torvalds
2017-06-23 0:18 ` Kees Cook
2016-12-10 16:45 ` Emese Revfy
2016-12-16 21:05 ` Kees Cook
2016-12-09 11:33 ` Arnd Bergmann
2016-12-09 19:13 ` Kees Cook
2016-12-09 20:35 ` Arnd Bergmann
2016-12-09 21:08 ` kugan [this message]
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=864d5aa6-245c-0b60-4862-f3eb172305b3@linaro.org \
--to=kugan.vivekanandarajah@linaro.org \
--cc=akpm@linux-foundation.org \
--cc=andrew.donnellan@au1.ibm.com \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=fengguang.wu@intel.com \
--cc=info@kernelci.org \
--cc=keescook@google.com \
--cc=kuganv@linaro.org \
--cc=labbott@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=maxim.kuvyrkov@linaro.org \
--cc=mpe@ellerman.id.au \
--cc=olof@lixom.net \
--cc=pageexec@freemail.hu \
--cc=rdunlap@infradead.org \
--cc=re.emese@gmail.com \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.org \
--cc=will.deacon@arm.com \
--cc=x86@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).