From: "Udo A. Steinberg" <us15@os.inf.tu-dresden.de>
To: Linus Torvalds <torvalds@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [OOPS] Linux-2.6.0-test9
Date: Mon, 3 Nov 2003 05:49:42 +0100 [thread overview]
Message-ID: <20031103054942.4d6c985e.us15@os.inf.tu-dresden.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0311022042390.18647-100000@home.osdl.org>
[-- Attachment #1: Type: text/plain, Size: 808 bytes --]
On Sun, 2 Nov 2003 20:45:55 -0800 (PST) Linus Torvalds (LT) wrote:
LT> Btw, what compiler version do you have? The UP+preempt bug is a real bug,
LT> but as far as I've been able to find out it's almost impossible to get gcc
LT> to actually generate code that might trigger it. So while it's entirely
LT> possible that the bug you're seeing is due to the (now fixed) UP+preempt
LT> bug, it's also quite possible that there's something else going on too.
I'm using gcc 3.3.2.
Reading specs from /usr/lib/gcc-lib/i486-slackware-linux/3.3.2/specs
Configured with: ../gcc-3.3.2/configure --prefix=/usr --enable-shared
--enable-threads=posix --enable-__cxa_atexit --disable-checking --with-gnu-ld
--verbose --target=i486-slackware-linux --host=i486-slackware-linux
Thread model: posix
gcc version 3.3.2
-Udo.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-11-03 4:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-02 23:09 Udo A. Steinberg
2003-11-02 23:19 ` Udo A. Steinberg
2003-11-03 3:01 ` Linus Torvalds
2003-11-03 3:56 ` Udo A. Steinberg
2003-11-03 4:45 ` Linus Torvalds
2003-11-03 4:49 ` Udo A. Steinberg [this message]
[not found] ` <5.1.0.14.2.20031103110914.00b671f0@caffeine.cc.com.au>
2003-11-03 3:48 ` Udo A. Steinberg
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=20031103054942.4d6c985e.us15@os.inf.tu-dresden.de \
--to=us15@os.inf.tu-dresden.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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®