This is the mail archive of the
mailing list for the GCC project.
Re: SafeStack proposal in GCC
- From: Joel Sherrill <joel dot sherrill at oarcorp dot com>
- To: Ian Lance Taylor <iant at google dot com>, Rich Felker <dalias at libc dot org>
- Cc: Volodymyr Kuznetsov <vova dot kuznetsov at epfl dot ch>, "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- Date: Mon, 9 May 2016 14:41:47 -0500
- Subject: Re: SafeStack proposal in GCC
- Authentication-results: sourceware.org; auth=none
- References: <CAFA9rWPkb=eV0GhvFeOnd4pRVh=N3fSifYBwZjy9Ndh68BmBww at mail dot gmail dot com> <0d50f0ef01b24c25a79a6f18eaddfd6d at REXA dot intranet dot epfl dot ch> <CANL6WeqEwFYx2H-sv81K8CDFypiJ+ray+xPyRH+7kitTpD8bqw at mail dot gmail dot com> <20160507054212 dot GE21636 at brightrain dot aerifal dot cx> <CAKOQZ8zYdRgjsg0D5oVfXkkadzkyybKZn3nnG8RBs5hLNq7Neg at mail dot gmail dot com>
On 5/9/2016 2:25 PM, Ian Lance Taylor wrote:
On Fri, May 6, 2016 at 10:42 PM, Rich Felker <email@example.com> wrote:
The *context APIs are deprecated and I'm not sure they're worth
supporting with this. It would be a good excuse to get people to stop
The gccgo library uses them, because there is no working alternative.
FWIW when this transition occurred, that's when the RTEMS port broke.
We don't have these methods.
It would be an interesting exercise to see if they could be
implemented in terms of our internal thread context management
APIs but no one has ever looked into it deeply.
In general coroutine support requires the ability to designate some
area of memory as stack space.