mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: David Daney <ddaney@caviumnetworks.com>
Cc: gcc@gcc.gnu.org, Alan Cox <alan@lxorguk.ukuu.org.uk>,
	linux-mips <linux-mips@linux-mips.org>,
	linux-kernel@vger.kernel.org,
	Adam Nemet <anemet@caviumnetworks.com>
Subject: Re: [PATCH] MIPS: Make BUG() __noreturn.
Date: Fri, 21 Nov 2008 19:46:43 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.64.0811211940450.29539@anakin> (raw)
In-Reply-To: <4926E499.4070706@caviumnetworks.com>

On Fri, 21 Nov 2008, David Daney wrote:
> Geert Uytterhoeven wrote:
> > On Fri, 21 Nov 2008, Alan Cox wrote:
> > > On Thu, 20 Nov 2008 17:26:36 -0800
> > > David Daney <ddaney@caviumnetworks.com> wrote:
> > > 
> > > > MIPS: Make BUG() __noreturn.
> > > > 
> > > > Often we do things like put BUG() in the default clause of a case
> > > > statement.  Since it was not declared __noreturn, this could sometimes
> > > > lead to bogus compiler warnings that variables were used
> > > > uninitialized.
> > > > 
> > > > There is a small problem in that we have to put a magic while(1); loop
> > > > to
> > > > fool GCC into really thinking it is noreturn.  
> > > That sounds like your __noreturn macro is wrong.
> > > 
> > > Try using __attribute__ ((__noreturn__))
> > > 
> > > if that works then fix up the __noreturn definitions for the MIPS and gcc
> > > you have.
> > 
> > Nope, gcc is too smart:
> > 
> > $ cat a.c
> > 
> > int f(void) __attribute__((__noreturn__));
> > 
> > int f(void)
> > {
> > }
> > 
> > $ gcc -c -Wall a.c
> > a.c: In function f:
> > a.c:6: warning: `noreturn' function does return
> > $ 
> 
> That's right.
> 
> I was discussing this issue with my colleague Adam Nemet, and we came
> up with a couple of options:
> 
> 1) Enhance the _builtin_trap() function so that we can specify the
>   break code that is emitted.  This would allow us to do something
>   like:
> 
> static inline void __attribute__((noreturn)) BUG()
> {
> 	__builtin_trap(0x200);
> }
> 
> 2) Create a new builtin '__builtin_noreturn()' that expands to nothing
>   but has no CFG edges leaving it, which would allow:
> 
> static inline void __attribute__((noreturn)) BUG()
> {
> 	__asm__ __volatile__("break %0" : : "i" (0x200));
> 	__builtin_noreturn();
> }

Now I remember, yes, __builtin_trap() is how we fixed it on m68k:

http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=e8006b060f3982a969c5170aa869628d54dd30d8

Of course, if you need a different trap code than the default, you're in
trouble.

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds

  reply	other threads:[~2008-11-21 18:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-21  1:26 David Daney
2008-11-21 10:00 ` Alan Cox
2008-11-21 10:27   ` Geert Uytterhoeven
2008-11-21 11:14     ` Maciej W. Rozycki
2008-11-21 12:58       ` Andreas Schwab
2008-11-21 16:40     ` David Daney
2008-11-21 18:46       ` Geert Uytterhoeven [this message]
2008-11-21 22:16         ` Ralf Baechle
2008-11-24 19:04           ` Maciej W. Rozycki
2008-11-21 23:00 ` Andrew Morton
2008-11-21 23:48   ` David Daney
2008-11-23  9:58   ` Ingo Molnar
2008-11-24  9:20     ` Ralf Baechle
2008-11-25  0:16     ` Jeremy Fitzhardinge
2008-11-22  9:39 ` Ralf Baechle

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=Pine.LNX.4.64.0811211940450.29539@anakin \
    --to=geert@linux-m68k.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=anemet@caviumnetworks.com \
    --cc=ddaney@caviumnetworks.com \
    --cc=gcc@gcc.gnu.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.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

all inboxes | Powered by JetHome®