public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/64368] [5 Regression] Several libstdc++ test failures on non-linux platforms after r218964.
Date: Wed, 21 Jan 2015 15:03:00 -0000 [thread overview]
Message-ID: <bug-64368-4-utYyxLHweR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64368-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64368
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[5 Regression] Several |[5 Regression] Several
|libstdc++ test failures on |libstdc++ test failures on
|darwin and others after |non-linux platforms after
|r218964. |r218964.
--- Comment #15 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> I've just confirmed that r218964 is also the cuprit for the
> (considerably smaller) set of 64-bit testsuite failures seen
> on Solaris (both SPARC and x86):
Some are also seen on hppa2.0w-hp-hpux11.11, see
https://gcc.gnu.org/ml/gcc-testresults/2015-01/msg02304.html:
FAIL: 22_locale/conversions/string/2.cc execution test
FAIL: 23_containers/unordered_map/requirements/explicit_instantiation/2.cc
(test for excess errors)
FAIL: 23_containers/unordered_map/requirements/explicit_instantiation/4.cc
(test for excess errors)
FAIL: 23_containers/vector/ext_pointer/types/2.cc execution test
FAIL: 30_threads/shared_lock/requirements/explicit_instantiation.cc (test for
excess errors)
FAIL: 30_threads/shared_lock/requirements/typedefs.cc (test for excess errors)
FAIL: 30_threads/shared_timed_mutex/requirements/standard_layout.cc (test for
excess errors)
FAIL: experimental/feat-cxx14.cc (test for excess errors)
Note that the last failures belong to another PR: they come from a later commit
and I see several of them on darwin (see FX tests). I have no inclination to
open a PR for them as long as the PRs I open are rotting for ever.
next prev parent reply other threads:[~2015-01-21 15:03 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-20 15:33 [Bug target/64368] New: [5 Regression] Several libstdc++ test failures on darwin " dominiq at lps dot ens.fr
2014-12-20 15:37 ` [Bug target/64368] " dominiq at lps dot ens.fr
2014-12-20 15:39 ` dominiq at lps dot ens.fr
2014-12-20 15:47 ` fxcoudert at gcc dot gnu.org
2014-12-20 16:00 ` dominiq at lps dot ens.fr
2014-12-20 17:39 ` howarth at bromo dot med.uc.edu
2014-12-29 2:23 ` hp at gcc dot gnu.org
2014-12-29 2:51 ` [Bug target/64368] [5 Regression] Several libstdc++ test failures on darwin and others " hp at gcc dot gnu.org
2014-12-29 12:56 ` redi at gcc dot gnu.org
2014-12-29 14:15 ` hp at gcc dot gnu.org
2014-12-29 14:48 ` hp at gcc dot gnu.org
2015-01-09 11:20 ` rguenth at gcc dot gnu.org
2015-01-12 7:26 ` izamyatin at gmail dot com
2015-01-21 11:13 ` ro at gcc dot gnu.org
2015-01-21 15:03 ` dominiq at lps dot ens.fr [this message]
2015-01-21 16:32 ` [Bug target/64368] [5 Regression] Several libstdc++ test failures on non-linux platforms " redi at gcc dot gnu.org
2015-01-24 20:38 ` howarth at bromo dot med.uc.edu
2015-01-26 12:33 ` redi at gcc dot gnu.org
2015-01-26 23:43 ` redi at gcc dot gnu.org
2015-01-26 23:44 ` redi at gcc dot gnu.org
2015-01-27 5:06 ` howarth at bromo dot med.uc.edu
2015-01-27 11:05 ` dominiq at lps dot ens.fr
2015-01-27 11:13 ` redi at gcc dot gnu.org
2015-01-27 12:23 ` dominiq at lps dot ens.fr
2015-01-27 13:13 ` redi at gcc dot gnu.org
2015-01-27 14:54 ` hp at gcc dot gnu.org
2015-01-27 21:11 ` andreast at gcc dot gnu.org
2015-01-28 0:48 ` redi at gcc dot gnu.org
2015-01-28 3:32 ` howarth at bromo dot med.uc.edu
2015-01-28 9:46 ` ro at CeBiTec dot Uni-Bielefeld.DE
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=bug-64368-4-utYyxLHweR@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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).