From: Segher Boessenkool <segher@kernel.crashing.org>
To: Nicholas Piggin <npiggin@gmail.com>
Cc: linux-kernel@vger.kernel.org, Paul Mackerras <paulus@samba.org>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] powerpc/bug: Remove specific powerpc BUG_ON()
Date: Thu, 11 Feb 2021 05:50:59 -0600 [thread overview]
Message-ID: <20210211115059.GB28121@gate.crashing.org> (raw)
In-Reply-To: <1613036567.zvyupcz926.astroid@bobo.none>
On Thu, Feb 11, 2021 at 08:04:55PM +1000, Nicholas Piggin wrote:
> It would be nice if we could have a __builtin_trap_if that gcc would use
> conditional traps with, (and which never assumes following code is
> unreachable even for constant true, so we can use it with WARN and put
> explicit unreachable for BUG).
It automatically does that with just __builtin_trap, see my other mail :-)
Segher
WARNING: multiple messages have this Message-ID (diff)
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Nicholas Piggin <npiggin@gmail.com>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
Michael Ellerman <mpe@ellerman.id.au>,
Paul Mackerras <paulus@samba.org>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] powerpc/bug: Remove specific powerpc BUG_ON()
Date: Thu, 11 Feb 2021 05:50:59 -0600 [thread overview]
Message-ID: <20210211115059.GB28121@gate.crashing.org> (raw)
In-Reply-To: <1613036567.zvyupcz926.astroid@bobo.none>
On Thu, Feb 11, 2021 at 08:04:55PM +1000, Nicholas Piggin wrote:
> It would be nice if we could have a __builtin_trap_if that gcc would use
> conditional traps with, (and which never assumes following code is
> unreachable even for constant true, so we can use it with WARN and put
> explicit unreachable for BUG).
It automatically does that with just __builtin_trap, see my other mail :-)
Segher
next prev parent reply other threads:[~2021-02-11 12:10 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-11 7:41 [PATCH] powerpc/bug: Remove specific powerpc BUG_ON() Christophe Leroy
2021-02-11 7:41 ` Christophe Leroy
2021-02-11 10:04 ` Nicholas Piggin
2021-02-11 10:04 ` Nicholas Piggin
2021-02-11 11:50 ` Segher Boessenkool [this message]
2021-02-11 11:50 ` Segher Boessenkool
2021-02-11 22:47 ` Nicholas Piggin
2021-02-11 22:47 ` Nicholas Piggin
2021-02-11 12:22 ` Segher Boessenkool
2021-02-11 12:22 ` Segher Boessenkool
2021-02-11 11:49 ` Segher Boessenkool
2021-02-11 11:49 ` Segher Boessenkool
2021-02-11 12:26 ` Christophe Leroy
2021-02-11 12:26 ` Christophe Leroy
2021-02-11 12:39 ` Segher Boessenkool
2021-02-11 12:39 ` Segher Boessenkool
2021-02-11 14:09 ` Christophe Leroy
2021-02-11 14:09 ` Christophe Leroy
2021-02-11 14:30 ` Segher Boessenkool
2021-02-11 14:30 ` Segher Boessenkool
2021-02-11 15:30 ` Christophe Leroy
2021-02-11 15:30 ` Christophe Leroy
2021-02-27 10:31 ` Christophe Leroy
2021-02-27 10:31 ` Christophe Leroy
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=20210211115059.GB28121@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.com \
--cc=paulus@samba.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.