mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: dick.streefland@altium.nl (Dick Streefland)
Cc: spam@altium.nl, linux-kernel@vger.kernel.org
Subject: Re: IA32 (2.6.2 - 2004-02-05.22.30) - 3 New warnings (gcc 3.2.2)
Date: Tue, 10 Feb 2004 07:44:50 -0800	[thread overview]
Message-ID: <20040210074450.3adcefdc.rddunlap@osdl.org> (raw)
In-Reply-To: <2e79.4028dd7d.6ae8c@altium.nl>

On Tue, 10 Feb 2004 13:32:45 -0000 spam@altium.nl (Dick Streefland) wrote:

| Linus Torvalds <torvalds@osdl.org> wrote:
| | On Fri, 6 Feb 2004 viro@parcelfarce.linux.theplanet.co.uk wrote:
| | > 
| | > Umm...  How about
| | > 
| | > static inline void BUG() __attribute__((noreturn));
| | > 
| | > static inline void BUG(void)
| | > {
| | > 	__asm__ ....
| | > }
| | 
| | Did you try that? Last time I tried, gcc would complain every time it saw 
| | the thing about "noreturn function does return".
| 
| So, make sure it won't return ;-)
| 
| static inline void BUG(void)
| {
|         __asm__ ("1: jmp 1b");
|         BUG();
| }

doesn't that sorta miss the BUG output?

--
~Randy
kernel-janitors project:  http://janitor.kernelnewbies.org/

  reply	other threads:[~2004-02-10 15:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-06 11:22 John Cherry
2004-02-06 11:33 ` viro
2004-02-06 16:52   ` Linus Torvalds
2004-02-06 18:22     ` viro
2004-02-06 18:35       ` Petr Vandrovec
2004-02-06 18:42       ` Linus Torvalds
2004-02-06 18:47         ` viro
2004-02-06 19:09           ` viro
2004-02-10 13:32         ` Dick Streefland
2004-02-10 15:44           ` Randy.Dunlap [this message]
2004-02-08  1:00 Jon Foster
2004-02-08  5:45 ` viro

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=20040210074450.3adcefdc.rddunlap@osdl.org \
    --to=rddunlap@osdl.org \
    --cc=dick.streefland@altium.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=spam@altium.nl \
    /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®