From: Peter Hurley <peter@hurleysoftware.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Aaro Koskinen <aaro.koskinen@iki.fi>,
Johannes Weiner <hannes@cmpxchg.org>,
linux-kernel@vger.kernel.org, Felipe Balbi <balbi@ti.com>,
Rabin Vincent <rabin@rab.in>
Subject: Re: [PATCH] arm: Blacklist gcc 4.8.[012] and 4.9.0 with CONFIG_FRAME_POINTER
Date: Fri, 10 Oct 2014 12:55:34 -0400 [thread overview]
Message-ID: <54380F86.10005@hurleysoftware.com> (raw)
In-Reply-To: <20141010163613.GO5182@n2100.arm.linux.org.uk>
On 10/10/2014 12:36 PM, Russell King - ARM Linux wrote:
> On Fri, Oct 10, 2014 at 12:26:14PM -0400, Peter Hurley wrote:
>> gcc versions 4.8.[012] and 4.9.0 generates code that prematurely
>> adjusts the stack pointer such that still-to-be-referenced locals
>> are below the stack pointer, which allows them to be overwritten
>> by interrupts.
>
> I would much rather do this in asm-offsets.c, along side the other ARM
> specific buggy compiler test(s). I'm presently putting together such
> a patch.
>
> The information in the thread on linux-omap says only GCC 4.8.1 and
> GCC 4.8.2. Where do you get the other versions from?
The gcc PR linked in the commit message; see the "Known to fail" field.
Regards,
Peter Hurley
next prev parent reply other threads:[~2014-10-10 16:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-10 16:26 [PATCH] arm: Blacklist gcc 4.8.[012] and 4.9.0 with CONFIG_FRAME_POINTER Peter Hurley
2014-10-10 16:36 ` Russell King - ARM Linux
2014-10-10 16:55 ` Peter Hurley [this message]
2014-10-11 16:33 ` Mikael Pettersson
2014-10-11 18:04 ` Peter Hurley
2014-10-12 9:50 ` Mikael Pettersson
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=54380F86.10005@hurleysoftware.com \
--to=peter@hurleysoftware.com \
--cc=aaro.koskinen@iki.fi \
--cc=balbi@ti.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=rabin@rab.in \
/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).