Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 01 Feb 2017 16:10:03 +0100
From: "PaX Team" <>
To: Kees Cook <>, Emese Revfy <>,
        Arnd Bergmann <>
CC:, Josh Triplett <>,,,,,,,,,,,,
Subject: Re: initify plugin crashes on arm allmodconfig

On 1 Feb 2017 at 14:52, Arnd Bergmann wrote:

> On my ARM test builds (using a recent gcc-7 snapshot), allmodconfig failed with a compiler
> crash, I have managed to minimize the test case to this:
> /home/arnd/cross-gcc/bin/arm-linux-gnueabi-gcc-7.0.1 -O2 -Wall -fplugin=/home/arnd/arm-soc/build/tmp/scripts/gcc-plugins/ -DINITIFY_PLUGIN
> -fplugin-arg-initify_plugin-search_init_exit_functions  -fno-inline-functions-called-once -S atmel_lcdfb.i arm-linux-gnueabi-gcc-7.0.1: internal compiler error: Segmentation fault (program cc1)
> While trying to reproduce it, one time I ended up killing the gcc task when it
> used more than 80 gigabytes (!) of memory after around six minutes of compiling
> the same file (drivers/video/fbdev/atmel_lcdfb.c), but other times it just crashed
> as above using various ARM cross compilers (4.9.3, 5.3, 6.1.1).

i tried to reproduce it with 5.4 and 6.3 to no avail (arm64->arm cross compiler)
so some more information will be needed. first, which plugin version did you try?
second, if you build your own gcc, can you configure one with this additional


this will enable lots of compile time self-checking in gcc and may pinpoint the
problem sooner (it also increases compile time so you probably want to keep this
gcc as a separate build from your main one).

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.