[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200620014447.GQ6430@brightrain.aerifal.cx>
Date: Fri, 19 Jun 2020 21:44:47 -0400
From: Rich Felker <dalias@...c.org>
To: Robert Skopalík <rs@...ome.cz>
Cc: "musl@...ts.openwall.com" <musl@...ts.openwall.com>,
Miroslav Němeček <mn@...ome.cz>
Subject: Re: strtok
On Sat, Jun 20, 2020 at 12:46:43AM +0000, Robert Skopalík wrote:
> I wouldn't like to bother you more than neccessary, but if you don't
> mind (as I hope :), I have one more question:
>
> Do we really need got table for a noMMU MCU? Fdpic uses it and I was
> looking for the answer what is it for pretty long - no success.
> Wouldn't it be enough just to keep the data segment offset in r9 and
> make all the data relative to it (in compiler)? That would get rid
> of the whole got table complexities. Bad idea? :)
That doesn't admit shared libraries, just multiple instances of the
same static-linked binary. It's not a supported ABI so you'd need to
hack up a toolchain and modified musl to do it.
On the other hand if you don't care about sharing text at all (might
be the case if yout text is expected to be very small anyway) you can
just use normal PIE binaries.
Rich
> -----Original Message-----
> From: Rich Felker [mailto:dalias@...c.org]
> Sent: Saturday, June 20, 2020 2:16 AM
> To: Robert Skopalík
> Cc: musl@...ts.openwall.com; Miroslav Němeček
> Subject: Re: [musl] strtok
>
> On Sat, Jun 20, 2020 at 12:03:12AM +0000, Robert Skopalík wrote:
> > Hello,
> >
> > we are working on an OS for a STM32 MCU. We like how the reentrancy
> > is solved in musl, but ... when two (or more) userspace programs
> > using a strtok function are run, there might be a collision (because
> > strtok uses a static var to save the pointer). We did not find any
> > redirection mechanism from strtok to strtok_r. How is it meant pls?
> > We do not want to force the users to write strtok_r into a
> > non-threaded user program.
> >
> > Is there some solution to make it work right?
> >
> > Thank you
>
> If multiple programs are running, each needs its own execution context
> including its own versions of all libc (and any other) global data.
> Probably you should look into the ARM FDPIC ABI, which is the right
> way to do this while still sharing program text for MMU-less
> microcontrollers like the one you're working with. The tooling should
> be mature now so that support could be added to musl, but making it
> happen needs people who are interested in providing feedback and
> testing.
>
> 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.
