From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Saul Wold <sgw@linux.intel.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/3] wic: remove systemd-boot for x32
Date: Thu, 21 Sep 2017 09:17:07 +0100 [thread overview]
Message-ID: <1505981827.18640.156.camel@linuxfoundation.org> (raw)
In-Reply-To: <20170919182734.15741-3-sgw@linux.intel.com>
On Tue, 2017-09-19 at 11:27 -0700, Saul Wold wrote:
> Currently systemd-boot actually incorporates libgcc, since the
> systemd-boot needs to be built with 64bit instructions it can not
> use the x32 based libgcc.
I'm a little confused by this since the point of x32 is that it uses
all the 64 bit instructions with a 32 bit address space?
Cheers,
Richard
next prev parent reply other threads:[~2017-09-21 8:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-19 18:27 [PATCH 0/3] Disable systemd-boot from building with x32 IA Machine Saul Wold
2017-09-19 18:27 ` [PATCH 1/3] arch-x86: Add x86-x32 to MACHINEOVERRIDES Saul Wold
2017-09-21 8:15 ` Richard Purdie
2017-09-26 0:46 ` Saul Wold
2017-09-19 18:27 ` [PATCH 2/3] wic: remove systemd-boot for x32 Saul Wold
2017-09-21 8:17 ` Richard Purdie [this message]
2017-09-21 14:22 ` Khem Raj
2017-09-19 18:27 ` [PATCH 3/3] systemd-boot: Should not build x32 Saul Wold
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=1505981827.18640.156.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=sgw@linux.intel.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.