From: Ian Lance Taylor <ian@zembu.com>
To: hjl@varesearch.com
Cc: mark@codesourcery.com, binutils@sourceware.cygnus.com
Subject: Re: A 32bit BFD patch
Date: Sat, 10 Jul 1999 17:53:00 -0000 [thread overview]
Message-ID: <19990711005234.1254.qmail@daffy.airs.com> (raw)
In-Reply-To: <19990710174726.458E33FC1@varesearch.com>
Date: Sat, 10 Jul 1999 10:47:26 -0700 (PDT)
From: hjl@varesearch.com (H.J. Lu)
Since the latest ELF/MIPS change, elf32/mips is now 64bit. As the
result,
# ...../configure --enable-targets=all
no longer works on 32bit hosts. Here is a patch to move elf32/mips
to 64bit.
Mark, would it be feasible to instead modify your code so that 32bit
MIPS ELF support does not require a 64 bit bfd_vma? On many machines,
using a 64 bit bfd_vma is a significant cost in efficiency, and I
would prefer to not force people to pay it unnecessarily.
Ian
next prev parent reply other threads:[~1999-07-10 17:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-10 10:47 H.J. Lu
1999-07-10 17:53 ` Ian Lance Taylor [this message]
1999-07-10 23:47 ` Mark Mitchell
1999-07-11 0:26 ` H.J. Lu
1999-07-11 9:30 ` Mark Mitchell
1999-07-11 9:37 ` H.J. Lu
1999-07-11 9:46 ` Mark Mitchell
1999-07-11 19:48 ` 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=19990711005234.1254.qmail@daffy.airs.com \
--to=ian@zembu.com \
--cc=binutils@sourceware.cygnus.com \
--cc=hjl@varesearch.com \
--cc=mark@codesourcery.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).