Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID:
 <VI1PR10MB35660283A924A8549685238DCF990@VI1PR10MB3566.EURPRD10.PROD.OUTLOOK.COM>
Date: Sat, 20 Jun 2020 13:00:54 +0000
From: Robert SkopalĂ­k <rs@...ome.cz>
To: "musl@...ts.openwall.com" <musl@...ts.openwall.com>
Subject: RE: strtok

Me tooo :)))

-----Original Message-----
From: Patrick Oppenlander [mailto:patrick.oppenlander@...il.com] 
Sent: Saturday, June 20, 2020 9:07 AM
To: musl@...ts.openwall.com
Subject: Re: [musl] strtok

On Sat, Jun 20, 2020 at 10:15 AM Rich Felker <dalias@...c.org> wrote:
>
> 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.
>

I'm very interested and will definitely be able to provide feedback & testing.

Apex (apexrtos.com) is waiting for musl FDPIC support so that I can
work on the kernel side. This is the RTOS with the Linux syscall
interface I think I might have mentioned some time ago.

Patrick

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.