public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/6552] make gnatlib_and_tools fails compiling a-chahan.adb on IRIX 6.2
Date: Fri, 24 Oct 2003 20:57:00 -0000 [thread overview]
Message-ID: <20031024204131.17311.qmail@sources.redhat.com> (raw)
In-Reply-To: <20020503115600.6552.ro@techfak.uni-bielefeld.de>
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=6552
------- Additional Comments From ro at gcc dot gnu dot org 2003-10-24 20:41 -------
For some reason, this comment didn't make it into bugzilla via mail ;-( So I'm
submitting it again via the web:
> This is related to the handling of depressed stack pointer, so a work
> around is to turn DSP off in 5gsystem.ads:
>
> Functions_Return_By_DSP : constant Boolean := False;
With this workaround, I was able to bootstrap current mainline (C and Ada
only) on mips-sgi-irix6.5, though still with -O2 removed as described
below. I'll use the freshly bootstrapped compiler to try another bootstrap
with -O2 and see how it goes.
Two problems:
* gnatpsta fails to link (I think there's another PR for this bug):
ld32: ERROR 33 : Unresolved text symbol "mips_abi" -- 1st referenced by
../targtyps.o.
Use linker option -v to see when and which objects, archives and dsos
are loaded.
ld32: INFO 152: Output file removed because of error.
collect2: ld returned 2 exit status
gnatlink: cannot call ../../xgcc
make[2]: *** [../../gnatpsta] Error 4
* What is the consequence of this workaround? From the comment in
targparm.ads, it seems like setting it to False for now and returning to
True later will break binary compatibility.
So how to proceed? Is a proper fix likely to be in place for GCC 3.4?
Rainer
next prev parent reply other threads:[~2003-10-24 20:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020503115600.6552.ro@techfak.uni-bielefeld.de>
2003-08-06 0:44 ` [Bug ada/6552] " pinskia at physics dot uc dot edu
2003-10-21 16:50 ` charlet at gcc dot gnu dot org
2003-10-21 18:03 ` ro at techfak dot uni-bielefeld dot de
2003-10-21 19:53 ` ro at techfak dot uni-bielefeld dot de
2003-10-22 10:49 ` [Bug middle-end/6552] " charlet at gcc dot gnu dot org
2003-10-24 20:57 ` ro at gcc dot gnu dot org [this message]
2003-10-24 21:18 ` ro at gcc dot gnu dot org
2003-10-27 12:54 ` ro at gcc dot gnu dot org
2003-10-27 13:20 ` charlet at gcc dot gnu dot org
2004-12-01 20:40 ` [Bug target/6552] " echristo at redhat dot com
2004-12-07 23:30 ` echristo at redhat dot com
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=20031024204131.17311.qmail@sources.redhat.com \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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).