From: Robert Lipe <robertl@dgii.com>
To: "H.J. Lu" <hjl@lucon.org>
Cc: egcs@cygnus.com
Subject: Re: does linux -fPIC/eh do so poorly?
Date: Mon, 16 Feb 1998 14:21:00 -0000 [thread overview]
Message-ID: <19980216150211.41958@dgii.com> (raw)
In-Reply-To: <m0y4WkF-00058fC@ocean.lucon.org>
[ OpenServer, EGCS from 0216 ]
> > make check-g++ RUNTESTFLAGS="--tool_opts -fPIC old-deja.exp=eh*"
> >
> > === g++ Summary ===
> >
> > # of expected passes 66
> > # of unexpected failures 37
> # make check-g++ RUNTESTFLAGS="--tool_opts -fPIC old-deja.exp=eh*"
>
> === g++ Summary ===
>
> # of expected passes 102
> # of untested testcases 1
> /home/work/gnu/bin/egcs/gcc/testsuite/../xgcc version egcs-2.90.24 980208 (egcs-1.0.2 prerelease)
>
> It looks fine on linux. I have been working with egcs 1.0.2. I haven't
> built egcs for a few days now.
Thanx for the sanity test, H.J.
When I do the same in my 1.0.2 tree, I almost see the same thing you see.
=== g++ Summary ===
# of expected passes 103
/home/play/egcs-release/native/gcc/testsuite/../xgcc version egcs-2.90.24 980208
(egcs-1.0.2 prerelease)
I better go do some digging here...
next prev parent reply other threads:[~1998-02-16 14:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-02-16 11:44 Robert Lipe
1998-02-16 14:21 ` H.J. Lu
1998-02-16 14:21 ` Robert Lipe [this message]
1998-02-18 2:42 ` Alexandre Oliva
1998-02-18 2:42 ` Robert Lipe
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=19980216150211.41958@dgii.com \
--to=robertl@dgii.com \
--cc=egcs@cygnus.com \
--cc=hjl@lucon.org \
/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).