From: "H. Peter Anvin" <hpa@zytor.com>
To: Andy Lutomirski <luto@amacapital.net>, "H.J. Lu" <hjl.tools@gmail.com>
Cc: Jan Beulich <JBeulich@suse.com>,
Binutils <binutils@sourceware.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: RFC: Add -mshared option to x86 ELF assembler
Date: Wed, 20 May 2015 13:32:05 -0700 [thread overview]
Message-ID: <555CEF45.4090609@zytor.com> (raw)
In-Reply-To: <CALCETrUb7yCvToB6AiGbChqiXzPYQHnYAjbYnr_JUsP3QEwAEQ@mail.gmail.com>
On 05/20/2015 01:02 PM, Andy Lutomirski wrote:
>>
>> I got
>>
>> [hjl@gnu-tools-1 kernel.org]$ readelf -r old/vmlinux.o | head -5
>>
>> Relocation section '.rela.text' at offset 0xafea2f0 contains 205717 entries:
>> Offset Info Type Sym. Value Sym. Name + Addend
>> 000000000001 1253100000002 R_X86_64_PC32 0000000000001e70 __fentry__ - 4
>> 000000000009 1c8c00000002 R_X86_64_PC32 0000000000000000 .data + 51bc
>> [hjl@gnu-tools-1 kernel.org]$ readelf -r new/vmlinux.o | head -5
>>
>> Relocation section '.rela.text' at offset 0xafea280 contains 205711 entries:
>> Offset Info Type Sym. Value Sym. Name + Addend
>> 000000000001 1253100000002 R_X86_64_PC32 0000000000001e70 __fentry__ - 4
>> 000000000009 1c8c00000002 R_X86_64_PC32 0000000000000000 .data + 51bc
>> [hjl@gnu-tools-1 kernel.org]$
>>
>> It removes 6 relocations. On gcc master branch,
>>
>> [hjl@gnu-tools-1 gcc-misc]$ size build-x86_64-linux*/gcc/cc1
>> text data bss dec hex filename
>> 21529621 62256 1348312 22940189 15e0a1d build-x86_64-linux.branch/gcc/cc1
>> 21529749 62256 1348312 22940317 15e0a9d build-x86_64-linux/gcc/cc1
>> [hjl@gnu-tools-1 gcc-misc]$ size build-x86_64-linux*/gcc/cc1plus
>> text data bss dec hex filename
>> 23713509 62400 1372760 25148669 17fbcfd build-x86_64-linux.branch/gcc/cc1plus
>> 23713669 62400 1372760 25148829 17fbd9d build-x86_64-linux/gcc/cc1plus
>> [hjl@gnu-tools-1 gcc-misc]$
>>
>> It is more effective. I will run more tests.
>
> This seems like a sensible idea, but I can imagine it breaking some
> weird use cases (like that one Linux thing). Is that okay?
>
What about the patch I posted recently?
-hpa
next prev parent reply other threads:[~2015-05-20 20:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-13 0:14 RFC: Add -mshared option to x86 ELF assembler H.J. Lu
2015-05-13 11:50 ` H.J. Lu
2015-05-13 12:59 ` H.J. Lu
2015-05-20 20:02 ` Andy Lutomirski
2015-05-20 20:32 ` H. Peter Anvin [this message]
2015-05-20 20:54 ` Andy Lutomirski
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=555CEF45.4090609@zytor.com \
--to=hpa@zytor.com \
--cc=JBeulich@suse.com \
--cc=binutils@sourceware.org \
--cc=hjl.tools@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.