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: <9272.880943247@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".
And here's the appropriate magic to add to target.exp to filter out
those warnings too.
# When using the HP assembler, -g isn't supported.
regsub -all "(^|\n)(cc1: warning: -g is only supported when using GAS on this processor\[^\n\]*\ncc1: warning:\[^\n\]*\n?)+" $text "\\1" text
regsub -all "(^|\n)(cc1plus: warning: -g is only supported when using GAS on this processor\[^\n\]*\ncc1plus: warning:\[^\n\]*\n?)+" $text "\\1" text
However, to get accurate g++ results (or even a g++ compiler that
works) you're going to need to add -fexceptions to the command
line because of the dumb linker on hpux9 core dumping on having a
local label in a .word pseudo-op.
At this point I'm not sure what else can be done to make the hpux9
toolchain happy when using 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
1997-11-30 20:14 ` Jeffrey A Law [this message]
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=9272.880943247@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).