On 01/27/2017 05:01 PM, Jeff Law wrote:
On 01/27/2017 02:28 PM, Martin Sebor wrote:
On 01/27/2017 11:20 AM, Jason Merrill wrote:
On Fri, Jan 27, 2017 at 11:56 AM, Martin Sebor wrote:
FWIW, I could avoid this awkward setup if I had just one repo for all
my changes, shared across my various mac
On 01/27/2017 02:28 PM, Martin Sebor wrote:
On 01/27/2017 11:20 AM, Jason Merrill wrote:
On Fri, Jan 27, 2017 at 11:56 AM, Martin Sebor wrote:
FWIW, I could avoid this awkward setup if I had just one repo for all
my changes, shared across my various machines. Unfortunately, for it
to really w
On 01/27/2017 11:20 AM, Jason Merrill wrote:
On Fri, Jan 27, 2017 at 11:56 AM, Martin Sebor wrote:
FWIW, I could avoid this awkward setup if I had just one repo for all
my changes, shared across my various machines. Unfortunately, for it
to really work I would also need to be able to commit us
On 01/27/2017 11:20 AM, Jason Merrill wrote:
On Fri, Jan 27, 2017 at 11:56 AM, Martin Sebor wrote:
FWIW, I could avoid this awkward setup if I had just one repo for all
my changes, shared across my various machines. Unfortunately, for it
to really work I would also need to be able to commit us
On Fri, Jan 27, 2017 at 11:56 AM, Martin Sebor wrote:
> FWIW, I could avoid this awkward setup if I had just one repo for all
> my changes, shared across my various machines. Unfortunately, for it
> to really work I would also need to be able to commit using Git rather
> than Subversion which doe
On Jan 27 2017, Martin Sebor wrote:
> FWIW, I could avoid this awkward setup if I had just one repo for all
> my changes, shared across my various machines. Unfortunately, for it
> to really work I would also need to be able to commit using Git rather
> than Subversion which doesn't work. At le
On 01/27/2017 02:45 AM, Rainer Orth wrote:
Martin Sebor writes:
The improvements to the handling of flexible array members in
C++ in GCC 6 inadvertently removed the pedantic warnings GCC
used to issue for their declarations. The attached patch
restores it.
After this patch, I get
FAIL: obj
Martin Sebor writes:
> The improvements to the handling of flexible array members in
> C++ in GCC 6 inadvertently removed the pedantic warnings GCC
> used to issue for their declarations. The attached patch
> restores it.
After this patch, I get
FAIL: obj-c++.dg/property/at-property-23.mm -fgn
On 01/25/2017 04:53 PM, Jakub Jelinek wrote:
On Wed, Jan 25, 2017 at 10:02:23AM -0700, Martin Sebor wrote:
--- gcc/cp/decl.c (revision 244844)
+++ gcc/cp/decl.c (working copy)
@@ -11798,6 +11798,17 @@ grokdeclarator (const cp_declarator *declarator,
}
else
On Wed, Jan 25, 2017 at 10:02:23AM -0700, Martin Sebor wrote:
> --- gcc/cp/decl.c (revision 244844)
> +++ gcc/cp/decl.c (working copy)
> @@ -11798,6 +11798,17 @@ grokdeclarator (const cp_declarator *declarator,
> }
> else
> {
> + /* Array is a
OK.
On Wed, Jan 25, 2017 at 12:02 PM, Martin Sebor wrote:
> The improvements to the handling of flexible array members in
> C++ in GCC 6 inadvertently removed the pedantic warnings GCC
> used to issue for their declarations. The attached patch
> restores it.
>
> Martin
The improvements to the handling of flexible array members in
C++ in GCC 6 inadvertently removed the pedantic warnings GCC
used to issue for their declarations. The attached patch
restores it.
Martin
PR c++/71290 - [6/7 Regression] Flexible array member is not diagnosed with -pedantic
gcc/cp/Ch
12 matches
Mail list logo
