From: Jani Nikula <jani.nikula@linux.intel.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Ander Conselvan de Oliveira
<ander.conselvan.de.oliveira@intel.com>,
Mika Kuoppala <mika.kuoppala@linux.intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
Daniel Vetter <daniel.vetter@intel.com>,
intel-gfx@lists.freedesktop.org,
Robert Bragg <robert@sixbynine.org>
Subject: Re: [PATCH 3/3] [RFC] Revert "drm/i915: use variadic macros and arrays to choose port/pipe based registers"
Date: Mon, 20 Mar 2017 13:24:02 +0200 [thread overview]
Message-ID: <87o9wwb38t.fsf@intel.com> (raw)
In-Reply-To: <CAK8P3a3=6wwPF+fjO7VLWxhhBhXEnLT+hhpwAhSaD8ZR4nMq1Q@mail.gmail.com>
On Mon, 20 Mar 2017, Arnd Bergmann <arnd@arndb.de> wrote:
> I don't know how to generate a URL for it, but after adding this to the
> command line for gcc-7,
>
> -fsanitize=kernel-address -fasan-shadow-offset=0xdfff900000000000
> --param asan-stack=1 --param asan-globals=1 --param
> asan-instrumentation-with-call-threshold=10000
> -fsanitize-address-use-after-scope
>
> the code turned from really nice into the log series of checks below.
> Without -fsanitize-address-use-after-scope (which didn't exist before gcc-7),
> it's less bad but still exceeds the (arbitrary) 1536 byte limit.
It seems to be the combination of --param asan-stack=1 and
-fsanitize-address-use-after-scope that really blows up the code [1]. I
filed a GCC bug on it, mostly to see what they say [2]. I don't know,
maybe they think it's expected. *shrug*.
BR,
Jani.
[1] https://godbolt.org/g/hgS817
[2] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80114
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-03-20 11:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 9:40 [PATCH 1/3] drm/i915: allocate mock file pointer dynamically Arnd Bergmann
2017-03-20 9:40 ` [PATCH 2/3] drm/i915: split out check for noncontiguous pfn range Arnd Bergmann
2017-03-21 9:56 ` Chris Wilson
2017-03-21 10:23 ` Chris Wilson
2017-03-20 9:40 ` [PATCH 3/3] [RFC] Revert "drm/i915: use variadic macros and arrays to choose port/pipe based registers" Arnd Bergmann
2017-03-20 10:08 ` Jani Nikula
2017-03-20 10:39 ` Arnd Bergmann
2017-03-20 11:24 ` Jani Nikula [this message]
2017-03-20 9:54 ` [PATCH 1/3] drm/i915: allocate mock file pointer dynamically Daniel Vetter
2017-03-20 12:00 ` Joonas Lahtinen
2017-03-20 12:02 ` Arnd Bergmann
2017-03-20 12:07 ` Arnd Bergmann
2017-03-21 10:16 ` Chris Wilson
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=87o9wwb38t.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=ander.conselvan.de.oliveira@intel.com \
--cc=arnd@arndb.de \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.kuoppala@linux.intel.com \
--cc=robert@sixbynine.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).