From: "David S. Miller" <davem@davemloft.net>
To: Nick Clifton <nickc@redhat.com>
Cc: ian@airs.com, ebotcazou@libertysurf.fr,
binutils@sources.redhat.com, schwab@suse.de
Subject: Re: Problems compiling elfxx-sparc.c
Date: Mon, 25 Apr 2005 18:32:00 -0000 [thread overview]
Message-ID: <20050425112426.59b3b1bb.davem@davemloft.net> (raw)
In-Reply-To: <426CBC64.7010008@redhat.com>
On Mon, 25 Apr 2005 10:46:12 +0100
Nick Clifton <nickc@redhat.com> wrote:
> I think that the question remains: Why is the 32-bit version of
> elfxx-sparc.c attempting to access 64-bit functions when support for
> 64-bit sparcs is not enabled ?
Because it's a genericization of all of the 32-bit and 64-bit
sparc support.
So much code is common that it's a maintainence nightmare to
have two instance of the same code just because one passes the
generic relocation object to the elf32 function and the other
passes it to the elf64 function.
MIPS does the exact same thing with it's elfxx-mips.c and people
seem to be fine with that.
I really don't want to add a pile of BFD64 ifdefs to elfxx-sparc.c,
that would be entirely silly. There has to be another solution to
this problem.
next prev parent reply other threads:[~2005-04-25 18:32 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-20 10:19 Nick Clifton
2005-04-20 13:15 ` Andreas Schwab
2005-04-20 18:26 ` David S. Miller
2005-04-20 18:40 ` David S. Miller
2005-04-20 22:38 ` Andreas Schwab
2005-04-20 23:21 ` David S. Miller
2005-04-21 12:20 ` Andreas Schwab
2005-04-21 3:16 ` Alan Modra
2005-04-21 3:24 ` David S. Miller
2005-04-22 3:19 ` Alan Modra
2005-04-22 3:53 ` David S. Miller
2005-04-21 10:50 ` Nick Clifton
2005-04-21 11:54 ` Eric Botcazou
2005-04-21 13:42 ` Ian Lance Taylor
2005-04-21 18:48 ` David S. Miller
2005-04-22 9:52 ` Nick Clifton
2005-04-22 10:02 ` Nick Clifton
2005-04-22 13:25 ` Ian Lance Taylor
2005-04-22 19:10 ` David S. Miller
2005-04-25 9:47 ` Nick Clifton
2005-04-25 18:32 ` David S. Miller [this message]
2005-04-25 19:10 ` David S. Miller
2005-04-25 21:54 ` David S. Miller
2005-04-26 8:45 ` Nick Clifton
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=20050425112426.59b3b1bb.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=binutils@sources.redhat.com \
--cc=ebotcazou@libertysurf.fr \
--cc=ian@airs.com \
--cc=nickc@redhat.com \
--cc=schwab@suse.de \
/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).