From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] x32 fun pants
Date: Thu, 15 Sep 2011 16:35:55 -0400 [thread overview]
Message-ID: <201109151635.56368.vapier@gentoo.org> (raw)
In-Reply-To: <28d0b6ed6e38725a08c800899a13145d@omrb.pnpi.spb.ru>
[-- Attachment #1: Type: Text/Plain, Size: 622 bytes --]
On Thursday, September 15, 2011 16:00:14 Alexey Shvetsov wrote:
please dont top post
> Is it accepted for merge into kernel mainline for 3.2?
no. i was just being optimistic. i'm running 3.1-rc4 atm with a smallish
patch to make it work.
> Actualy this abi looks like n32 mips abi.
yeah, a lot of the reasons behind the creation of n32 were behind the creation
of the x32 abi.
> PS why not merge all x86 abis into one keyword? because x86_32 x86_64
> x86_x32 are only abis of x86. Also we dont have different keywords for
> different mips abis (64bit and 32bit ones)
that'd be nice :)
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2011-09-15 20:40 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-15 19:34 [gentoo-dev] x32 fun pants Mike Frysinger
2011-09-15 20:00 ` Alexey Shvetsov
2011-09-15 20:35 ` Mike Frysinger [this message]
2011-09-16 7:48 ` Michał Górny
2011-09-16 7:58 ` Stratos Psomadakis
2011-09-16 8:14 ` Michał Górny
2011-09-16 15:06 ` Markos Chandras
2011-09-16 17:32 ` Mike Frysinger
2011-09-16 18:25 ` Markos Chandras
2011-09-17 5:53 ` [gentoo-dev] " Duncan
2011-09-16 18:07 ` [gentoo-dev] " Stratos Psomadakis
2011-09-15 20:12 ` Michał Górny
2011-09-15 20:33 ` Mike Frysinger
2011-09-15 21:03 ` Michał Górny
2011-09-15 21:18 ` Mike Frysinger
2011-09-16 5:46 ` [gentoo-dev] " Duncan
2011-09-16 18:15 ` Mike Frysinger
2011-09-19 23:28 ` [gentoo-dev] " Joshua Kinard
2011-09-16 8:28 ` Stratos Psomadakis
2011-09-16 16:08 ` Mike Frysinger
2011-09-16 19:09 ` Thomas Sachau
2011-09-16 20:17 ` Mike Frysinger
2011-09-16 13:36 ` Donnie Berkholz
2011-09-16 14:06 ` Michał Górny
2011-09-16 16:01 ` Mike Frysinger
2011-09-16 16:24 ` Mike Frysinger
2011-09-16 15:52 ` Mike Frysinger
2011-09-20 0:25 ` Joshua Kinard
2011-12-02 20:54 ` Mike Frysinger
2011-12-02 21:25 ` Samuli Suominen
2011-12-02 21:55 ` Mike Frysinger
2011-12-06 21:40 ` Mike Frysinger
2011-12-06 22:13 ` Markos Chandras
2011-12-06 22:39 ` Mike Frysinger
2011-12-10 8:02 ` Mike Frysinger
2011-12-10 13:15 ` [gentoo-dev] " octoploid
2011-12-10 18:37 ` Mike Frysinger
2011-12-10 19:36 ` Alec Warner
2011-12-10 19:49 ` Mike Frysinger
2011-12-10 20:01 ` Mike Gilbert
2011-12-11 1:36 ` Chí-Thanh Christopher Nguyễn
2011-12-11 3:18 ` Mike Frysinger
2011-12-12 14:47 ` Francesco Riosa
2011-12-12 17:26 ` Mike Frysinger
2011-12-12 22:47 ` Francesco Riosa
2011-12-13 21:20 ` Mike Frysinger
2011-12-08 21:22 ` [gentoo-dev] " Mike Frysinger
2011-12-08 21:29 ` Markos Chandras
2011-12-08 21:34 ` Mike Frysinger
2011-12-08 21:40 ` Markos Chandras
2011-12-08 22:11 ` Mike Frysinger
2012-06-05 18:44 ` [gentoo-dev] x32 release candidate Mike Frysinger
2012-06-06 2:17 ` Mike Frysinger
2012-06-06 5:14 ` Mike Frysinger
2012-06-06 19:40 ` Gregory M. Turner
2012-06-06 20:14 ` vivo75
2012-06-07 3:17 ` Mike Frysinger
2012-06-07 6:13 ` Luca Barbato
2012-06-07 13:38 ` Mike Frysinger
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=201109151635.56368.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/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