From: Jeffrey A Law <law@cygnus.com>
To: James Macnicol <m9305357@bohm.anu.edu.au>
Cc: egcs@cygnus.com
Subject: Re: Shared C++ libs on i386-pc-solaris2.5.1
Date: Thu, 11 Sep 1997 10:01:00 -0000 [thread overview]
Message-ID: <4912.873994065@hurl.cygnus.com> (raw)
In-Reply-To: <34174E74.7057@bohm.anu.edu.au>
In message < 34174E74.7057@bohm.anu.edu.au >you write:
> > Gcc is emitting a reference to __ctype into the constant pool. This is
> > a place where constants are stored if they aren't valid as immediates in
> > an instruction. This is for instance where floating point constants are
> > stored.
[ ... ]
> >
> > Tue Sep 9 16:29:42 1997 Jim Wilson <wilson@cygnus.com>
> >
> > * i386/sco5.h (READONLY_DATA_SECTION): Define.
[ ... ]
> Alas, this isn't the solution for i386-pc-solaris2.5.1.
> READONLY_DATA_SECTION() is already defined as above in
> gcc/config/i386/svr4.h which is included in the Solaris x86 config.
Hmmmm.
On some systems (PAs running hpux), you can't have a text/readonly data
item which is initialized to the address of another item.
ie
.word foo
isn't valid if it's going into the text or readonly data section.
This is becaue the dynamic linker can't modify that memory location
at runtime if "foo" is resolved from a shared library.
Maybe you're running into a similar problem.
Jeff
next prev parent reply other threads:[~1997-09-11 10:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199709100139.SAA07609@cygnus.com>
1997-09-09 19:54 ` James Macnicol
1997-09-10 22:37 ` James Macnicol
1997-09-11 10:01 ` Jeffrey A Law [this message]
1997-09-11 13:20 ` Richard Henderson
1997-09-07 5:42 James Macnicol
1997-09-07 10:11 ` H.J. Lu
[not found] <34096EF5.5768EC4F@student.anu.edu.au>
1997-09-04 15:05 ` Jim Wilson
1997-09-04 16:55 ` Jeffrey A Law
-- strict thread matches above, loose matches on Subject: below --
1997-08-31 2:07 egcs 970828 and X11 on linux/x86 H.J. Lu
1997-08-31 13:17 ` Shared C++ libs on i386-pc-solaris2.5.1 James Macnicol
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=4912.873994065@hurl.cygnus.com \
--to=law@cygnus.com \
--cc=egcs@cygnus.com \
--cc=m9305357@bohm.anu.edu.au \
/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).