From: Keir Fraser <keir@xensource.com>
To: "Woller, Thomas" <thomas.woller@amd.com>,
Tim Deegan <Tim.Deegan@xensource.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Cs/ 14346 breaks 64bit hv
Date: Wed, 14 Mar 2007 15:57:25 +0000 [thread overview]
Message-ID: <C21DCBE5.B78F%keir@xensource.com> (raw)
In-Reply-To: <683860AD674C7348A0BF0DE3918482F6048FB67C@SAUSEXMB1.amd.com>
On 14/3/07 15:00, "Woller, Thomas" <thomas.woller@amd.com> wrote:
> Sure does look like the code generated isn't correct with older bcc..
> But a few more tests will confirm or deny.
If this is the case I think we should explicitly check for a recent enough
bcc during the build, and print a warning (and not build) the rombios if the
dev86 tools are too old. We don't want to have to be worrying about broken
toolchains if we can avoid it.
-- Keir
next prev parent reply other threads:[~2007-03-14 15:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-13 23:01 Cs/ 14346 breaks 64bit hv Woller, Thomas
2007-03-14 6:47 ` Woller, Thomas
2007-03-14 9:34 ` Tim Deegan
2007-03-14 9:56 ` Tim Deegan
2007-03-14 15:00 ` Woller, Thomas
2007-03-14 15:57 ` Keir Fraser [this message]
2007-03-14 16:54 ` Tim Deegan
2007-03-14 17:14 ` Woller, Thomas
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=C21DCBE5.B78F%keir@xensource.com \
--to=keir@xensource.com \
--cc=Tim.Deegan@xensource.com \
--cc=thomas.woller@amd.com \
--cc=xen-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.