From: Benjamin Herrenschmidt <benh@au1.ibm.com>
To: Anton Blanchard <anton@samba.org>
Cc: linuxppc-dev@lists.ozlabs.org, paulus@samba.org,
wschmidt@us.ibm.com, Alan Modra <amodra@gmail.com>
Subject: Re: BUG_ON and gcc don't mix
Date: Tue, 20 Aug 2013 14:24:03 +1000 [thread overview]
Message-ID: <1376972643.25016.109.camel@pasglop> (raw)
In-Reply-To: <20130820123750.7353f2f1@kryten>
On Tue, 2013-08-20 at 12:37 +1000, Anton Blanchard wrote:
> 0: 00 00 23 a1 lhz r9,0(r3)
> 4: 01 00 60 38 li r3,1
> 8: 20 00 a9 0c twlgei r9,32
> c: 20 00 80 4e blr
>
> Nice! I remember chasing this down before and the issue is we need the
> address of the trap instruction for our bug exception table. Maybe
> we need a gcc builtin in which we can get a label on the trap
> instruction. Would that be possible?
I suppose we can always just do a label before builtin_trap and have
the BUG code search a few instructions :-)
Cheers,
Ben.
next prev parent reply other threads:[~2013-08-20 4:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-20 2:37 BUG_ON and gcc don't mix Anton Blanchard
2013-08-20 4:24 ` Benjamin Herrenschmidt [this message]
2013-08-20 4:32 ` Alan Modra
2013-08-20 4:45 ` Alan Modra
2013-08-20 8:36 ` David Laight
2013-08-20 10:55 ` Anton Blanchard
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=1376972643.25016.109.camel@pasglop \
--to=benh@au1.ibm.com \
--cc=amodra@gmail.com \
--cc=anton@samba.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.org \
--cc=wschmidt@us.ibm.com \
/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).