From: Jason Merrill <jason@cygnus.com>
To: Joe Buck <jbuck@synopsys.com>
Cc: egcs@cygnus.com
Subject: Re: 970929 test results: libstdc++ test failures! (sparc-solaris251)
Date: Thu, 02 Oct 1997 11:08:00 -0000 [thread overview]
Message-ID: <u93emk11iv.fsf@yorick.cygnus.com> (raw)
In-Reply-To: <199710021746.KAA21629@atrus.synopsys.com>
>>>>> Joe Buck <jbuck@synopsys.com> writes:
> Jason writes:
>> Arrgh. This is a bug in the mangling code; that should be __F1Z, not
>> __g1Z. However, I don't understand why it's failing; it seems to be a
>> miscompilation of build_decl_overload_real. Does this patch fix
>> the problem?
> No, in fact, with this patch, *all* the libstdc++ tests fail to compile.
Arrgh again. That patch seems to work for other folks. Did you rebuild
all the library code, including libgcc? If so, could you possibly
investigate why that section of build_decl_overload_real is doing the wrong
thing? It seems like an awfully simple operation to me. I don't know why
it's breaking all of a sudden.
Jason
next prev parent reply other threads:[~1997-10-02 11:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199710012211.PAA28962.cygnus.egcs@atrus.synopsys.com>
1997-10-01 18:18 ` Jason Merrill
1997-10-02 1:59 ` Torbjorn Lindgren
1997-10-02 6:31 ` 970929 test results: libstdc++ test failures! Torbjorn Lindgren
1997-10-02 10:46 ` 970929 test results: libstdc++ test failures! (sparc-solaris251) Joe Buck
1997-10-02 11:08 ` Jason Merrill [this message]
1997-10-02 11:25 ` Joe Buck
1997-10-02 14:40 ` Joe Buck
1997-10-02 15:02 ` Joe Buck
1997-10-02 11:23 ` Chip Salzenberg
1997-10-02 13:23 ` H.J. Lu
1997-10-02 13:28 ` Chip Salzenberg
1997-10-02 13:30 ` H.J. Lu
1997-10-02 13:40 ` Joe Buck
1997-10-02 13:49 ` H.J. Lu
1997-10-01 15:11 Joe Buck
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=u93emk11iv.fsf@yorick.cygnus.com \
--to=jason@cygnus.com \
--cc=egcs@cygnus.com \
--cc=jbuck@synopsys.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).