From: James Macnicol <m9305357@bohm.anu.edu.au>
To: egcs@cygnus.com
Subject: Re: Shared C++ libs on i386-pc-solaris2.5.1
Date: Wed, 10 Sep 1997 22:37:00 -0000 [thread overview]
Message-ID: <34174E74.7057@bohm.anu.edu.au> (raw)
In-Reply-To: <199709100139.SAA07609@cygnus.com>
> -Tcl 8.0 will not build with egcs-970904 since "__ctype" is not found
> by
> the linker. Tcl 8.0 compiles fine with gcc 2.7.2.2.
>
> I was just discussing a similar problem with one of the i386-sco5 users.
> Was this a shared library build? The following info may be useful.
>
> --
>
> 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.
>
> This is happening because of a change to the cse pass, which is causing
> some constants to be forced into the constant pool that weren't before.
> This is a somewhat questionable optimization, since it may increase the
> size of the program without giving faster code. In any case, if you compile
> with -O2, the constant pool itself is optimized, and unused constants are
> removed. So this problem goes away at -O2.
>
> This constant pool entry should have gone into the the readonly data section
> (or into the data section), instead of the default text section.
>
> This change was copied from the svr4.h file, so I suspect that it will
> fix your problem.
>
> If not, then try the definition of SELECT_RTX_SECTION from sparc/sysv4.h.
> This will put the constant pool entry into the data section.
>
> Tue Sep 9 16:29:42 1997 Jim Wilson <wilson@cygnus.com>
>
> * i386/sco5.h (READONLY_DATA_SECTION): Define.
>
> Index: sco5.h
> ===================================================================
> RCS file: /cvs/cvsfiles/egcs/gcc/config/i386/sco5.h,v
> retrieving revision 1.1.1.1
> diff -p -r1.1.1.1 sco5.h
> *** sco5.h 1997/08/11 15:57:18 1.1.1.1
> --- sco5.h 1997/09/09 23:27:54
> *************** do { \
> *** 573,578 ****
> --- 573,580 ----
> CTORS_SECTION_FUNCTION \
> DTORS_SECTION_FUNCTION
>
> + #define READONLY_DATA_SECTION() const_section ()
> +
> #undef CONST_SECTION_FUNCTION
> #define CONST_SECTION_FUNCTION \
> void \
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.
Rebuilding Tcl 8.0 with -O2 also does not remove the
error.
Something I forgot in the original post was to say that
gcc/objc/archive.c needs a dose of <stdarg.h> to pick up the va_*
macros.
James
next prev parent reply other threads:[~1997-09-10 22:37 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 [this message]
1997-09-11 10:01 ` Jeffrey A Law
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=34174E74.7057@bohm.anu.edu.au \
--to=m9305357@bohm.anu.edu.au \
--cc=egcs@cygnus.com \
/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).