This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH v2 1/3] posix: Remove dynamic memory allocation from execl{e,p}
- From: Adhemerval Zanella <adhemerval dot zanella at linaro dot org>
- To: Joseph Myers <joseph at codesourcery dot com>
- Cc: libc-alpha at sourceware dot org
- Date: Mon, 1 Feb 2016 16:09:18 -0200
- Subject: Re: [PATCH v2 1/3] posix: Remove dynamic memory allocation from execl{e,p}
- Authentication-results: sourceware.org; auth=none
- References: <1454343665-1706-1-git-send-email-adhemerval dot zanella at linaro dot org> <1454343665-1706-2-git-send-email-adhemerval dot zanella at linaro dot org> <alpine dot DEB dot 2 dot 10 dot 1602011648030 dot 2674 at digraph dot polyomino dot org dot uk> <56AF936C dot 6070907 at linaro dot org> <alpine dot DEB dot 2 dot 10 dot 1602011752310 dot 2674 at digraph dot polyomino dot org dot uk>
On 01-02-2016 15:53, Joseph Myers wrote:
> On Mon, 1 Feb 2016, Adhemerval Zanella wrote:
>
>> Right, it is not ensuring the safeness. Is '-fstack-check' the suffice
>> option to ensure it or do we need a more strict one?
>
> I think it's the right option, but don't know if it works reliably across
> supported architectures and GCC versions (or, at least, does not generate
> wrong code even if the checks aren't fully safe in all cases) - it's not
> very widely used.
>
I think we can use this option, since it supported on gcc (and I also do not
have any other better option in mind that fits in these function memory
constraints).