From: Jakub Jelinek <jakub@redhat.com>
To: Jiri Slaby <jslaby@suse.cz>
Cc: stable@vger.kernel.org, Steven Noonan <steven@uplinklabs.net>,
Ingo Molnar <mingo@kernel.org>,
Richard Henderson <rth@twiddle.net>,
Linus Torvalds <torvalds@linux-foundation.org>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [patch added to 3.12-stable] compiler/gcc4+: Remove inaccurate comment about 'asm goto' miscompiles
Date: Thu, 28 Jan 2016 12:03:47 +0100 [thread overview]
Message-ID: <20160128110347.GX3017@tucnak.redhat.com> (raw)
In-Reply-To: <1453978615-20487-2-git-send-email-jslaby@suse.cz>
On Thu, Jan 28, 2016 at 11:56:53AM +0100, Jiri Slaby wrote:
> From: Steven Noonan <steven@uplinklabs.net>
>
> This patch has been added to the 3.12 stable tree. If you have any
> objections, please let us know.
>
> ===============
>
> commit 5631b8fba640a4ab2f8a954f63a603fa34eda96b upstream.
>
> The bug referenced by the comment in this commit was not
> completely fixed in GCC 4.8.2, as I mentioned in a thread back
> in February:
>
> https://lkml.org/lkml/2014/2/12/797
If you suspect a GCC bug, better try to narrow it down to a reasonably sized
testcase, preprocess it and file in GCC bugzilla. Otherwise it will never
be fixed.
Jakub
next prev parent reply other threads:[~2016-01-28 11:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 10:56 [patch added to 3.12-stable] arm64: restore bogomips information in /proc/cpuinfo Jiri Slaby
2016-01-28 10:56 ` [patch added to 3.12-stable] compiler/gcc4+: Remove inaccurate comment about 'asm goto' miscompiles Jiri Slaby
2016-01-28 11:03 ` Jakub Jelinek [this message]
2016-01-29 8:55 ` Ingo Molnar
2016-01-28 10:56 ` [patch added to 3.12-stable] compiler-gcc: integrate the various compiler-gcc[345].h files Jiri Slaby
2016-01-28 10:56 ` [patch added to 3.12-stable] x86: vvar, fix excessive gcc-6 DECLARE_VVAR warnings Jiri Slaby
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=20160128110347.GX3017@tucnak.redhat.com \
--to=jakub@redhat.com \
--cc=jslaby@suse.cz \
--cc=mingo@kernel.org \
--cc=rostedt@goodmis.org \
--cc=rth@twiddle.net \
--cc=stable@vger.kernel.org \
--cc=steven@uplinklabs.net \
--cc=torvalds@linux-foundation.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).