public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dougkwan at google dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/33700] FAIL: 17_intro/headers/all_pedantic_errors.cc (test for excess errors)
Date: Mon, 08 Oct 2007 19:50:00 -0000	[thread overview]
Message-ID: <20071008195035.26394.qmail@sourceware.org> (raw)
In-Reply-To: <bug-33700-276@http.gcc.gnu.org/bugzilla/>



------- Comment #3 from dougkwan at google dot com  2007-10-08 19:50 -------
Subject: Re:  FAIL: 17_intro/headers/all_pedantic_errors.cc (test for excess
errors)

That's strange. I am looking at it. I ran the libstdc++ testsuite
before and did not see this problem.

-Doug

8 Oct 2007 19:32:42 -0000, dave at hiauly1 dot hia dot nrc dot ca
<gcc-bugzilla@gcc.gnu.org>:
>
>
> ------- Comment #2 from dave at hiauly1 dot hia dot nrc dot ca  2007-10-08 19:32 -------
> Subject: Re:  FAIL: 17_intro/headers/all_pedantic_errors.cc (test for excess
> errors)
>
> > ------- Comment #1 from pcarlini at suse dot de  2007-10-08 18:57 -------
> > So the problem is new, right? Has it to do with the recent fixes for the
> > deadlock bug?
>
> Looking at the testresults, it appears to have been introduced between
> 128587 and 128594 in September.  The only patch of significance in this
> period is Jason's 128590.  It's not obvious to me why this would have
> affected the behavior of -pedantic.
>
> Dave
>
>
> --
>
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33700
>
> ------- You are receiving this mail because: -------
> You are on the CC list for the bug, or are watching someone who is.
>


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33700


  parent reply	other threads:[~2007-10-08 19:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-08 18:16 [Bug libstdc++/33700] New: " danglin at gcc dot gnu dot org
2007-10-08 18:57 ` [Bug libstdc++/33700] " pcarlini at suse dot de
2007-10-08 19:32 ` dave at hiauly1 dot hia dot nrc dot ca
2007-10-08 19:50 ` dougkwan at google dot com [this message]
2007-10-08 20:11 ` dave at hiauly1 dot hia dot nrc dot ca
2007-10-08 22:35 ` dougkwan at google dot com
2007-10-08 23:01 ` dave at hiauly1 dot hia dot nrc dot ca
2007-10-08 23:35 ` pcarlini at suse dot de
2007-10-11  1:26 ` dave at hiauly1 dot hia dot nrc dot ca
2007-10-11 23:50 ` [Bug target/33700] " danglin at gcc dot gnu dot org
2007-10-14 22:22 ` danglin at gcc dot gnu dot org
2007-10-14 22:25 ` danglin at gcc dot gnu dot org

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=20071008195035.26394.qmail@sourceware.org \
    --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).