On 06/12/2014 10:47 PM, Kui Zhang wrote:
> Thanks for the patches. The workaround works.
>
> Stupid idea, maybe something in dmesg to help spark conversions, when
> this workaround is hit?
>
> Looks like golang people are close.
>
The kernel won't even know.
-hpa
--
To unsubscribe fr
Thanks for the patches. The workaround works.
Stupid idea, maybe something in dmesg to help spark conversions, when
this workaround is hit?
Looks like golang people are close.
Thanks
Kuiz
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majo
On 06/12/2014 11:51 AM, Andy Lutomirski wrote:
> On Thu, Jun 12, 2014 at 11:48 AM, H. Peter Anvin 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 .
>
>
On Thu, Jun 12, 2014 at 11:48 AM, H. Peter Anvin 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 .
What should I rebase on for that? And wasn't there some he
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 .
-hpa
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to major
On Thu, Jun 12, 2014 at 11:41 AM, H. Peter Anvin wrote:
> On 06/12/2014 11:38 AM, Andy Lutomirski wrote:
>>>
>>> 2. Write a dummy section table that contains a single empty section of
>>> type SHT_DYNSYM. Hopefully the Go runtime will then get far enough to
>>> fail cleanly. And they can go and
On 06/12/2014 11:38 AM, Andy Lutomirski wrote:
>>
>> 2. Write a dummy section table that contains a single empty section of
>> type SHT_DYNSYM. Hopefully the Go runtime will then get far enough to
>> fail cleanly. And they can go and write a real ELF parser or copy my
>> reference parser correctl
On Thu, Jun 12, 2014 at 10:20 AM, Andy Lutomirski wrote:
> On Thu, Jun 12, 2014 at 9:59 AM, Kui Zhang wrote:
>> Hello,
>>
>> This commit seem to cause Segmentation fault on any of my golang executables.
>
> Well, crap. It looks like the Go people took my sample vDSO parser...
> and broke it. WT
On Thu, Jun 12, 2014 at 10:26 AM, Andy Lutomirski wrote:
> On Thu, Jun 12, 2014 at 10:20 AM, Andy Lutomirski wrote:
>> On Thu, Jun 12, 2014 at 9:59 AM, Kui Zhang wrote:
>>> Hello,
>>>
>>> This commit seem to cause Segmentation fault on any of my golang
>>> executables.
>
> Can you send me a gol
On Thu, Jun 12, 2014 at 10:20 AM, Andy Lutomirski wrote:
> On Thu, Jun 12, 2014 at 9:59 AM, Kui Zhang wrote:
>> Hello,
>>
>> This commit seem to cause Segmentation fault on any of my golang executables.
Can you send me a golang executable that doesn't work. I just build
the "hello world" exampl
On Thu, Jun 12, 2014 at 9:59 AM, Kui Zhang wrote:
> Hello,
>
> This commit seem to cause Segmentation fault on any of my golang executables.
Well, crap. It looks like the Go people took my sample vDSO parser...
and broke it. WTF were they thinking? I should have noticed that
they screwed it up
11 matches
Mail list logo
