Why are there multiple ucontext.h headers for the same architeture?

[Neven Sajko]

I still do not understand this: when would sysdeps/arm/sys/ucontext.h
be used/installed instead of
sysdeps/unix/sysv/linux/arm/sys/ucontext.h?

Or, more generally, these seem to be all the ucontext.h headers in glibc:

sysdeps/unix/sysv/linux/x86/sys/ucontext.h
sysdeps/unix/sysv/linux/sparc/sys/ucontext.h
sysdeps/unix/sysv/linux/sh/sys/ucontext.h
sysdeps/unix/sysv/linux/s390/sys/ucontext.h
sysdeps/unix/sysv/linux/riscv/sys/ucontext.h
sysdeps/unix/sysv/linux/powerpc/sys/ucontext.h
sysdeps/unix/sysv/linux/nios2/sys/ucontext.h
sysdeps/unix/sysv/linux/mips/sys/ucontext.h
sysdeps/unix/sysv/linux/microblaze/sys/ucontext.h
sysdeps/unix/sysv/linux/m68k/sys/ucontext.h
sysdeps/unix/sysv/linux/ia64/sys/ucontext.h
sysdeps/unix/sysv/linux/hppa/sys/ucontext.h
sysdeps/unix/sysv/linux/csky/sys/ucontext.h
sysdeps/unix/sysv/linux/arm/sys/ucontext.h
sysdeps/unix/sysv/linux/alpha/sys/ucontext.h
sysdeps/unix/sysv/linux/aarch64/sys/ucontext.h
sysdeps/mips/sys/ucontext.h
sysdeps/m68k/sys/ucontext.h
sysdeps/i386/sys/ucontext.h
sysdeps/generic/sys/ucontext.h
sysdeps/arm/sys/ucontext.h
stdlib/ucontext.h
include/ucontext.h

So the same question I asked for ARM could also be asked for i386,
m68k, or mips.

Thanks,
Neven