From: "Martin Liška" <mliska@suse.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Sparse Mailing-list <linux-sparse@vger.kernel.org>,
Chris Li <sparse@chrisli.org>
Subject: Re: [PATCH 1/2] compiler/gcc5: Remove quirk for asm_volatile_goto()
Date: Wed, 15 Apr 2015 11:08:43 +0200 [thread overview]
Message-ID: <552E2A9B.7030605@suse.cz> (raw)
In-Reply-To: <CA+55aFzcyHJfP95EDZxOL7iCXg3HL42XqnMFoHFOSMhyGaKtMg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1213 bytes --]
On 04/14/2015 07:58 PM, Linus Torvalds wrote:
> On Tue, Apr 14, 2015 at 2:25 AM, Martin Liška <mliska@suse.cz> wrote:
>> Remove comments related to GCC 4.x branch and workaround for
>> asm_volatile_goto which is fixed in GCC 5 release.
>
> How sure are you that it is *really* fixed? Because it wasn't, last we saw.
>
> It was originally claimed to be fixed in 4.8.2, but that turned out to
> be wrong. See commit 5631b8fba640 ("compiler/gcc4+: Remove inaccurate
> comment about 'asm goto' miscompiles"), and
>
> https://lkml.org/lkml/2014/2/12/817
>
> which shows that the bugzilla you reference is at the very least
> unreliable. Apparently the gcc test-case didn't catch all the
> problems.
>
> IOW, just leave the workaround. It has no actual cost, and the gcc bug
> wasn't obviously fully fixed. There are apparently very few users of
> "asm goto" (probably partly because of the limitations of it,
> particularly the "no outputs").
>
> Linus
>
Hello Linus.
Agree with you that a bit more defensive approach is reasonable, mainly because
of the actual cost.
Thus, I send updated version of the patch which just removes unrelated GCC 4.x branch
comments.
Thanks,
Martin
[-- Attachment #2: 0001-compiler-gcc5-Remove-comments-related-to-GCC-4.x-bra.patch --]
[-- Type: text/x-patch, Size: 835 bytes --]
From 9db00c78af98a26685d3e0034d26962167441070 Mon Sep 17 00:00:00 2001
From: mliska <mliska@suse.cz>
Date: Wed, 15 Apr 2015 10:55:14 +0200
Subject: [PATCH 1/2] compiler/gcc5: Remove comments related to GCC 4.x branch.
Signed-off-by: Martin Liska <mliska@suse.cz>
---
include/linux/compiler-gcc5.h | 8 --------
1 file changed, 8 deletions(-)
diff --git a/include/linux/compiler-gcc5.h b/include/linux/compiler-gcc5.h
index efee493..abb03b8 100644
--- a/include/linux/compiler-gcc5.h
+++ b/include/linux/compiler-gcc5.h
@@ -12,10 +12,6 @@
like BUG(), printk(), panic() etc. [but let's keep them for now for
older compilers]
- Early snapshots of gcc 4.3 don't support this and we can't detect this
- in the preprocessor, but we can live with this because they're unreleased.
- Maketime probing would be overkill here.
prev parent reply other threads:[~2015-04-15 9:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-14 9:25 [PATCH 1/2] compiler/gcc5: Remove quirk for asm_volatile_goto() Martin Liška
2015-04-14 17:58 ` Linus Torvalds
2015-04-15 9:08 ` Martin Liška [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=552E2A9B.7030605@suse.cz \
--to=mliska@suse.cz \
--cc=linux-sparse@vger.kernel.org \
--cc=sparse@chrisli.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.