From: "H.J. Lu" <hjl.tools@gmail.com>
To: Xinliang David Li <davidxl@google.com>
Cc: x32-abi@googlegroups.com,
GNU C Library <libc-alpha@sourceware.org>,
GCC Development <gcc@gcc.gnu.org>,
Binutils <binutils@sourceware.org>
Subject: Re: x32 psABI status update
Date: Sat, 19 Feb 2011 20:57:00 -0000 [thread overview]
Message-ID: <AANLkTikZWkJBeteKfXgFoDG18JtSe8ihj38aSODjdsMd@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikkpK9ouXckHaVzwXe+p_Cz2hVH5T7xOoQL7OSE@mail.gmail.com>
More data
* 186.crafty from SPEC CPU 2000 (64bit integer):
o Intel Core i7
+ ~5% slower than x86-64.
+ ~29% faster than ia32.
+ Sizes in bytes:
text data bss dec
hex filename
200519 16388 1068916 1285823
139ebf crafty.32
172389 16868 1069784 1259041
133621 crafty.64
174723 16564 1068916 1260203
133aab crafty.x32
o Intel Atom
+ ~6% slower than x86-64.
+ ~7% faster than ia32.
+ Sizes in bytes:
text data bss dec
hex filename
199339 16388 1068916 1284643 139a23 crafty.32
171157 16868 1069784 1257809 133151 crafty.64
173535 16564 1068916 1259015 133607
crafty.x32
H.J.
---
On Sat, Feb 19, 2011 at 11:23 AM, Xinliang David Li <davidxl@google.com> wrote:
> This shows how important ilp32 is for some applications. It would be good to
> show the impact of larger register set. Candidates are those spec programs
> which are slower with ia32.
>
> David
>
> On Feb 19, 2011 10:14 AM, "H.J. Lu" <hjl.tools@gmail.com> wrote:
>> On Fri, Feb 18, 2011 at 8:28 PM, H.J. Lu <hjl.tools@gmail.com> wrote:
>>> On Wed, Feb 16, 2011 at 9:45 PM, H.J. Lu <hjl.tools@gmail.com> wrote:
>>>> On Wed, Feb 16, 2011 at 11:22 AM, H.J. Lu <hjl.tools@gmail.com> wrote:
>>>>> Hi,
>>>>>
>>>>> I updated x32 psABI draft to version 0.2 to change x32 library path
>>>>> from lib32 to libx32 since lib32 is used for ia32 libraries on Debian,
>>>>> Ubuntu and other derivative distributions. The new x32 psABI is
>>>>> available from:
>>>>>
>>>>> https://sites.google.com/site/x32abi/home
>>>>>
>>>>
>>>> Initial kernel, glibc and gcc port for x32 psABI draft version 0.2 is
>>>> done:
>>>>
>>>> 1. Kernel should be very stable. Fedora 14 kernel patch is also
>>>> available.
>>>> 2. Need to fix GCC run-time libraries.
>>>> 3. Need to fix glibc tests.
>>>>
>>>> Please check them out and provide feed backs.
>>>
>>> I updated x32 website:
>>>
>>> https://sites.google.com/site/x32abi/
>>>
>>> with "get started" instructions.
>>>
>>
>> I update the x32 website
>>
>> https://sites.google.com/site/x32abi/
>>
>> with data on mcf in SPEC CPU 2K:
>>
>> * 181.mcf from SPEC CPU 2000:
>> o Intel Core i7
>> + ~32% faster than x86-64.
>> + ~1% slower than ia32.
>> + Sizes in bytes:
>>
>> text data bss dec
>> hex filename
>> 12155 336 7036 19527
>> 4c47 mcf.32
>> 12421 664 13568 26653
>> 681d mcf.64
>> 11583 412 7040 19035
>> 4a5b mcf.x32
>>
>> o Intel Atom
>> + ~28% faster than x86-64.
>> + ~0.5% slower than ia32.
>> + Sizes in bytes:
>>
>> text data bss dec
>> hex filename
>> 12059 336 7036 19431
>> 4be7 mcf.32
>> 12341 664 13568 26573
>> 67cd mcf.64
>> 11411 412 7040 18863
>> 49af mcf.x32
>>
>>
>> --
>> H.J.
>
--
H.J.
prev parent reply other threads:[~2011-02-19 20:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-17 5:46 H.J. Lu
2011-02-19 4:29 ` H.J. Lu
2011-02-19 18:14 ` H.J. Lu
[not found] ` <AANLkTikkpK9ouXckHaVzwXe+p_Cz2hVH5T7xOoQL7OSE@mail.gmail.com>
2011-02-19 20:57 ` H.J. Lu [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=AANLkTikZWkJBeteKfXgFoDG18JtSe8ihj38aSODjdsMd@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=binutils@sourceware.org \
--cc=davidxl@google.com \
--cc=gcc@gcc.gnu.org \
--cc=libc-alpha@sourceware.org \
--cc=x32-abi@googlegroups.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).