This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ 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]

Re: New AIX testsuite failures

From: Jonathan Wakely <jwakely at redhat dot com>
To: Ville Voutilainen <ville dot voutilainen at gmail dot com>
Cc: David Edelsohn <dje dot gcc at gmail dot com>, libstdc++ <libstdc++ at gcc dot gnu dot org>
Date: Thu, 14 Jun 2018 19:23:18 +0100
Subject: Re: New AIX testsuite failures
References: <CAGWvny=mD2XBQ_S8DTtBu=ntn-qOADLq1id=gsXRk4S17yT9wA@mail.gmail.com> <CAFk2RUabnkbKdSNfZPwyNxjUcH4P+4TwRRg3anYL=9Kb4Mva-w@mail.gmail.com>

On 14/06/18 21:02 +0300, Ville Voutilainen wrote:

On 14 June 2018 at 20:57, David Edelsohn <dje.gcc@gmail.com> wrote:

I'm still seeing two, new failures in the libstdc++ testsuite on AIX:

23_containers/array/tuple_interface/tuple_element_cpp14.cc
20_util/pair/astuple/astuple_cpp14.cc

Both additional errors are similar.  Appended below.

Any idea what's wrong?


I would wager that since <array> doesn't #include <tuple>, moving
tuple_element_t with the feature macro
borked it. :)


Right. No idea why I didn't see that failure though.

I'll fix it.

Follow-Ups:
- Re: New AIX testsuite failures
  - From: Jonathan Wakely

References:
- New AIX testsuite failures
  - From: David Edelsohn
- Re: New AIX testsuite failures
  - From: Ville Voutilainen

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]