Re: [RFC PATCH 00/23] aarch64-gnu port

[Sergey Bugaev <bugaevc@gmail.com>]

On Mon, Mar 11, 2024 at 4:48 PM H.J. Lu <hjl.tools@gmail.com> wrote:
> I think hurd maintainers can approve and check in all hurd specific
> changes now even if they won't build.   The generic changes should
> be looked at more closely so that they have no impacts on any
> future Linux changes and future Linux changes won't be blocked
> because of hurd.

On Mon, Mar 11, 2024 at 5:15 PM Maxim Kuvyrkov
<maxim.kuvyrkov@linaro.org> wrote:
> Hi Sergey,
>
> Would you please update and re-post your patch series, so that reviewers can check that it doesn't break existing targets?

Hi Maxim, H.J.,

"Even if they won't build" won't stay that way for long: since the
time I posted this glibc patchset, I've been working on porting GNU
Mach to AArch64, and while that work is not yet upstream, my branch of
gnumach compiles, boots in QEMU, and passes the testsuite! (And I am
*so* excited about this!) Moreover, the simple glibc-based program
that I've used for testing in GDB (as mentioned in the cover letter)
starts up and reaches main() too! I have not rebuilt it since then,
meaning that ABI indeed matches between the kernel and this glibc
patchset.

So yes, it might be the time for me to rebase & update this patchset,
and post it again. I'll start working on that then.

By the way, while I have a somewhat better understanding of AArch64 &
ARM-based systems now, I'd still appreciate any reviews / insights /
pointers.

Sergey