This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Porting libsanitizer to aarch64
- From: Richard Henderson <rth at redhat dot com>
- To: Jakub Jelinek <jakub at redhat dot com>
- Cc: Konstantin Serebryany <konstantin dot s dot serebryany at gmail dot com>, Christophe Lyon <christophe dot lyon at linaro dot org>, GCC Development <gcc at gcc dot gnu dot org>
- Date: Wed, 22 May 2013 13:19:05 -0700
- Subject: Re: Porting libsanitizer to aarch64
- References: <CAKdteOa-UDeo5zDwCeYSydu0K-WqmTjPgj3sYUpKrc0YPoncCg at mail dot gmail dot com> <20130521154426 dot GA1377 at tucnak dot redhat dot com> <CAGQ9bdyXCWDt0FF4+F5_4LbW7XcZACczKfHhr28nnwk96rf5Mw at mail dot gmail dot com> <20130522074341 dot GC1377 at tucnak dot redhat dot com>
On 05/22/2013 12:43 AM, Jakub Jelinek wrote:
> Changing frame grows upward into frame grows downward shouldn't be that
> hard, see e.g. rs6000 port, where
> #define FRAME_GROWS_DOWNWARD (flag_stack_protect != 0 || flag_asan != 0)
> and grep the port where it uses FRAME_GROWS_DOWNWARD.
> Basically you need to tweak initial elimination offset computation for it,
> and that might be it, or perhaps one or two extra spots.
FWIW, I would actually recommend against conditionalizing FRAME_GROWS_DOWNWARD
for a new port. Just make it _always_ grow down and save yourself the
additional code bloat in the backend.
r~