Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #1011673

Bug#960674: golang-go: "fatal error: gc_trigger underflow" on mipsel

Cross-posted to 2 groups.

Show all headers | View raw

Adrian Bunk <bunk@debian.org> 于2020年5月21日周四 下午3:40写道：
>
> On Thu, May 21, 2020 at 06:41:34AM +0800, YunQiang Su wrote:
> > Adrian Bunk <bunk@debian.org> 于2020年5月21日周四 上午4:44写道：
> > >
> > > On Tue, May 19, 2020 at 11:43:30AM +0800, Shengjing Zhu wrote:
> > > >
> > > > FTR, after giving back golang-1.14 mipsel several times, it's finally
> > > > built, by a longson builder.
> > > > So I guess it only occurs on octeon. Since the porterbox eller is also
> > > > octeon, it also can't build any go program.
> > >
> > > On eller golang-1.14 fails to build both in sid and buster chroots.
> > >
> > > golang-1.11 also fails to build in a buster chroot with floating point
> > > test errors.
> > >
> > > golang-1.14 gets unbroken by GOMIPS=softfloat.
> > >
> > > The only kernel configuration change on eller in the buster point
> > > release is CONFIG_MIPS_O32_FP64_SUPPORT=y, everything observed would
> > > make sense if the problem is that golang-1.11 and golang-1.14 are
> > > not compatible with CONFIG_MIPS_O32_FP64_SUPPORT.
> >
> > It is just support O32_FP64. I don't expect it will have any effect.
> > Since currently, the toolchain/libraries are all FPXX.
>
> Only the gcc/binutils toolchain/libraries or also the Go toolchain?

you are right. the current golang still output FP32 object...
So, we think that it is buggy.

Since Loongson CPU has some strange behaviour, it even can work...
Let's try to patch golang to support FPXX or FP64.

https://github.com/golang/go/issues/39289

>
> Go has its own compiler.
> Go has its own linker.
>
> You do not need binutils installed for building Go programs.
>
> cu
> Adrian

Back to linux.debian.bugs.dist | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Bug#960674: golang-go: "fatal error: gc_trigger underflow" on mipsel Shengjing Zhu <zhsj@debian.org> - 2020-05-19 05:50 +0200
  Bug#960674: golang-go: "fatal error: gc_trigger underflow" on mipsel Adrian Bunk <bunk@debian.org> - 2020-05-20 22:50 +0200
    Bug#960674: golang-go: "fatal error: gc_trigger underflow" on mipsel YunQiang Su <syq@debian.org> - 2020-05-21 00:50 +0200
      Bug#960674: golang-go: "fatal error: gc_trigger underflow" on mipsel Adrian Bunk <bunk@debian.org> - 2020-05-21 09:50 +0200
        Bug#960674: golang-go: "fatal error: gc_trigger underflow" on mipsel YunQiang Su <syq@debian.org> - 2020-05-28 03:10 +0200
          Bug#960674: golang-go: "fatal error: gc_trigger underflow" on mipsel Aurelien Jarno <aurelien@aurel32.net> - 2020-05-29 23:10 +0200
            Bug#960674: golang-go: "fatal error: gc_trigger underflow" on mipsel Adrian Bunk <bunk@debian.org> - 2020-05-30 09:00 +0200
            Bug#960674: golang-go: "fatal error: gc_trigger underflow" on mipsel Adrian Bunk <bunk@debian.org> - 2020-06-08 19:20 +0200
          Re: Bug#960674: golang-go: "fatal error: gc_trigger underflow" on mipsel Shengjing Zhu <zhsj@debian.org> - 2020-06-24 20:20 +0200
            Re: Bug#960674: golang-go: "fatal error: gc_trigger underflow" on mipsel YunQiang Su <syq@debian.org> - 2020-06-25 03:00 +0200
      Bug#960674: golang-go: "fatal error: gc_trigger underflow" on mipsel Florian Weimer <fw@deneb.enyo.de> - 2020-05-30 12:30 +0200

csiph-web