From: Samuel Thibault <samuel.thibault@eu.citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: Aron Griffis <aron@hp.com>,
xen-devel@lists.xensource.com,
xen-ia64-devel@lists.xensource.com
Subject: Re: Re: [Xen-devel] [PATCH 2 of 2] cross-build fixes in ioemu-remote
Date: Thu, 31 Jul 2008 16:34:58 +0100 [thread overview]
Message-ID: <20080731153458.GS4678@implementation.uk.xensource.com> (raw)
In-Reply-To: <18577.55125.163478.822929@mariner.uk.xensource.com>
Ian Jackson, le Thu 31 Jul 2008 16:16:37 +0100, a écrit :
> Aron Griffis writes ("[Xen-devel] [PATCH 2 of 2] cross-build fixes in ioemu-remote"):
> > Partly fix cross-building in ioemu-remote:
> >
> > - The ioemu version of cc-option doesn't take $(CC) as the first
> > argument, so all builds were getting -msse2 regardless of
> > architecture.
>
> I'll commit this in just a moment.
Mmm, actually I think we don't need that sse2 option any more: thanks
to dirty bit tracking, the sse2-optimized memcmp loop is gone. At least
-DUSE_SSE2 is not used anywhere.
Samuel
prev parent reply other threads:[~2008-07-31 15:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-31 14:51 [PATCH 0 of 2] partly fix cross-build of ioemu-remote Aron Griffis
2008-07-31 14:51 ` [PATCH 1 of 2] pass IOEMU_CONFIGURE_CROSS to ioemu-remote/xen-setup Aron Griffis
2008-07-31 14:51 ` [PATCH 2 of 2] cross-build fixes in ioemu-remote Aron Griffis
[not found] ` <m2n.s.1KOZmg-002Rh9@chiark.greenend.org.uk>
2008-07-31 15:16 ` [Xen-devel] " Ian Jackson
2008-07-31 15:29 ` [Xen-ia64-devel] " Samuel Thibault
2008-07-31 16:48 ` Ian Jackson
2008-07-31 19:21 ` Aron Griffis
2008-08-01 16:26 ` Ian Jackson
2008-08-01 17:22 ` Re: [Xen-devel] " Aron Griffis
2008-08-04 22:31 ` [Xen-ia64-devel] " Aron Griffis
2008-08-05 7:40 ` Keir Fraser
2008-08-11 9:15 ` Re: [Xen-devel] " Ian Jackson
2008-07-31 15:34 ` Samuel Thibault [this message]
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=20080731153458.GS4678@implementation.uk.xensource.com \
--to=samuel.thibault@eu.citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=aron@hp.com \
--cc=xen-devel@lists.xensource.com \
--cc=xen-ia64-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.