Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-dev
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-dev@g.o
From: Mike Frysinger <vapier@g.o>
Subject: Re: x32 fun pants
Date: Fri, 16 Sep 2011 12:24:26 -0400
On Friday, September 16, 2011 12:01:43 Mike Frysinger wrote:
> On Friday, September 16, 2011 10:06:07 Michał Górny wrote:
> > But doesn't switching mean we're going to hit LFS PITA once again?
> 
> LFS hasnt really been a pain in a long while.  but it's something worth
> raising on the x32 lists (which i'll do) since x32 has native 64bit support
> (uint64_t == %rax).  so there should be no need to have 32bit interfaces at
> all for read funcs.

actually, this is already done.  in my libx32 libc.so.6, the 64bit ver is an 
alias to the 32bit ver.
  5790: 000cff00   210 FUNC    WEAK   DEFAULT   11 openat64
  6755: 000cff00   210 FUNC    WEAK   DEFAULT   11 openat
  6055: 000d07c0    92 FUNC    WEAK   DEFAULT   11 creat
  6595: 000d07c0    92 FUNC    WEAK   DEFAULT   11 creat64

so no, there shouldnt be any LFS issues with x32.  all file offsets are 64bit.

granted, if code does something like "int x = lseek(fd, 0, SEEK_CUR)", it'll 
break.  but that's irrelevant to x32 ... that's broken for all 32bit systems.
-mike
Attachment:
signature.asc (This is a digitally signed message part.)
References:
x32 fun pants
-- Mike Frysinger
Re: x32 fun pants
-- Michał Górny
Re: x32 fun pants
-- Mike Frysinger
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: x32 fun pants
Next by thread:
Re: x32 fun pants
Previous by date:
Re: x32 fun pants
Next by date:
Re: [RFC] Adding a tiny install-mask directory list to gx86


Updated Jun 29, 2012

Summary: Archive of the gentoo-dev mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.