On Fri, May 19, 2023 at 2:06 PM Maciej W. Rozycki <ma...@orcam.me.uk> wrote: > > On Sat, 29 Apr 2023, Jeff Law via Gcc-patches wrote: > > > > PR target/105525 is a build regression for the vax and lm32 linux > > > targets present in gcc-12/13/head, where the builds fail due to > > > unsatisfied references to __INTPTR_TYPE__ and __UINTPTR_TYPE__, > > > caused by these two targets failing to provide glibc-stdint.h. > > > > > > Fixed thusly, tested by building crosses, which now succeeds. > > > > > > Ok for trunk? (Note I don't have commit rights.) > > > > > > 2023-04-28 Mikael Pettersson<mikpeli...@gmail.com> > > > > > > PR target/105525 > > > * config.gcc (vax-*-linux*): Add glibc-stdint.h. > > > (lm32-*-uclinux*): Likewise. > > Thanks. I've pushed this to the trunk. > > Hmm, I find it quite insteresting and indeed encouraging that someone > actually verifies our VAX/Linux target. > > Mikael, how do you actually verify it however?
My vax builds are only cross-compilers without kernel headers or libc. The background is that I maintain a script to build GCC-based crosses to as many targets as I can, currently it supports 78 distinct processors and 82 triplets (four processors have multiple triplets). I only check that I can build the toolchains (full linux-gnu ones where possible). /Mikael > I'm asking because while I did a glibc port for VAX/Linux (including VAX > floating-point format support), it was many years ago and for LinuxThreads > configuration only (hence glibc 2.4 only), which I suspect may not be > supported by GCC anymore. And it has never made its way upstream, because > we'd have to land Linux kernel bits there first and that effort has > stalled. > > I can still boot that old stuff on my VAX machine, but the userland is > minimal and somewhat unstable as things sometimes crash or otherwise > behave in a weird way. I do have working `bash' and more importantly > `gdbserver' binaries though. > > Maciej
