mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@osdl.org>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Matthias Andree <matthias.andree@gmx.de>,
	Linux-Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.9 BK build broken
Date: Mon, 18 Oct 2004 22:14:00 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.58.0410182208020.2287@ppc970.osdl.org> (raw)
In-Reply-To: <41748ADE.70403@pobox.com>



On Mon, 18 Oct 2004, Jeff Garzik wrote:
> > 
> > I get an ICE here in -BK-latest, which the attached patch fixes (backs 
> > out Linus's change).

Heh. Clearly there's a gcc bug.. What compiler version?

I've got gcc-3.2 and gcc-3.3, and neither seems to have any trouble, but 
hey, I'm cursed by having fairly up-to-date systems.

That said, I know what's up, but it would be good to know what compilers 
have this problem..

> Another data point, I have no problems with 2.6-BK-latest on x86-64, 
> with gcc 3.3.3 (FC2)...

Too much C syntax, too little CPP braindamage. 

I bet the thing is fixed by changing the

	#define __builtin_warning(x, ...) (1)

into

	#define __builtin_warning(x, y...) (1)

(ie add the name for the varargs macro argument). Never mind that we don't 
use it, and newer gcc's are happy - older gcc's clearly aren't ;)

		Linus

  reply	other threads:[~2004-10-19  5:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-19  2:17 Matthias Andree
2004-10-19  2:32 ` Jeff Garzik
2004-10-19  3:32   ` Jeff Garzik
2004-10-19  5:14     ` Linus Torvalds [this message]
2004-10-19  9:00       ` Matthias Andree
2004-10-19 16:05         ` Linus Torvalds
2004-10-19  9:23       ` SOLVED: " Matthias Andree
2004-10-19  5:10 ` Andrew Morton
2004-10-19  9:03   ` Matthias Andree

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.58.0410182208020.2287@ppc970.osdl.org \
    --to=torvalds@osdl.org \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthias.andree@gmx.de \
    /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®