From: Anthony Green <green@redhat.com>
To: binutils@sources.redhat.com, gcc@gnu.org
Subject: 64-bit Solaris and shared libraries
Date: Sat, 29 Mar 2003 09:16:00 -0000 [thread overview]
Message-ID: <1048907231.2638.47.camel@escape> (raw)
64-bit Solaris systems require 0 in e_flags of the ELF header (implying
RMO code). gas currently defaults to TSO for sparc64, so you can't use
gcc to create a working .so without also using -Wa,-TSO.
Should gas be changed to always default to TSO? Or should GCC pass -TSO
to the assembler was suggested here:
http://gcc.gnu.org/ml/gcc-bugs/2002-09/msg00742.html
Modifying gas certainly seems like a safe choice.
AG
next reply other threads:[~2003-03-29 3:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-29 9:16 Anthony Green [this message]
2003-03-29 11:22 ` Jakub Jelinek
2003-03-29 19:51 ` Anthony Green
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=1048907231.2638.47.camel@escape \
--to=green@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=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).