From: Martin Sebor <msebor@gmail.com>
To: Andreas Schwab <schwab@suse.de>
Cc: Jason Merrill <jason@redhat.com>,
Gcc Patch List <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] 69517 - [5/6 regression] SEGV on a VLA with excess initializer elements
Date: Thu, 14 Apr 2016 15:26:00 -0000 [thread overview]
Message-ID: <570FB693.5080806@gmail.com> (raw)
In-Reply-To: <mvmoa9cpj7k.fsf@hawking.suse.de>
On 04/14/2016 04:39 AM, Andreas Schwab wrote:
> Martin Sebor <msebor@gmail.com> writes:
>
>> diff --git a/gcc/testsuite/g++.dg/cpp1y/vla11.C b/gcc/testsuite/g++.dg/cpp1y/vla11.C
>> new file mode 100644
>> index 0000000..af9624a
>> --- /dev/null
>> +++ b/gcc/testsuite/g++.dg/cpp1y/vla11.C
>> @@ -0,0 +1,711 @@
>> +// PR c++/69517 - [5/6 regression] SEGV on a VLA with excess initializer
>> +// elements
>> +// PR c++/70019 - VLA size overflow not detected
>> +//
>> +// Runtime test to verify that attempting to either construct a VLA with
>> +// erroneous bounds, or initialize one with an initializer-list that
>> +// contains more elements than the VLA's non-constant (runtime) bounds
>> +// causes an exception to be thrown. Test also verifies that valid
>> +// VLAs and their initializers don't cause such an exception.
>> +
>> +// { dg-do run { target c++11 } }
>> +// { dg-additional-options "-Wno-vla" }
>
> On m68k:
>
> /daten/aranym/gcc/gcc-20160414/gcc/testsuite/g++.dg/cpp1y/vla11.C: In instantiation of 'struct TestType<32u>':
> /daten/aranym/gcc/gcc-20160414/gcc/testsuite/g++.dg/cpp1y/vla11.C:201:1: required from here
> /daten/aranym/gcc/gcc-20160414/gcc/testsuite/g++.dg/cpp1y/vla11.C:89:27: error: requested alignment 32 is larger than 16 [-Wattributes]
Thank you for the heads up (and sorry about the breakage). I've
committed r234976 to fix that.
Martin
next prev parent reply other threads:[~2016-04-14 15:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-07 1:38 Martin Sebor
2016-03-14 21:26 ` Martin Sebor
2016-03-21 22:10 ` PING #2 " Martin Sebor
2016-03-23 18:34 ` Jason Merrill
2016-03-23 22:50 ` Martin Sebor
2016-03-24 16:24 ` Jason Merrill
2016-04-01 23:02 ` Martin Sebor
2016-04-04 23:35 ` Jason Merrill
2016-04-08 0:05 ` Martin Sebor
2016-04-10 23:14 ` Martin Sebor
2016-04-12 15:43 ` Jason Merrill
2016-04-12 17:37 ` Martin Sebor
2016-04-12 18:17 ` Jason Merrill
2016-04-13 18:37 ` Martin Sebor
2016-04-13 19:26 ` Jason Merrill
2016-04-14 2:35 ` H.J. Lu
2016-04-14 15:32 ` Martin Sebor
2016-04-14 10:40 ` Andreas Schwab
2016-04-14 15:26 ` Martin Sebor [this message]
2016-04-15 7:11 ` Christophe Lyon
2016-04-15 12:31 ` Jakub Jelinek
2016-04-15 14:33 ` Martin Sebor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=570FB693.5080806@gmail.com \
--to=msebor@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.com \
--cc=schwab@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).