From: David Daney <ddaney@avtrex.com>
To: binutils@sourceware.org
Cc: Ian Lance Taylor <ian@wasabisystems.com>
Subject: Re: Committing MIPS -mno-shared patch
Date: Wed, 02 Mar 2005 22:29:00 -0000 [thread overview]
Message-ID: <42263E58.5060005@avtrex.com> (raw)
In-Reply-To: <20041210194800.6490.qmail@gossamer.airs.com>
Ian Lance Taylor wrote:
> This is the patch I am committing to add support for the -mno-shared
> option to the MIPS target.
>
> Ian
>
> gas/ChangeLog:
> 2004-12-10 Ian Lance Taylor <ian@wasabisystems.com>
>
> * config/tc-mips.c (mips_in_shared): New static variable.
> (macro_build_lui): Permit "_gp" if !mips_in_shared.
> (md_longopts): Add -mshared and -mno-shared.
> (md_parse_option): Handle OPTION_MSHARED and OPTION_MNO_SHARED.
> (s_cpload): Implement !mips_in_shared case.
> (s_cpsetup): Likewise.
> * doc/c-mips.texi (MIPS Opts): Document -mno-shared.
> * NEWS: Mention -mno-shared.
>
> gas/testsuite/ChangeLog:
> 2004-12-10 Ian Lance Taylor <ian@wasabisystems.com>
>
> * gas/mips/elf-rel23a.d: New test.
> * gas/mips/elf-rel23b.d: New test.
> * gas/mips/elf-rel25.s: New test.
> * gas/mips/elf-rel25.d: New test.
> * gas/mips/elf-rel25a.d: New test.
> * gas/mips/mips.exp: Run new tests.
>
>
FYI:
-mno-shared appears to be broken on o32 LE for large programs.
I have a large program composed of about 250,000 lines of code in about
1000 source files (mostly java but with some C and C++ thrown in for
good measure). Linking of this program causes the linker to create
multiple GOTs.
When building with -Wa,-mno-shared there is some as of yet undetermined
problem with the resulting executable preventing it from running.
Without -Wa,-mno-shared there are no problems.
David Daney.
next prev parent reply other threads:[~2005-03-02 22:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-10 19:48 Ian Lance Taylor
2005-03-02 22:29 ` David Daney [this message]
2005-03-03 1:02 ` Ian Lance Taylor
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=42263E58.5060005@avtrex.com \
--to=ddaney@avtrex.com \
--cc=binutils@sourceware.org \
--cc=ian@wasabisystems.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).