From: Eric Botcazou <ebotcazou@libertysurf.fr>
To: "David S. Miller" <davem@davemloft.net>
Cc: binutils@sources.redhat.com, jakub@redhat.com
Subject: Re: Add elf64-sparc TLS support.
Date: Mon, 11 Apr 2005 21:54:00 -0000 [thread overview]
Message-ID: <200504112350.16480.ebotcazou@libertysurf.fr> (raw)
In-Reply-To: <20050411143049.2ca61b9e.davem@davemloft.net>
> We also get GC and refcounting as a side effect.
Great!
> If you now diff elf32-sparc and elf64-sparc it is clear there is a lot
> of code that can be commonized out, in a similar style to elfxx-mips.c
My wildest dream. :-)
> I intend to do that in the near future so that maintaining the sparc
> BFD backends becomes simpler. The only really difficult difference
> between these two backends is the special reloc counting necessary to
> handle OLO10 relocations.
Ideally a Bugzilla PR should be opened to track this project, with the
SPARC-oriented folks in the CC list, so as to avoid duplicating work.
> I've updated the TLS sparc64 testcases in the linker as well. I only
> run the sparc64 TLS tests on platforms other than sparc-*-elf since it
> does not multiarch. This is based upon feedback from Eric.
There are probably others (sparc-rtems now comes to mind), I'll update the
list when I get a chance.
--
Eric Botcazou
next prev parent reply other threads:[~2005-04-11 21:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-11 21:35 David S. Miller
2005-04-11 21:54 ` Eric Botcazou [this message]
2005-04-12 2:30 ` David S. Miller
2005-04-12 4:34 ` Eric Botcazou
2005-04-12 8:54 ` Eric Botcazou
2005-04-12 20:45 ` David S. Miller
2005-04-13 3:48 ` Richard Henderson
2005-04-13 4:18 ` David S. Miller
2005-04-13 4:52 ` Richard Henderson
2005-04-13 6:12 ` David S. Miller
2005-04-13 6:50 ` Eric Botcazou
2005-04-13 7:06 ` David S. Miller
2005-04-13 7:52 ` Eric Botcazou
2005-04-13 22:34 ` Jakub Jelinek
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=200504112350.16480.ebotcazou@libertysurf.fr \
--to=ebotcazou@libertysurf.fr \
--cc=binutils@sources.redhat.com \
--cc=davem@davemloft.net \
--cc=jakub@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).