[go-nuts] Re: SIGILL running 1.14 on macOS

[James Pettyjohn]

Sooner the better, it's crept into downstream packages. E.g. docker 
installed via brew is toast as it was built in 1.14.

On Wednesday, March 4, 2020 at 1:16:13 PM UTC-8, Jon Conradt wrote:
>
> You can follow the progress toward 1.14.1 via 
> https://github.com/golang/go/milestone/137
>
> Looking at 1.13.0 and 1.12.0 it looks like the time between a .0 release 
> and a .0 release is about three weeks. So I'm hoping for a St. Patrick's 
> Day releases of 1.14.1
>
> Jon
>

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/e30f0353-e0df-4970-b319-9cc2e8e595ff%40googlegroups.com.

[go-nuts] Re: SIGILL running 1.14 on macOS

[Jon Conradt]

You can follow the progress toward 1.14.1 
via https://github.com/golang/go/milestone/137

Looking at 1.13.0 and 1.12.0 it looks like the time between a .0 release 
and a .0 release is about three weeks. So I'm hoping for a St. Patrick's 
Day releases of 1.14.1

Jon

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/a1e83ff5-5544-4129-bc44-bfd8e5f98fbc%40googlegroups.com.

[go-nuts] Re: SIGILL running 1.14 on macOS

[Jon Conradt]

