public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: GCC Development <gcc@gcc.gnu.org>,
	Binutils <binutils@sourceware.org>,
		GNU C Library <libc-alpha@sourceware.org>,
	x32-abi@googlegroups.com
Subject: Re: x32 psABI status update
Date: Sat, 19 Feb 2011 18:14:00 -0000	[thread overview]
Message-ID: <AANLkTim4mo7aXQs7YCVSqdXQhMJ0UorOrfkTJFrQNOPj@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimHHJykx4u52nuig+M+YMqcEW8yLzNSCZ391Asi@mail.gmail.com>

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.

  reply	other threads:[~2011-02-19 18:14 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 [this message]
     [not found]     ` <AANLkTikkpK9ouXckHaVzwXe+p_Cz2hVH5T7xOoQL7OSE@mail.gmail.com>
2011-02-19 20:57       ` H.J. Lu

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=AANLkTim4mo7aXQs7YCVSqdXQhMJ0UorOrfkTJFrQNOPj@mail.gmail.com \
    --to=hjl.tools@gmail.com \
    --cc=binutils@sourceware.org \
    --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).