public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: paolo@gcc.gnu.org
To: David.Billinghurst@riotinto.com, gcc-bugs@gcc.gnu.org,
	gcc-prs@gcc.gnu.org, gdr@gcc.gnu.org
Subject: Re: c++/5294: Failure of test 26_numerics/binary_closure.cc on cygwin
Date: Fri, 18 Jan 2002 01:15:00 -0000	[thread overview]
Message-ID: <20020118091505.12681.qmail@sources.redhat.com> (raw)

Synopsis: Failure of test 26_numerics/binary_closure.cc on cygwin

State-Changed-From-To: analyzed->closed
State-Changed-By: paolo
State-Changed-When: Fri Jan 18 01:15:04 2002
State-Changed-Why:
    I'm closing this, since in the meanwhile we have learned
    that the C++ front-end is at fault: c++/5348 is the
    relevant PR, complete of short testcases for the C++ front
    end guys.
    I have added to PR5348 David.Billinghurst@riotinto.com
    
    Cheers,
    Paolo.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5294


                 reply	other threads:[~2002-01-18  9:15 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20020118091505.12681.qmail@sources.redhat.com \
    --to=paolo@gcc.gnu.org \
    --cc=David.Billinghurst@riotinto.com \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=gdr@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).