From: Jason Merrill <jason@cygnus.com>
To: jbuck@synopsys.com (Joe Buck), egcs@cygnus.com
Subject: Re: 970929 test results: libstdc++ test failures! (sparc-solaris251)
Date: Wed, 01 Oct 1997 18:18:00 -0000 [thread overview]
Message-ID: <u9yb4d0xq0.fsf@yorick.cygnus.com> (raw)
In-Reply-To: <199710012211.PAA28962.cygnus.egcs@atrus.synopsys.com>
>>>>> Joe Buck <jbuck@synopsys.com> writes:
> sin__g1Zd_RCcomplex_complex /var/tmp/cca005N51.o
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?
Tue Sep 30 08:51:36 1997 Jason Merrill <jason@yorick.cygnus.com>
* method.c (build_decl_overload_real): Reformat.
Index: method.c
===================================================================
RCS file: /cvs/cvsfiles/devo/gcc/cp/method.c,v
retrieving revision 1.158
retrieving revision 1.159
diff -c -r1.158 -r1.159
*** method.c 1997/09/30 07:20:51 1.158
--- method.c 1997/09/30 15:54:09 1.159
***************
*** 1157,1164 ****
TREE_CHAIN (parms));
}
}
else
! OB_PUTC ((tparms != NULL_TREE) ? 'H' : 'F');
if (tparms)
{
--- 1157,1166 ----
TREE_CHAIN (parms));
}
}
+ else if (tparms)
+ OB_PUTC ('H');
else
! OB_PUTC ('F');
if (tparms)
{
next parent reply other threads:[~1997-10-01 18:18 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 [this message]
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
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=u9yb4d0xq0.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).