I am looking forward to 1.14.1, this ruined my Saturday. :(

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/50ae204b-6240-4a83-a8df-61d580dc4de8%40googlegroups.com.

[go-nuts] Re: SIGILL running 1.14 on macOS

[James Pettyjohn]

Looks like this was already resolved for 1.14.1 
.

On Wednesday, February 26, 2020 at 11:00:24 AM UTC-8, James Pettyjohn wrote:
>
> A little further digging shows that VZEROUPPER is part of the AVX 
> instruction set, not supported on any Apple computers prior to 2011 from 
> what I can tell.
>
> Given the rc1 code worked fine, that could be an alternative for Darwin 
> where the CPU does not support AVX. While not ideal, I'd argue it's better 
> than cutting off support for these machines which can run High Sierra. Once 
> support for High Sierra is dropped then it should not matter as it takes a 
> 2013 or later model to run anything after High Sierra.
>
> - James
>
>
>
> On Wednesday, February 26, 2020 at 10:29:33 AM UTC-8, James Pettyjohn 
> wrote:
>>
>> I am trying to run go1.14 on macOS 10.13.2 with on a late 2009 iMac with 
>> an i7 but always get the same crash:
>>
>>
>> SIGILL: illegal instruction
>> PC=0x1066040 m=0 sigcode=1
>>
>>
>> goroutine 1 [running, locked to thread]:
>> runtime.asyncPreempt()
>> /usr/local/go/src/runtime/preempt_amd64.s:8 fp=0xc58ef0 sp=
>> 0xc58ee8 pc=0x1066040
>> fmt.init()
>> /usr/local/go/src/fmt/scan.go:465 fp=0xc58ef8 sp=0xc58ef0 
>> pc=0x10e6540
>> runtime.doInit(0x1a80520)
>> /usr/local/go/src/runtime/proc.go:5414 +0x8a fp=0xc58f28 sp=
>> 0xc58ef8 pc=0x1043aca
>> runtime.doInit(0x1a80ec0)
>> /usr/local/go/src/runtime/proc.go:5409 +0x57 fp=0xc58f58 sp=
>> 0xc58f28 pc=0x1043a97
>> runtime.doInit(0x1a850c0)
>> /usr/local/go/src/runtime/proc.go:5409 +0x57 fp=0xc58f88 sp=
>> 0xc58f58 pc=0x1043a97
>> runtime.main()
>> /usr/local/go/src/runtime/proc.go:190 +0x1ce fp=0xc58fe0 sp=
>> 0xc58f88 pc=0x103702e
>> runtime.goexit()
>> /usr/local/go/src/runtime/asm_amd64.s:1373 +0x1 fp=0xc58fe8 
>> sp=0xc58fe0 pc=0x10647d1
>>
>>
>> rax0x1a80520
>> rbx0xb
>> rcx0x0
>> rdx0x1a80578
>> rdi0xcb2020
>> rsi0x10e6540
>> rbp0xc58f18
>> rsp0xc58ee8
>> r8 0x3277901
>> r9 0x203000
>> r100x8
>> r110x55
>> r120x1
>> r130x55
>> r140x171acac
>> r150x38
>> rip0x1066040
>> rflags 0x10202
>> cs 0x2b
>> fs 0x0
>> gs 0x0
>>
>>
>> Which appears to be a call to VZEROUPPER in preempt_amd64.s 
>> 
>> .
>>
>> This was not the case in rc1, which runs just fine. I get the same 
>> results from installing it with brew, .pkg and .tgz installs - have done 
>> the install from source yet.
>>
>> Any tips would be appreciated.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/ebfc97e6-bf43-46cc-bfbd-cbe4b756353d%40googlegroups.com.

[go-nuts] Re: SIGILL running 1.14 on macOS

[James Pettyjohn]

A little further digging shows that VZEROUPPER is part of the AVX 
instruction set, not supported on any Apple computers prior to 2011 from 
what I can tell.

Given the rc1 code worked fine, that could be an alternative for Darwin 
where the CPU does not support AVX. While not ideal, I'd argue it's better 
than cutting off support for these machines which can run High Sierra. Once 
support for High Sierra is dropped then it should not matter as it takes a 
2013 or later model to run anything after High Sierra.

- James



On Wednesday, February 26, 2020 at 10:29:33 AM UTC-8, James Pettyjohn wrote:
>
> I am trying to run go1.14 on macOS 10.13.2 with on a late 2009 iMac with 
> an i7 but always get the same crash:
>
>
> SIGILL: illegal instruction
> PC=0x1066040 m=0 sigcode=1
>
>
> goroutine 1 [running, locked to thread]:
> runtime.asyncPreempt()
> /usr/local/go/src/runtime/preempt_amd64.s:8 fp=0xc58ef0 sp=
> 0xc58ee8 pc=0x1066040
> fmt.init()
> /usr/local/go/src/fmt/scan.go:465 fp=0xc58ef8 sp=0xc58ef0 
> pc=0x10e6540
> runtime.doInit(0x1a80520)
> /usr/local/go/src/runtime/proc.go:5414 +0x8a fp=0xc58f28 sp=
> 0xc58ef8 pc=0x1043aca
> runtime.doInit(0x1a80ec0)
> /usr/local/go/src/runtime/proc.go:5409 +0x57 fp=0xc58f58 sp=
> 0xc58f28 pc=0x1043a97
> runtime.doInit(0x1a850c0)
> /usr/local/go/src/runtime/proc.go:5409 +0x57 fp=0xc58f88 sp=
> 0xc58f58 pc=0x1043a97
> runtime.main()
> /usr/local/go/src/runtime/proc.go:190 +0x1ce fp=0xc58fe0 sp=
> 0xc58f88 pc=0x103702e
> runtime.goexit()
> /usr/local/go/src/runtime/asm_amd64.s:1373 +0x1 fp=0xc58fe8 sp
> =0xc58fe0 pc=0x10647d1
>
>
> rax0x1a80520
> rbx0xb
> rcx0x0
> rdx0x1a80578
> rdi0xcb2020
> rsi0x10e6540
> rbp0xc58f18
> rsp0xc58ee8
> r8 0x3277901
> r9 0x203000
> r100x8
> r110x55
> r120x1
> r130x55
> r140x171acac
> r150x38
> rip0x1066040
> rflags 0x10202
> cs 0x2b
> fs 0x0
> gs 0x0
>
>
> Which appears to be a call to VZEROUPPER in preempt_amd64.s 
> .
>
> This was not the case in rc1, which runs just fine. I get the same results 
> from installing it with brew, .pkg and .tgz installs - have done the 
> install from source yet.
>
> Any tips would be appreciated.
>

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/3ca625a5-c45e-4f05-92f9-36e3e61ff739%40googlegroups.com.