public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
To: law@cygnus.com
Cc: egcs@cygnus.com
Subject: Re: egcs-971127 hppa1.1-hp-hpux9.01 results
Date: Mon, 01 Dec 1997 19:30:00 -0000	[thread overview]
Message-ID: <199712020210.VAA09712@caip.rutgers.edu> (raw)

 > From: Jeffrey A Law <law@hurl.cygnus.com>
 > 
 > 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
 > 
 > 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


	Okay, I got these inserted and they work fine.  Thanks!  Will
they be appearing in the next dejagnu snapshot?



 > 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.


	You mean -fno-exceptions, right?



 > At this point I'm not sure what else can be done to make the hpux9
 > toolchain happy when using the HP assembler.
 > jeff


	Well, what we have is not too bad.  After applying the two
patches to target.exp, I get somewhat better results.  Ie, dejagnu
marks over 100 more tests as passing, see below.

	Most of the remaining errors are from "ld" core dumping.
However a few are cc1 internal compiler errors.  I think we may see
some benefit in fixing these.

		--Kaveh

xgcc: Internal compiler error: program cc1 got fatal signal 6
FAIL: gcc.c-torture/execute/920428-2.c compilation,  -O1
xgcc: Internal compiler error: program cc1 got fatal signal 6
FAIL: gcc.c-torture/execute/920428-2.c compilation,  -O2
xgcc: Internal compiler error: program cc1 got fatal signal 6
FAIL: gcc.c-torture/execute/920428-2.c compilation,  -O2 -fomit-frame-pointer -finline-functions

xgcc: Internal compiler error: program cc1 got fatal signal 6
FAIL: gcc.c-torture/execute/920501-5.c compilation,  -O2 -fomit-frame-pointer -finline-functions

xgcc: Internal compiler error: program cc1 got fatal signal 6
FAIL: gcc.c-torture/execute/920501-7.c compilation,  -O1
xgcc: Internal compiler error: program cc1 got fatal signal 6
FAIL: gcc.c-torture/execute/920501-7.c compilation,  -O2
xgcc: Internal compiler error: program cc1 got fatal signal 6
FAIL: gcc.c-torture/execute/920501-7.c compilation,  -O2 -fomit-frame-pointer -finline-functions

----------------------------------------------------------------------------
egcs-971127 plain:
                === libio Summary ===
# of unexpected failures        14
# of expected failures          26
                === libstdc++ Summary ===
# of unexpected failures        10
# of expected failures          20
                === gcc Summary ===
# of expected passes            4765
# of unexpected failures        84
# of expected failures          5
# of untested testcases         36
# of unsupported tests          6
                === g++ Summary ===
# of expected passes            3118
# of unexpected failures        148
# of unexpected successes       1
# of expected failures          216
# of untested testcases         6
                === g77 Summary ===
# of expected passes            125
# of unexpected failures        6
# of untested testcases         1

----------------------------------------------------------------------------
egcs-971127 + patches to target.exp:
                === libio Summary ===
# of expected passes            40
                === libstdc++ Summary ===
# of expected passes            21
# of unexpected failures        3
# of expected failures          6
                === gcc Summary ===
# of expected passes            4797
# of unexpected failures        52
# of expected failures          5
# of untested testcases         36
# of unsupported tests          6
                === g++ Summary ===
 
# of expected passes            3131
# of unexpected failures        135
# of unexpected successes       1
# of expected failures          216
# of untested testcases         6
                === g77 Summary ===
# of expected passes            125
# of unexpected failures        6
# of untested testcases         1
----------------------------------------------------------------------------
--
Kaveh R. Ghazi			Project Manager / Custom Development
ghazi@caip.rutgers.edu		ICon CMT Corp.

             reply	other threads:[~1997-12-01 19:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-12-01 19:30 Kaveh R. Ghazi [this message]
1997-12-02  8:02 ` Jeffrey A Law
  -- strict thread matches above, loose matches on Subject: below --
1997-11-29 13:40 Kaveh R. Ghazi
1997-11-30 20:14 ` Jeffrey A Law
1997-11-30 20:14 ` 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=199712020210.VAA09712@caip.rutgers.edu \
    --to=ghazi@caip.rutgers.edu \
    --cc=egcs@cygnus.com \
    --cc=law@cygnus.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).