Re: Bug#886294: transition: nodejs

[Aurelien Jarno <aurelien@aurel32.net>]

On 2018-01-24 13:24, Emilio Pozuelo Monfort wrote:
> On 23/01/18 19:21, Jérémy Lal wrote:
> > cc-ing s390x team to ask (re)building nodejs-8.9.3~dfsg-11 on zemlinsky.
> > 
> >             but on s390x you're getting
> >             illegal instructions on zemlinsky, which is a Z10 mainframe. Looks
> >             like newer
> >             node possibly bumped the baseline, or just accidentally introduced
> >             instructions
> >             not supported by our baseline.
> > 
> > 
> >         Starting investigations about that. Hopefully it's a change that could
> >         have been
> >         backward-compatible.
> > 
> > 
> > nodejs/v8 somewhat officially support s390x down to z196.
> > I removed the added march=z196 flag and uploaded it into nodejs-8.9.3~dfsg-11.
> > It would be wonderful to build it on zemlinsky to see what happens.
> 
> Still fails: https://buildd.debian.org/status/package.php?p=node-srs&suite=sid

I requeued nodejs on zemlinsky and it also failed. After a quick check,
it appears that It uses he load/store on condition 1 facility directly,
ie not in GCC generated code. The change is therefore intentional. This
facility has been introduced with the z196.

> Our baseline is z10, and z196 is newer. So if upstream now requires z196, we
> have three options:

Officially our baseline is still z900.

> - Revert / fix that so upstream works with z10 again
> - Remove nodejs from s390x
> - Bump our baseline
> 
> See go and rustc for similar problems.

Bumping the baseline to z196 looks like the easiest way and as you said,
it would also fix go, rustc and maybe more software. However we discussed
raising the ISA to z10 about one year and a half ago, and the conclusion
was that we still have users with older machines. I'll try to restart
the discussion again.

Aurelien

-- 
Aurelien Jarno                          GPG: 4096R/1DDD8C9B
aurelien@aurel32.net                 http://www.aurel32.net