Re: [PATCH] tools/nolibc: add support for Alpha

[Willy Tarreau <w@1wt.eu>]

On Tue, Jul 15, 2025 at 04:42:10PM +0200, Thomas Weißschuh wrote:
> > I finally managed to reinstall my DS10 to build and test this and FWIW
> > the test passes:
> 
> Thanks for getting real hardware involved!

You're welcome, I was happy to revive it after 15yr of downtime and
upgrade it from 2.4.37 to 6.12 ;-)

> > The result is exactly the same if I comment that line that resets brk,
> > as brk was apparently already NULL:
> > 
> >   13 sbrk_0 = <0x120024000>                                         [OK]
> >   14 sbrk = 0                                                       [OK]
> >   15 brk = 0                                                        [OK]
> 
> brk shouldn't be NULL I think. It looks instead like it's 0x120024000.
> And it looks weird because the raw numbers look similar to my machine.
> 
> >   1 argv_addr = <0x11fc7b428>                                       [OK]
> 
> >   13 sbrk_0 = <0x120024000>                                         [OK]
> 
> argv is not greater than brk.
> 
> Could you double-check your test modification?

I only commented out the "brk = NULL;" line enclosed in the
"#if defined(__alpha__)" block. But I can recheck everything. I
must say, the machine is old and super slow, I untarred a kernel
and applied the for-next patches then your alpha series on top
of it. Cloning via git would take a day or two based on my
experience with haproxy which is hundreds of times smaller...

> How does it behave in QEMU for you?

Not tested.

> Also could you provide your kernel config?

I could but for this I'll need to find a way to access it again. For an
unknown reason the console stopped responding yesterday, and now it only
speaks but I cannot enter anything. I suspect a voltage issue (same with
two adapters). Anyway it was the default config from the 6.12 debian 13
kernel apparently.

Will report back when I figure out this console issue (I'm still having
machines with real serial ports anyway).

Willy