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] New: [5 Regression] Several libstdc++ test failures on darwin after r218964.
Date: Sat, 20 Dec 2014 15:33:00 -0000 [thread overview]
Message-ID: <bug-64368-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64368
Bug ID: 64368
Summary: [5 Regression] Several libstdc++ test failures on
darwin after r218964.
Product: gcc
Version: 5.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: dominiq at lps dot ens.fr
At r218988 I see the following failures on x86_64-apple-darwin14:
FAIL: 22_locale/locale/cons/6.cc execution test
FAIL: 22_locale/num_get/get/char/11.cc execution test
FAIL: 22_locale/num_get/get/char/12.cc execution test
FAIL: 22_locale/num_get/get/char/13.cc execution test
FAIL: 22_locale/num_get/get/char/14.cc execution test
FAIL: 22_locale/num_get/get/char/15.cc execution test
FAIL: 22_locale/num_get/get/char/22131.cc execution test
FAIL: 22_locale/num_get/get/char/23953.cc execution test
FAIL: 22_locale/num_get/get/char/37958.cc execution test
FAIL: 22_locale/num_get/get/char/39168.cc execution test
FAIL: 22_locale/num_get/get/wchar_t/11.cc execution test
FAIL: 22_locale/num_get/get/wchar_t/12.cc execution test
FAIL: 22_locale/num_get/get/wchar_t/13.cc execution test
FAIL: 22_locale/num_get/get/wchar_t/14.cc execution test
FAIL: 22_locale/num_get/get/wchar_t/15.cc execution test
FAIL: 22_locale/num_get/get/wchar_t/22131.cc execution test
FAIL: 22_locale/num_get/get/wchar_t/23953.cc execution test
FAIL: 22_locale/num_get/get/wchar_t/37958.cc execution test
FAIL: 22_locale/num_get/get/wchar_t/39168.cc execution test
FAIL: 22_locale/num_put/put/char/11.cc execution test
FAIL: 22_locale/num_put/put/char/23953.cc execution test
FAIL: 22_locale/num_put/put/char/38196.cc execution test
FAIL: 22_locale/num_put/put/wchar_t/11.cc execution test
FAIL: 22_locale/num_put/put/wchar_t/23953.cc execution test
FAIL: 22_locale/num_put/put/wchar_t/38196.cc execution test
FAIL: 22_locale/numpunct/members/char/cache_1.cc execution test
FAIL: 22_locale/numpunct/members/char/cache_2.cc execution test
FAIL: 22_locale/numpunct/members/wchar_t/cache_1.cc execution test
FAIL: 22_locale/numpunct/members/wchar_t/cache_2.cc execution test
FAIL: 27_io/basic_istream/extractors_arithmetic/char/07.cc execution test
FAIL: 27_io/basic_istream/extractors_arithmetic/char/08.cc execution test
FAIL: 27_io/basic_istream/extractors_arithmetic/wchar_t/07.cc execution test
FAIL: 27_io/basic_istream/extractors_arithmetic/wchar_t/08.cc execution test
FAIL: 27_io/basic_ostream/inserters_arithmetic/char/1.cc execution test
FAIL: 27_io/basic_ostream/inserters_arithmetic/wchar_t/1.cc execution test
FAIL: 27_io/manipulators/adjustfield/char/1.cc execution test
FAIL: 27_io/manipulators/adjustfield/wchar_t/1.cc execution test
FAIL: 27_io/manipulators/basefield/char/1.cc execution test
FAIL: 27_io/manipulators/basefield/wchar_t/1.cc execution test
FAIL: ext/profile/mutex_extensions_neg.cc (test for errors, line 306)
FAIL: ext/profile/mutex_extensions_neg.cc (test for excess errors)
They are of the kind
11.exe(53592,0x7fff76220300) malloc: *** error for object 0x10da37cbc: pointer
being freed was not allocated
but for ext/profile/mutex_extensions_neg.cc also seen on linux.
next reply other threads:[~2014-12-20 15:33 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-20 15:33 dominiq at lps dot ens.fr [this message]
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 ` [Bug target/64368] [5 Regression] Several libstdc++ test failures on non-linux platforms " dominiq at lps dot ens.fr
2015-01-21 16:32 ` 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@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).