Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK4o1WxQsFn7euBa8gE=hDB0_MO64RUZdOvP3iy7oCjw6_eSGA@mail.gmail.com>
Date: Mon, 23 Jun 2014 22:09:29 +0100
From: Justin Cormack <justin@...cialbusservice.com>
To: musl@...ts.openwall.com
Subject: getcontext etc was Re: Re: go support (was: Best place to
 discuss other lightweight libraries?)

On Wed, Apr 24, 2013 at 2:42 PM, Rich Felker <dalias@...ifal.cx> wrote:
>> i tried to build gcc 4.7.2 with go support (--enable-languages=c,c++,go)
>> and that fails due to a lack of set/getcontext().
>> (see pkg/gcc472 in sabotage)
>>
>> according to rich, adding that to musl requires a non-trivial amount
>> of arch specific asm.
>
> Yes, but it is a wanted feature, so I wouldn't mind it getting done.
> It was even part of the standard prior to POSIX 2008, and the reason
> for removing it was stupid. (The reason was that the makecontext
> function's calling convention is bogus and impossible to support
> properly, but they could have fixed this by deprecating the use of the
> variadic arguments in any way except passing a single void* argument,
> rather than deprecating the whole set of interfaces.)

Just to revive this post 1.0, it would be very nice indeed to have
set,get,swapcontext.

Justin

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.