On Wed, Jan 27, 2016 at 9:45 AM, Marek Polacek <pola...@redhat.com> wrote: > On Wed, Jan 27, 2016 at 10:02:36AM -0700, Jeff Law wrote: >> On 01/27/2016 12:26 AM, Marek Polacek wrote: >> >Ping. >> > >> >On Wed, Jan 20, 2016 at 12:31:51PM +0100, Marek Polacek wrote: >> >>On Wed, Jan 13, 2016 at 11:11:52PM +0000, Joseph Myers wrote: >> >>>The C front-end changes are OK. >> >> >> >>Jason, is the C++ part of this patch here >> >><https://gcc.gnu.org/ml/gcc-patches/2016-01/msg00866.html> >> >>(which is identical to the change in the C FE) ok? >> >> >> >>Also, not sure about backporting this, maybe just to 5? >> I'll go ahead and ack the C++ bits. This is fine for the trunk. > > Thanks. > >> WRT backporting, your call. > > I think I'll put it into GCC 5 (it's safe and should apply cleanly), > but leave 4.9 alone. > > Marek
I got FAIL: c-c++-common/vector-compare-4.c -Wc++-compat (test for warnings, line 17) FAIL: c-c++-common/vector-compare-4.c -Wc++-compat (test for warnings, line 18) FAIL: c-c++-common/vector-compare-4.c -Wc++-compat (test for warnings, line 34) FAIL: c-c++-common/vector-compare-4.c -Wc++-compat (test for warnings, line 35) on x86 on GCC 5 branch. -- H.J.
