On Mon, Mar 21, 2011 at 1:20 AM, Michael Matz wrote:
> Hi,
>
> On Sun, 20 Mar 2011, H.J. Lu wrote:
>
>> I don't think it will help x32 and I think it will make it harder to add
>> x32 support. I still want to see a real usage before I add it.
>
> % cat real-world.c
> /* intptr_t; what's that? */
>
Hi,
On Sun, 20 Mar 2011, H.J. Lu wrote:
> I don't think it will help x32 and I think it will make it harder to add
> x32 support. I still want to see a real usage before I add it.
% cat real-world.c
/* intptr_t; what's that? */
union space_saving_htab_element {
void *generic_pointer;
/* Usu
On Sun, Mar 20, 2011 at 10:53 PM, Mike Frysinger wrote:
> On Monday, March 21, 2011 01:35:35 H.J. Lu wrote:
>> On Sun, Mar 20, 2011 at 10:08 PM, Mike Frysinger wrote:
>> > On Thursday, March 17, 2011 01:21:16 H.J. Lu wrote:
>> >> On Wed, Mar 16, 2011 at 7:57 PM, Mike Frysinger wrote:
>> >> > in lo
On Monday, March 21, 2011 01:35:35 H.J. Lu wrote:
> On Sun, Mar 20, 2011 at 10:08 PM, Mike Frysinger wrote:
> > On Thursday, March 17, 2011 01:21:16 H.J. Lu wrote:
> >> On Wed, Mar 16, 2011 at 7:57 PM, Mike Frysinger wrote:
> >> > in looking at the gcc files, it doesnt seem like there's any defines
On Sun, Mar 20, 2011 at 10:08 PM, Mike Frysinger wrote:
> On Thursday, March 17, 2011 01:21:16 H.J. Lu wrote:
>> On Wed, Mar 16, 2011 at 7:57 PM, Mike Frysinger wrote:
>> > in looking at the gcc files, it doesnt seem like there's any defines
>> > setup to declare x32 directly. instead, you'd hav
On Thursday, March 17, 2011 01:21:16 H.J. Lu wrote:
> On Wed, Mar 16, 2011 at 7:57 PM, Mike Frysinger wrote:
> > in looking at the gcc files, it doesnt seem like there's any defines
> > setup to declare x32 directly. instead, you'd have to do something
> > like: #ifdef __x86_64__
> > # if __SIZEO
On 03/16/2011 10:21 PM, H.J. Lu wrote:
> On Wed, Mar 16, 2011 at 7:57 PM, Mike Frysinger wrote:
>> On Wednesday, March 16, 2011 08:39:57 H.J. Lu wrote:
>>> On Tue, Mar 15, 2011 at 10:24 PM, Mike Frysinger wrote:
so we get back to my original e-mail:
are you getting a unique host t
On Wed, Mar 16, 2011 at 10:45 PM, Mike Frysinger wrote:
> On Thursday, March 17, 2011 01:21:16 H.J. Lu wrote:
>> On Wed, Mar 16, 2011 at 7:57 PM, Mike Frysinger wrote:
>> > ok, took long enough, but that answers most things. your usage of "x32-"
>> > prefixed binaries in the documentation seems
On Thursday, March 17, 2011 01:21:16 H.J. Lu wrote:
> On Wed, Mar 16, 2011 at 7:57 PM, Mike Frysinger wrote:
> > ok, took long enough, but that answers most things. your usage of "x32-"
> > prefixed binaries in the documentation seems to imply a lot more than the
> > fact you just picked those lo
On Wed, Mar 16, 2011 at 7:57 PM, Mike Frysinger wrote:
> On Wednesday, March 16, 2011 08:39:57 H.J. Lu wrote:
>> On Tue, Mar 15, 2011 at 10:24 PM, Mike Frysinger wrote:
>> > so we get back to my original e-mail:
>> > are you getting a unique host tuple for this ? or are you
>> > extending
On Wednesday, March 16, 2011 08:39:57 H.J. Lu wrote:
> On Tue, Mar 15, 2011 at 10:24 PM, Mike Frysinger wrote:
> > so we get back to my original e-mail:
> >are you getting a unique host tuple for this ? or are you
> > extending x86_64-linux-gnu ? so the only way of knowing which ABI is to
Mike Frysinger writes:
> but it doesnt say what to do for binutils or gcc itself. obviously you cant
> use the -mx32 flag when building the cross gcc for the first time since the
> current native gcc wont support it.
Of course, for a compiler tool the only thing that matters is the
target.
A
On Tue, Mar 15, 2011 at 10:24 PM, Mike Frysinger wrote:
> On Wednesday, March 16, 2011 00:51:37 H.J. Lu wrote:
>> On Tue, Mar 15, 2011 at 9:30 PM, Mike Frysinger wrote:
>> > On Wednesday, March 16, 2011 00:17:04 H.J. Lu wrote:
>> >> On Mon, Mar 7, 2011 at 1:33 PM, Mike Frysinger wrote:
>> >> > On
On Wednesday, March 16, 2011 00:51:37 H.J. Lu wrote:
> On Tue, Mar 15, 2011 at 9:30 PM, Mike Frysinger wrote:
> > On Wednesday, March 16, 2011 00:17:04 H.J. Lu wrote:
> >> On Mon, Mar 7, 2011 at 1:33 PM, Mike Frysinger wrote:
> >> > On Saturday, March 05, 2011 14:08:04 H.J. Lu wrote:
> >> >> Many
On Tue, Mar 15, 2011 at 9:30 PM, Mike Frysinger wrote:
> On Wednesday, March 16, 2011 00:17:04 H.J. Lu wrote:
>> On Mon, Mar 7, 2011 at 1:33 PM, Mike Frysinger wrote:
>> > On Saturday, March 05, 2011 14:08:04 H.J. Lu wrote:
>> >> Many x32 bugs are fixed in kernel, glibc, binutils and GCC:
>> >>
>>
On Wednesday, March 16, 2011 00:17:04 H.J. Lu wrote:
> On Mon, Mar 7, 2011 at 1:33 PM, Mike Frysinger wrote:
> > On Saturday, March 05, 2011 14:08:04 H.J. Lu wrote:
> >> Many x32 bugs are fixed in kernel, glibc, binutils and GCC:
> >>
> >> https://sites.google.com/site/x32abi/
> >>
> >> The major
Hi,
Almost all x32 bugs in kernel, glibc and binutils are fixed:
https://sites.google.com/site/x32abi/
There are no unexpected failures in glibc testsuite. I am
working on remaining GCC bugs.
--
H.J.
On Mon, Mar 7, 2011 at 1:33 PM, Mike Frysinger wrote:
> On Saturday, March 05, 2011 14:08:04 H.J. Lu wrote:
>> Many x32 bugs are fixed in kernel, glibc, binutils and GCC:
>>
>> https://sites.google.com/site/x32abi/
>>
>> The major remaining issues are glibc/gcc testsuite failures,
>> kernel core d
On Saturday, March 05, 2011 14:08:04 H.J. Lu wrote:
> Many x32 bugs are fixed in kernel, glibc, binutils and GCC:
>
> https://sites.google.com/site/x32abi/
>
> The major remaining issues are glibc/gcc testsuite failures,
> kernel core dump and signal handler unwind.
are you getting a unique host
On Sat, Mar 5, 2011 at 11:08 AM, H.J. Lu wrote:
> Hi,
>
> Many x32 bugs are fixed in kernel, glibc, binutils and GCC:
>
> https://sites.google.com/site/x32abi/
>
> The major remaining issues are glibc/gcc testsuite failures,
> kernel core dump and signal handler unwind.
>
I checked in a kernel pa
Hi,
Many x32 bugs are fixed in kernel, glibc, binutils and GCC:
https://sites.google.com/site/x32abi/
The major remaining issues are glibc/gcc testsuite failures,
kernel core dump and signal handler unwind.
--
H.J.
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 databssdec
hexfilename
On Fri, Feb 18, 2011 at 8:28 PM, H.J. Lu wrote:
> On Wed, Feb 16, 2011 at 9:45 PM, H.J. Lu wrote:
>> On Wed, Feb 16, 2011 at 11:22 AM, H.J. Lu 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 librari
On Wed, Feb 16, 2011 at 9:45 PM, H.J. Lu wrote:
> On Wed, Feb 16, 2011 at 11:22 AM, H.J. Lu 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 distributio
On Wed, Feb 16, 2011 at 11:22 AM, H.J. Lu 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://s
25 matches
Mail list logo
