From: Eric Christopher <echristo@redhat.com>
To: Daniel Jacobowitz <dan@debian.org>
Cc: binutils@sources.redhat.com, linux-mips@linux-mips.org
Subject: Re: Problems generating shared library for MIPS using binutils-2.13...
Date: 05 Nov 2002 11:21:37 -0800 [thread overview]
Message-ID: <1036524097.1509.169.camel@ghostwheel> (raw)
In-Reply-To: <20021105183220.GA8656@nevyn.them.org>
> The principal thing is that I want O32 code. You can't use a higher
> ISA level than MIPS2 and still use O32, as far as I understand. And
> this setup has a 32-bit kernel, so using MIPS3/4/64 instructions in
> userspace is a real losing proposition.
>
You should be able to do -mips32 -mabi=32, however, I wouldn't bet on
this working atm :)
> I obviously want -mtune=sb1. So probably I should just be using
> -mtune=sb1 -mips2. And hack the GENERATE_BRANCHLIKELY test to honor
> -mtune. Blech, I wish these options were less confusing!
>
:) Good idea on the GENERATE_BRANCHLIKELY. I think it probably should be
dependent on mtune anyhow.
-eric
--
Yeah, I used to play basketball...
next prev parent reply other threads:[~2002-11-05 19:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-25 16:38 Problems generating shared library for MIPS using binutils-2.13 Steven J. Hill
2002-10-25 16:44 ` Daniel Jacobowitz
2002-10-25 16:54 ` Steven J. Hill
2002-10-25 17:06 ` Maciej W. Rozycki
2002-11-04 14:49 ` Steven J. Hill
2002-11-04 15:02 ` H. J. Lu
2002-11-04 16:57 ` Steven J. Hill
2002-11-04 17:11 ` H. J. Lu
2002-11-04 17:16 ` Steven J. Hill
2002-11-04 17:24 ` H. J. Lu
2002-11-05 15:19 ` Richard Sandiford
2002-11-05 17:15 ` H. J. Lu
2002-11-05 17:26 ` Daniel Jacobowitz
2002-11-05 17:33 ` H. J. Lu
2002-11-05 18:17 ` Richard Sandiford
2002-11-05 18:32 ` Daniel Jacobowitz
2002-11-05 19:21 ` Eric Christopher [this message]
2002-10-25 17:50 ` H. J. Lu
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=1036524097.1509.169.camel@ghostwheel \
--to=echristo@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=dan@debian.org \
--cc=linux-mips@linux-mips.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