From: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
To: carlos@systemhalted.org (Carlos O'Donell)
Cc: dave.anglin@nrc.ca, binutils@sourceware.org,
parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Re: [PATCH] Add TLS support for hppa-linux.
Date: Thu, 25 May 2006 02:34:00 -0000 [thread overview]
Message-ID: <200605241704.k4OH4s2W027366@hiauly1.hia.nrc.ca> (raw)
In-Reply-To: <119aab440605240804y5572dc47tba09bcaec0d5b71a@mail.gmail.com> from "Carlos O'Donell" at May 24, 2006 11:04:38 am
> It's never too late, which lines were too long?
Any lines over 79 characters:
+ enum {
+ GOT_UNKNOWN = 0, GOT_NORMAL = 1, GOT_TLS_GD = 2, GOT_TLS_LDM = 4, GOT_TLS_I
+#define hppa_elf_local_got_tls_type(abfd) \
+ ((char *)(elf_local_got_offsets (abfd) + (elf_tdata (abfd)->symtab_hdr.sh_inf
o * 2)))
+ if ((hh->tls_type & (GOT_TLS_GD|GOT_TLS_IE)) == (GOT_TLS_GD|GOT_TLS_IE
))
+ if ((*local_tls_type & (GOT_TLS_GD|GOT_TLS_IE)) == (GOT_TLS_GD|GOT
_TLS_IE))
+ if ((*local_tls_type & (GOT_TLS_GD|GOT_TLS_IE)) == (GOT_TLS_GD
|GOT_TLS_IE))
+ loc += htab->srelgot->reloc_count++ * sizeof (Elf32_External_Rel
a);
+ loc += htab->srelgot->reloc_count * sizeof (Elf32_External_R
ela);
+ outrel.r_info = ELF32_R_INFO (indx,R_PARISC_TLS_DTPMOD32
);
+ bfd_put_32 (output_bfd, 0, htab->sgot->contents + cur_of
f);
+ bfd_put_32 (output_bfd, relocation - dtpoff_base (info
),
+ bfd_put_32 (output_bfd, relocation - dtpoff_base (info
),
+ outrel.r_info = ELF32_R_INFO (indx, R_PARISC_TLS_DTP
OFF32);
+ outrel.r_info = ELF32_R_INFO (indx, R_PARISC_TLS_TPREL32
);
Dave
--
J. David Anglin dave.anglin@nrc-cnrc.gc.ca
National Research Council of Canada (613) 990-0752 (FAX: 952-6602)
prev parent reply other threads:[~2006-05-24 17:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-15 10:10 Carlos O'Donell
2006-05-24 13:23 ` Nick Clifton
2006-05-24 14:18 ` [parisc-linux] " John David Anglin
2006-05-24 23:53 ` Carlos O'Donell
2006-05-25 2:34 ` John David Anglin [this message]
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=200605241704.k4OH4s2W027366@hiauly1.hia.nrc.ca \
--to=dave@hiauly1.hia.nrc.ca \
--cc=binutils@sourceware.org \
--cc=carlos@systemhalted.org \
--cc=dave.anglin@nrc.ca \
--cc=parisc-linux@lists.parisc-linux.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).