This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] Add gcc.dg/stack-check-16.c
- From: Jeff Law <law at redhat dot com>
- To: Jakub Jelinek <jakub at redhat dot com>
- Cc: gcc-patches at gcc dot gnu dot org
- Date: Fri, 19 Jan 2018 11:08:09 -0700
- Subject: Re: [PATCH] Add gcc.dg/stack-check-16.c
- Authentication-results: sourceware.org; auth=none
- References: <20180119112204.GT2063@tucnak>
On 01/19/2018 04:22 AM, Jakub Jelinek wrote:
> Hi!
>
> This patch adds a new testcases, not exactly sure what is the exact
> origin and what was the problem. The changes I've done are:
> 1) macroize, so that the test is just a few lines rather than 160KB,
> verified -fdump-tree-gimple printf call is identical between this
> and the original test
> 2) remove optimize(0) attribute, the test is compiled with -O0
> 3) use __builtin_alloca instead of alloca and add mtrace prototype,
> remove -w because no warnings are emitted any longer
>
> The test passes at least on x86_64-linux with -m32/-m64. Ok for trunk?
>
> 2018-01-19 Jeff Law <law@redhat.com>
> Jakub Jelinek <jakub@redhat.com>
>
> * gcc.dg/stack-check-16.c: New test.
OK.
I've been wandering my mailboxes to find the discussion which led to
this test, but can't seem to find it. Based on the structure of the
test I'm pretty sure it is related to a large outgoing argument area.
THe fact that it wasn't submitted upstream, but was in the aarch64
bundle means it was probably related to the need to probe the outgoing
argument area which is specific to aarch64.
Without any scanning of dump files or assembly output it must have been
an ICE in that code. The thing that worries me is I can't recall fixing
such an ICE!
But again, OK for the trunk.
Jeff