From: Tim Prince <tprince@computer.org>
To: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>,
gcc-bugs@gcc.gnu.org, gcc@gcc.gnu.org
Cc: David.Billinghurst@riotinto.com, echristo@redhat.com
Subject: Re: Profiling on mips-irix6? (Testcase gcc.dg/nest.c failure)
Date: Wed, 02 Oct 2002 21:54:00 -0000 [thread overview]
Message-ID: <20021003043650.DE5952CC1E@inet1.ywave.com> (raw)
In-Reply-To: <200210021422.KAA10736@caip.rutgers.edu>
On Wednesday 02 October 2002 07:22, Kaveh R. Ghazi wrote:
> When running the testsuite on mips-sgi-irix6.5, I get a failure in
> gcc.dg/nest.c:
>
> http://gcc.gnu.org/ml/gcc-testresults/2002-09/msg01040.html
>
> > FAIL: gcc.dg/nest.c (test for excess errors)
> > WARNING: gcc.dg/nest.c compilation failed to produce executable
>
> Its not just me:
> http://gcc.gnu.org/ml/gcc-testresults/2002-09/msg01050.html
>
> This test passes in the -pg flag. Looking at gcc.log, I see:
> > ld32: FATAL 9 : I/O error (/usr/lib32/mips3/gcrt1.o): No such file or
> > directory collect2: ld returned 32 exit status
>
> I can't find gcrt1.o anywhere. Its not already installed on my system
> nor is it provided by and built by gcc itself.
As I used Irix-6.5 in a previous cloak, I'll take a stab:
-pg was not the way to do profiling on Irix-6.5; I'm not surprised the
support libraries are missing. It was done by building with -g and using
speedshop.
>
> So before I proceed I was wondering whether there is some place to get
> a gcrt1.o and/or libprof1.a for irix6.
> If not, I can open a PR/change-request for someone to provide one,
How about symlinking gcrt0.o to gcrt1.o, for example?
> and
> mark the testcase to only assemble on irix, not compile & run.
I've noticed that most cygwin testers are getting a link failure; a different
problem, caused by the typical (full) installation not supporting -pg without
over-riding the library search order. Simplest cure there is to un-install
the alternate mingw runtime.
I doubt it's feasible for gcc maintainers to fix target-specific things like
this. But you're right, this test fails for target-specific reasons which
aren't the fault of gcc. Apparently, it was meant specifically to diagnose a
power-pc specific problem; shouldn't that be noted without requiring web
research, for example, by making it run only on targets where it is relevant?
--
Tim Prince
next prev parent reply other threads:[~2002-10-03 4:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-02 8:05 Kaveh R. Ghazi
2002-10-02 21:54 ` Tim Prince [this message]
2002-10-03 1:46 ` Kaveh R. Ghazi
2002-10-03 12:15 ` Jim Wilson
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=20021003043650.DE5952CC1E@inet1.ywave.com \
--to=tprince@computer.org \
--cc=David.Billinghurst@riotinto.com \
--cc=echristo@redhat.com \
--cc=gcc-bugs@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--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).