public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/64368] [5 Regression] Several libstdc++ test failures on darwin and others after r218964.
Date: Mon, 29 Dec 2014 12:56:00 -0000	[thread overview]
Message-ID: <bug-64368-4-Z9Z9O3oa8M@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

--- Comment #9 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Who is waving anything away? I've been fixing things for Darwin at all hours of
the day, while on vacation and while ill, so don't appreciate that comment.

I have run the years in valgrind and saw no problem on Linux.

Someone could always try debugging things themselves, even if just posting full
stack traces to this report.


  parent reply	other threads:[~2014-12-29 12:56 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 [this message]
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-Z9Z9O3oa8M@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).