public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: David.Billinghurst@riotinto.com
To: gcc-gnats@gcc.gnu.org
Cc: jason@redhat.com
Subject: c++/6072: 3.2 g++ testsuite breakage on cygwin
Date: Wed, 27 Mar 2002 13:06:00 -0000 [thread overview]
Message-ID: <20020327210254.31666.qmail@sources.redhat.com> (raw)
>Number: 6072
>Category: c++
>Synopsis: 3.2 g++ testsuite breakage on cygwin
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Wed Mar 27 13:06:01 PST 2002
>Closed-Date:
>Last-Modified:
>Originator: David Billinghurst
>Release: 3.2
>Organization:
>Environment:
i686-pc-cygwin
>Description:
The following patch to trunk on 2002-03-15 between 18:32
UTC and 19:00 UTC, broke a number of tests on cygwin.
See gcc-bugs mailing list around 20 March for limited
discussion
2002-03-15 Jason Merrill <jason@redhat.com>
* varasm.c (assemble_variable): Call resolve_unique_section before
checking DECL_SECTION_NAME. Use zeros for a decl with DECL_INITIAL
of error_mark_node.
Additional FAILS are
FAIL: g++.dg/eh/omit-frame-pointer.C execution test
FAIL: g++.dg/template/conv3.C (test for excess errors)
WARNING: g++.dg/template/conv3.C compilation failed to produce executable
FAIL: g++.dg/template/qualttp20.C (test for excess errors)
FAIL: g++.dg/template/qualttp3.C (test for excess errors)
FAIL: g++.dg/template/qualttp4.C (test for excess errors)
FAIL: g++.dg/template/qualttp5.C (test for excess errors)
FAIL: g++.dg/template/qualttp6.C (test for excess errors)
FAIL: g++.dg/template/qualttp7.C (test for excess errors)
FAIL: g++.dg/template/qualttp8.C (test for excess errors)
FAIL: g++.dg/template/recurse.C (test for excess errors)
FAIL: g++.benjamin/15071.C Execution test
FAIL: g++.brendan/copy9.C Execution test
FAIL: g++.brendan/nest21.C Execution test
FAIL: g++.brendan/ptolemy2.C Execution test
FAIL: g++.jason/2371.C Execution test
FAIL: g++.jason/template24.C Execution test
FAIL: g++.jason/template31.C Execution test
FAIL: g++.jason/typeid1.C Execution test
FAIL: g++.law/arg8.C Execution test
FAIL: g++.law/code-gen5.C Execution test
FAIL: g++.law/ctors12.C Execution test
FAIL: g++.law/cvt2.C Execution test
FAIL: g++.law/virtual3.C Execution test
FAIL: g++.mike/eh2.C Execution test
FAIL: g++.mike/net34.C Execution test
FAIL: g++.mike/net46.C Execution test
FAIL: g++.mike/p658.C Execution test
FAIL: g++.other/headers1.C Execution test
FAIL: g++.other/sibcall1.C Execution test
FAIL: g++.other/unchanging1.C Execution test
FAIL: g++.pt/ttp19.C Execution test
FAIL: g++.robertl/eb115.C Execution test
FAIL: g++.robertl/eb118.C Execution test
FAIL: g++.robertl/eb21.C Execution test
FAIL: g++.robertl/eb27.C Execution test
FAIL: g++.robertl/eb31.C Execution test
FAIL: g++.robertl/eb41.C Execution test
FAIL: g++.robertl/eb46.C Execution test
FAIL: g++.robertl/eb54.C Execution test
FAIL: g++.robertl/eb66.C Execution test
FAIL: g++.robertl/eb73.C Execution test
FAIL: g++.robertl/eb77.C Execution test
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2002-03-27 21:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-27 13:06 David.Billinghurst [this message]
2002-04-12 7:24 billingd
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=20020327210254.31666.qmail@sources.redhat.com \
--to=david.billinghurst@riotinto.com \
--cc=gcc-gnats@gcc.gnu.org \
--cc=jason@redhat.com \
/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).