From: Bill Schmidt <wschmidt@linux.ibm.com>
To: Fangrui Song <i@maskray.me>
Cc: Alan Modra <amodra@gmail.com>, binutils@sourceware.org
Subject: Re: Rename PowerPC64 pcrel GOT TLS relocations
Date: Sun, 7 Jun 2020 15:39:20 -0500 [thread overview]
Message-ID: <20ddb459-f86d-88f5-f826-5c685a259e0c@linux.ibm.com> (raw)
In-Reply-To: <MWHPR12MB14568AF20BD3E813FE493F9DCB840@MWHPR12MB1456.namprd12.prod.outlook.com>
On 6/7/20 2:17 PM, Fangrui Song wrote:
> On Sun, Jun 7, 2020 at 11:30 AM Bill Schmidt <wschmidt@linux.ibm.com> wrote:
>> On 6/6/20 3:02 AM, Alan Modra via Binutils wrote:
>>> On Sat, Jun 06, 2020 at 12:21:29AM -0700, Fangrui Song wrote:
>>>> On Fri, Jun 5, 2020 at 10:12 PM Alan Modra via Binutils
>>>> <binutils@sourceware.org> wrote:
>>>>> These relocations should have had REL in their names, to reflect the
>>>>> fact that they are pc-relative. Fix that now by adding _PCREL.
>>>>> I've added some back-compatibility code to support anyone using
>>>>> .reloc with the old relocations.
>>>> https://openpowerfoundation.org/?resource_lib=64-bit-elf-v2-abi-specification-power-architecture
>>>> (Revision 1.4, June 22, 2017) hasn't been updated for nearly three
>>>> years.
>>>> For these relocation types, which specification is defining them?
>>> The ELFv2 ABI has been updated to include Power10 related information,
>>> and should be released soon.
>>>
>> ...with the only caveat that "soon" is a matter of some months, just due
>> to the publication process at OpenPOWER Foundation. A specification
>> document gets a lot of scrutiny and has to go through several foundation
>> committees and a public review period.
>>
>> We're now at the point where we're having internal reviews at IBM to
>> ensure everything we say is what we mean to say, after which I'll be
>> shepherding the document through the publication process. At best guess
>> from prior experience, the final document should be available in the
>> autumn. The public review period will probably get started in 2-3
>> months, at which point you can use the review document as reference for
>> the relocations. Meantime the source code serves as intent.
>>
>> Bureaucracy and process... but ultimately it does help with the quality
>> of the document.
>>
>> Thanks,
>> Bill
> Bill, thanks for the information.
>
> A follow-up question: how can I subscribe to the updates when the
> public review period starts? I registered an account on
> openpowerfoundation.org a while ago. Now I clicked
> https://members.openpowerfoundation.org/wg/OPF/document/search?q=64-bit+elf&yt2=Search
> , searched for "64-bit elf", and I got "Power Architecture 64-Bit ELF
> V2 ABI Specification.pdf" posted on Monday, August 24, 2015, 8:47 AM,
> which is older than the 2017 version. This version is probably
> irrelevant. A bit wrestling with the website gave me
> https://members.openpowerfoundation.org/wg/OPF/mail/thread/8117 ,
> which says
>
> Click here to submit a comment or subscribe to the comment email
> distribution list for the 64-Bit ELF V2 ABI Specification: Power
> Architecture:
>
> syssw-elfv2abi@mailinglist.openpowerfoundation.org
>
> This seems to be more promising. So I sent an email to this address
> with "subscribe" in the subject, but I haven't received a confirmation
> email yet. How can I know whether I am subscribed? Additionally, if
> this is a mailing list (probably private), can a user with an account
> on openpowerfoundation.org browse the archive? Thanks.
Subscribing was correct -- I see your request out there. I am now
desperately hunting for my moderator password... I'll get this taken
care of, but I might need to get a new moderator password set up first.
The traffic volume was apparently too low for this to stick in my mind.
I apologize for my poor organization. Anyway, it should take effect
soon, and there will be an announcement on the mailing list when the
document enters the public review period.
I think you'll be able to see the archive, but I can't answer that with
authority until I sort out my authentication issue. Apologies!
Bill
next prev parent reply other threads:[~2020-06-07 20:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-06 5:12 Alan Modra
2020-06-06 7:21 ` Fangrui Song
[not found] ` <MWHPR12MB1456E96F004CB70690CB6EE4CB870@MWHPR12MB1456.namprd12.prod.outlook.com>
2020-06-06 8:02 ` Alan Modra
2020-06-07 18:30 ` Bill Schmidt
2020-06-07 19:17 ` Fangrui Song
[not found] ` <MWHPR12MB14568AF20BD3E813FE493F9DCB840@MWHPR12MB1456.namprd12.prod.outlook.com>
2020-06-07 20:39 ` Bill Schmidt [this message]
2020-06-08 14:19 ` Bill Schmidt
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=20ddb459-f86d-88f5-f826-5c685a259e0c@linux.ibm.com \
--to=wschmidt@linux.ibm.com \
--cc=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=i@maskray.me \
/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).