From: "H. Peter Anvin" <hpa@zytor.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Kui Zhang <kuizhang@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Segmentation fault on all golang executables
Date: Thu, 12 Jun 2014 12:11:36 -0700 [thread overview]
Message-ID: <5399FB68.2000507@zytor.com> (raw)
In-Reply-To: <CALCETrWyC5B0EgdbxKr_VYN+bARGy55E_p2ppk-gW5sLc5jHWg@mail.gmail.com>
On 06/12/2014 11:51 AM, Andy Lutomirski wrote:
> On Thu, Jun 12, 2014 at 11:48 AM, H. Peter Anvin <hpa@linux.intel.com> wrote:
>> On 06/12/2014 11:42 AM, Andy Lutomirski wrote:
>>>
>>> Note that my hack will build a buggy vdso on big-endian hosts. Is
>>> there a way to convert host -> BE yet?
>>>
>>
>> Yes, use <tools/be_byteshift.h>.
>
> What should I rebase on for that? And wasn't there some header that
> was supposed to choose the right include file given the host runtime?
>
> Also, I meant host -> LE, of course, but that should be trivial.
>
No need to rebase. My patchset proposes replacing
<tools/be_byteshift.h> and <tools/le_byteshift.h> by a unified
<tools/unaligned.h> but that is not important for this purpose.
host -> LE uses <tools/le_byteshift.h> which is already in use by
vdso2c. Use put_unaligned_leXX().
-hpa
prev parent reply other threads:[~2014-06-12 19:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-12 16:59 Segmentation fault on all golang executables Kui Zhang
2014-06-12 17:20 ` Andy Lutomirski
2014-06-12 17:26 ` Andy Lutomirski
2014-06-12 17:36 ` Andy Lutomirski
[not found] ` <CAKx2Y1kTuK2cCn_uhVMgU5SeLsjXzHcFRmds7LP7-QG8BMqAdA@mail.gmail.com>
[not found] ` <CALCETrXnXp45iRC1h=_pOYrvXPc=hrTYnnVgsUg+i9URVfJTow@mail.gmail.com>
2014-06-13 5:47 ` Kui Zhang
2014-06-13 5:51 ` H. Peter Anvin
2014-06-12 18:38 ` Andy Lutomirski
2014-06-12 18:41 ` H. Peter Anvin
2014-06-12 18:42 ` Andy Lutomirski
2014-06-12 18:48 ` H. Peter Anvin
2014-06-12 18:51 ` Andy Lutomirski
2014-06-12 19:11 ` H. Peter Anvin [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=5399FB68.2000507@zytor.com \
--to=hpa@zytor.com \
--cc=kuizhang@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.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