This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: [RFC][AArch64] function prologue analyzer in linux kernel
- From: Andrew Pinski <pinskia at gmail dot com>
- To: Eric Botcazou <ebotcazou at adacore dot com>
- Cc: GCC Mailing List <gcc at gcc dot gnu dot org>, AKASHI Takahiro <takahiro dot akashi at linaro dot org>, Will Deacon <will dot deacon at arm dot com>, "Richard Earnshaw (lists)" <Richard dot Earnshaw at arm dot com>
- Date: Tue, 12 Jan 2016 00:22:41 -0800
- Subject: Re: [RFC][AArch64] function prologue analyzer in linux kernel
- Authentication-results: sourceware.org; auth=none
- References: <567BA582 dot 4060707 at linaro dot org> <56949911 dot 7000902 at linaro dot org> <CA+=Sn1k4sd9-pjxFBxQGO_dX+ABV7cG2amaxNCBDNG_y3C18RA at mail dot gmail dot com> <1513747 dot f6kUjzybvk at polaris>
On Tue, Jan 12, 2016 at 12:18 AM, Eric Botcazou <ebotcazou@adacore.com> wrote:
>> -fstack-usage does not work when there are VLAs or alloca's. So there
>> is no way to figure that part out without analysis of the actual
>> assembly code.
>
> No, -fstack-usage always works, i.e. its output can always be relied upon;
> when it cannot compute the maximum stack usage, it prints "unbounded".
Yes It works that way but that is not useful enough for what is needed
to do unwinding :).
>
> --
> Eric Botcazou