[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20150316002543.GV23507@brightrain.aerifal.cx>
Date: Sun, 15 Mar 2015 20:25:43 -0400
From: Rich Felker <dalias@...c.org>
To: musl@...ts.openwall.com
Subject: Re: ideas for build system changes, bits refactoring
On Sun, Mar 15, 2015 at 06:47:56PM -0500, Bobby Bingham wrote:
> > 2. Factor arch bits (types, struct layouts, constant values, etc.) as
> > a sequence of overlays: a generic base, several common families like
> > 32-bit, 64-bit, 64-bit+ILP32, ld-64, ld-80, ld-128, and finally
> > arch-specific bits. The latter should be nearly empty for most archs.
>
> Do you mean that a final bits header would come from one of these
> overlays that hadn't been overridden by another overlay, or would be a
> composite built from pieces provided by the different overlays?
>
> For example, powerpc/bits/errno.h is nearly identical to the file used
> on most other architectures, just with a different value of EDEADLOCK.
> Would the powerpc arch-specific errno.h need to redefine all of the
> values, or would it be able to inherit most of the values from the
> generic base and just override EDEADLOCK?
I don't have a plan in mind for this yet. Obviously there are
simplifying/deduplication benefits to being able to make small
replacements like this, but in order to make sense there needs to be a
net savings still even after we implement whatever part of the build
script would be responsible for merging them. I'm not sure how that
would work.
This could of course be done in multiple phases, where the first phase
is just cp'ing the 'best match' overlay and we later add fancier
merging.
> 5. This may be orthogonal to the rest of these ideas, but what about
> providing thin wrappers for the syscalls used by musl itself, similar to
> the __sys_open* macros already provided by internal/syscall.h? I think
> it would help for bare metal targets to be able to implement one
> individual function per syscall, rather than needing to implement a
> whole syscall dispatcher.
Yes. I'd still like to explore what changes users wanting to do
bare-metal stuff with musl would like to see. I agree it's sort of
orthogonal to the above.
Rich
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
