From: Linus Torvalds <torvalds@linux-foundation.org>
To: Ulrich Drepper <drepper@redhat.com>
Cc: akpm@linux-foundation.org, mingo@elte.hu, tglx@linutronix.de,
linux-kernel@vger.kernel.org,
user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] [PATCH] fix UML on x86-64
Date: Tue, 6 May 2008 16:27:27 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.1.10.0805061625090.32269@woody.linux-foundation.org> (raw)
In-Reply-To: <200805062304.m46N4h6d007206@devserv.devel.redhat.com>
On Tue, 6 May 2008, Ulrich Drepper wrote:
>
> This patch breaks UML for me on x86-64 running Fedora 8 (gcc 4.1.2):
It breaks things how?
Because on x86, the cut-off is gcc4 vs pre-4. See arch/x86/Makefile:
KBUILD_CFLAGS += $(shell if [ $(call cc-version) -lt 0400 ] ; then \
echo $(call cc-option,-fno-unit-at-a-time); fi ;)
and it's a bit distressing that these compiler flags are set two different
ways (in fact, I was already bothered by the fact that UML sets it totally
independently of x86 in the first place).
So what is the UML failure behaviour with gcc-4.1.2?
Linus
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2008-05-06 23:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-06 23:04 [uml-devel] [PATCH] fix UML on x86-64 Ulrich Drepper
2008-05-06 23:27 ` Linus Torvalds [this message]
2008-05-06 23:38 ` Ulrich Drepper
2008-05-07 0:06 ` Linus Torvalds
2008-05-07 0:15 ` Linus Torvalds
2008-05-07 1:48 ` Jeff Dike
2008-05-07 1:31 ` Jeff Dike
2008-05-07 3:26 ` Jeff Dike
2008-05-07 4:00 ` Jeff Dike
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=alpine.LFD.1.10.0805061625090.32269@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=drepper@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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