From owner-freebsd-current Wed Jul 19 19:31:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id CF2ED37B890 for ; Wed, 19 Jul 2000 19:31:14 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id TAA10301; Wed, 19 Jul 2000 19:31:13 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id TAA15177; Wed, 19 Jul 2000 19:31:12 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Wed, 19 Jul 2000 19:31:12 -0700 (PDT) Message-Id: <200007200231.TAA15177@vashon.polstra.com> To: hm@hcs.de Subject: Re: kernel compile failure without -O option In-Reply-To: <20000719144614.7FE52483D@hcswork.hcs.de> References: <20000719144614.7FE52483D@hcswork.hcs.de> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <20000719144614.7FE52483D@hcswork.hcs.de>, Hellmuth Michaelis wrote: > > In the process of tracing down the problem of the kernel panic when booting > a kernel with pcvt enabled, i tried to compile a kernel without the -O > option to gcc and got this compile failure (sources from 18.7.2000 9:00 MET): > > cc -c -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes > -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual > -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include > -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 > -fomit-frame-pointer ../../i386/i386/atomic.c > In file included from ../../i386/i386/atomic.c:47: > machine/atomic.h: In function `atomic_set_char': > machine/atomic.h:106: inconsistent operand constraints in an `asm' > machine/atomic.h: In function `atomic_clear_char': > machine/atomic.h:107: inconsistent operand constraints in an `asm' [...] I have seen that same problem recently in a slightly different context. After staring at the code for a very long time, I could only conclude that the problem was a bug in gcc. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message