From: Matthias Klose <doko@cs.tu-berlin.de>
To: David Edelsohn <dje@watson.ibm.com>,
gcc@gcc.gnu.org, debian-gcc@lists.debian.org
Subject: Re: [3.3 branch] Ada bootstrap failure on powerpc-linux
Date: Sun, 29 Dec 2002 14:24:00 -0000 [thread overview]
Message-ID: <15887.21620.507341.193791@gargle.gargle.HOWL> (raw)
In-Reply-To: <15887.20176.278795.928264@gargle.gargle.HOWL>
Matthias Klose writes:
> David Edelsohn writes:
> > >>>>> Matthias Klose writes:
> >
> > Matthias> ../targtyps.o(.text+0x6a): In function `get_target_long_double_size':
> > Matthias> : undefined reference to `rs6000_long_double_type_size'
> > Matthias> ../targtyps.o(.text+0x6e): In function `get_target_long_double_size':
> > Matthias> : undefined reference to `rs6000_long_double_type_size'
> >
> > This has been discussed on the GCC mailinglist before. Because
> > Gnat cannot link with the GCC infrastructure defining this variable to
> > provide variable size, it needs to assume 64-bit long double for now.
>
> I found
>
> http://gcc.gnu.org/ml/gcc/2002-03/msg00809.html
>
> but this was before branching for 3.1/3.2.
ok, found. should this be applied to the 3.3 branch again?
2002-04-02 David Edelsohn <edelsohn@gnu.org>
* config/rs6000/rs6000.h (WIDEST_HARDWARE_FP_SIZE): Define.
--- src/gcc/config/rs6000/rs6000.h~ 2002-12-10 23:42:32.000000000 +0100
+++ src/gcc/config/rs6000/rs6000.h 2002-12-29 20:58:22.000000000 +0100
@@ -611,6 +611,9 @@
#define LIBGCC2_LONG_DOUBLE_TYPE_SIZE 64
#endif
+/* Work around rs6000_long_double_type_size dependency in ada/targtyps.c. */
+#define WIDEST_HARDWARE_FP_SIZE 64
+
/* Width in bits of a pointer.
See also the macro `Pmode' defined below. */
#define POINTER_SIZE (TARGET_32BIT ? 32 : 64)
next prev parent reply other threads:[~2002-12-29 20:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-29 9:18 Matthias Klose
2002-12-29 11:39 ` David Edelsohn
2002-12-29 13:19 ` Matthias Klose
2002-12-29 14:24 ` Matthias Klose [this message]
2002-12-29 18:09 ` David Edelsohn
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=15887.21620.507341.193791@gargle.gargle.HOWL \
--to=doko@cs.tu-berlin.de \
--cc=debian-gcc@lists.debian.org \
--cc=dje@watson.ibm.com \
--cc=gcc@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).