From: Jeffrey A Law <law@cygnus.com>
To: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
Cc: egcs@cygnus.com
Subject: Re: egcs-971127 hppa1.1-hp-hpux9.01 results
Date: Sun, 30 Nov 1997 20:14:00 -0000 [thread overview]
Message-ID: <9074.880938744@hurl.cygnus.com> (raw)
In-Reply-To: <199711291709.MAA28369@caip.rutgers.edu>
In message < 199711291709.MAA28369@caip.rutgers.edu >you write:
> PS: I think at least some (many?) of the "make check" errors for
> libio, libstdc++ and g++ are due to the testsuite passing -g and
> getting a warning "cc1plus: warning: -g is only supported when using
> GAS on this processor".
Probably. I'll see what I can do.
> Also some of the errors reported for gcc may
> be due to a warning from the hpux9 assembler which is considered
> harmless by the gcc documentation: "Use of GR3 when frame>=8192 may
> cause conflict".
Yes, this causes some grief for dejagnu. Adding this to prune_warnings
in target.exp should fix this problem.
# This happens when assembling code with the native HP assembler
regsub -all "(^|\n)(as:\[^\n\]*err#13.\n .warning.\[^\n\]*\n?)+" $text "\\1" text
> Many other errors resulted from ld terminating with signal 11.
> I can send the detailed log files to anyone who is interested.
Yes, this is happening in the tests which test computed gotos and
such -- we've traded an assembly time error for a link error when using
label values and computed gotos in an attempt to keep C++ working
with the HP assembler.
jeff
next prev parent reply other threads:[~1997-11-30 20:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-11-29 13:40 Kaveh R. Ghazi
1997-11-30 20:14 ` Jeffrey A Law [this message]
1997-11-30 20:14 ` Jeffrey A Law
1997-12-01 19:30 Kaveh R. Ghazi
1997-12-02 8:02 ` Jeffrey A Law
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=9074.880938744@hurl.cygnus.com \
--to=law@cygnus.com \
--cc=egcs@cygnus.com \
--cc=ghazi@caip.rutgers.edu \
/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).