From: Bob Wilson <bwilson@tensilica.com>
To: binutils@sources.redhat.com
Subject: Re: PATCH: Support 64bit BFD and 64bit host for xtensa
Date: Mon, 11 Apr 2005 16:58:00 -0000 [thread overview]
Message-ID: <425AAC0A.6060403@tensilica.com> (raw)
In-Reply-To: <20050410163925.GB28734@lucon.org>
H. J. Lu wrote:
> On Sat, Apr 09, 2005 at 01:48:35PM -0700, H. J. Lu wrote:
>
>>m68k and xtensa are failed to build with --enable-64-bit-bfd. This
>>patch fixes it.
This part is OK with me.
> It turns out that xtensa doesn't support 64bit BFD on 32bit host
> nor 64bit host. xtensa passes pointer as int to frag_variant, where
> it is stored as offsetT. This patch changes int to long.
This doesn't seem like the right solution. I'd rather not be casting pointers
to integers, even if the integer is big enough. Let me see if I can find a way
to avoid storing pointers in the frag's fr_var field.
--Bob
next prev parent reply other threads:[~2005-04-11 16:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-09 20:48 PATCH: Support 64bit BFD for m68k and xtensa H. J. Lu
2005-04-10 16:39 ` PATCH: Support 64bit BFD and 64bit host for xtensa H. J. Lu
2005-04-10 20:15 ` Andreas Schwab
2005-04-10 20:27 ` H. J. Lu
2005-04-11 16:58 ` Bob Wilson [this message]
2005-04-11 17:40 ` H. J. Lu
2005-04-14 22:38 ` Bob Wilson
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=425AAC0A.6060403@tensilica.com \
--to=bwilson@tensilica.com \
--cc=binutils@sources.redhat.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).