This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
| Other format: | [Raw text] | |
On 27 September 2016 at 03:21, Ville Voutilainen <ville.voutilainen@gmail.com> wrote: > On 27 September 2016 at 03:16, Christophe Lyon > <christophe.lyon@linaro.org> wrote: >> 20_util/declval/requirements/1_neg.cc (test for errors, line 2263) >> 20_util/declval/requirements/1_neg.cc (test for excess errors) >> 20_util/make_signed/requirements/typedefs_neg.cc (test for errors, line 1928) >> 20_util/make_signed/requirements/typedefs_neg.cc (test for excess errors) >> 20_util/make_unsigned/requirements/typedefs_neg.cc (test for >> errors, line 1781) >> 20_util/make_unsigned/requirements/typedefs_neg.cc (test for >> errors, line 1824) >> 20_util/make_unsigned/requirements/typedefs_neg.cc (test for excess errors) >> >> Error messages include: >> /aci-gcc-fsf/builds/gcc-fsf-gccsrc/obj-aarch64-none-linux-gnu/gcc3/aarch64-none-linux-gnu/libstdc++-v3/include/type_traits:2270: >> error: static assertion failed: declval() must not be used! >> >> Is it just because the pattern in dg-error is *-*-* ? > > > Argh, I'll take a look. These errors come from the testsuite expecting > certain line numbers in certain > library headers, and adding code to said headers shifts the error lines. I have committed the attached patch as obvious. Pardons all around for failing to run the full suite properly.
Attachment:
fix-lwg2729-backport-testsuite-failures.diff
Description: Text document
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |