From: octoploid <cryptooctoploid@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: x32 fun pants
Date: Sat, 10 Dec 2011 13:15:10 +0000 (UTC) [thread overview]
Message-ID: <loom.20111210T140702-285@post.gmane.org> (raw)
In-Reply-To: 201112100302.14676.vapier@gentoo.org
Mike Frysinger <vapier <at> gentoo.org> writes:
> On Tuesday 06 December 2011 17:39:48 Mike Frysinger wrote:
> > i'll post binaries here:
> > http://dev.gentoo.org/~vapier/x32/
>
> i've posted a stage3 tarball there now built with catalyst. if people want to
> give it a spin and file bugs, that'd probably be cool.
>
> notes:
> - don't waste time on stable packages ... your bugs will be rejected
> - when filing new bugs, check the tracker first [1], and if it isn't already
> listed, add your bug as a blocker of it
> - the default build includes all 3 ABIs for gcc/glibc
> - x32 is the default ABI
Nice.
Given that it's relatively easy to hit the 4GB barrier in the
toolchain (e.g. Firefox LTO build), wouldn't it make sense to
build gcc, binutils, et.al. as 64-bit LSB executables?
next prev parent reply other threads:[~2011-12-10 13:21 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
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 ` octoploid [this message]
2011-12-10 18:37 ` [gentoo-dev] " 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=loom.20111210T140702-285@post.gmane.org \
--to=cryptooctoploid@gmail.com \
--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