Date: Tue, 2 May 2006 19:59:54 +1000 From: Peter Jeremy <peterjeremy@optushome.com.au> To: Roland Smith <rsmith@xs4all.nl> Cc: Mikhail Teterin <mi+mx@aldan.algebra.com>, stable@freebsd.org, current@freebsd.org Subject: Re: cc can't build 32-bit executables on amd64 Message-ID: <20060502095954.GA693@turion.vk2pj.dyndns.org> In-Reply-To: <20060501220414.GA74865@slackbox.xs4all.nl> References: <200605011604.26507.mi%2Bmx@aldan.algebra.com> <20060501212539.GA24193@regurgitate.ugcs.caltech.edu> <200605011739.02920.mi%2Bmx@aldan.algebra.com> <20060501220414.GA74865@slackbox.xs4all.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
--Dxnq1zWXvFF0Q93v Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, 2006-May-02 00:04:14 +0200, Roland Smith wrote: >On Mon, May 01, 2006 at 05:39:02PM -0400, Mikhail Teterin wrote: =2E.. >> create 32-bit executables. Thus created lame, for example (from the >> audio/lame port) works and happily converts mp3 files (using >> assembler-optimized routines available only for 32-bit i386). > >Lame compiles and runs just fine on amd64. But probably not as fast since it's using a generic 'C' core instead of a hand-tweaked assembler core. I read Mikhail's comment as meaning that it is possible to build non-trivial 32-bit executables on amd64, there's just work still needed to make this work as a general case. --=20 Peter Jeremy --Dxnq1zWXvFF0Q93v Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEVy2Z/opHv/APuIcRAgZuAKCTY2dxioLZ8UuUv1biKhqUedZjugCeKSRQ YNo8Aid/WYh5l166tR5lR4s= =EDc+ -----END PGP SIGNATURE----- --Dxnq1zWXvFF0Q93v--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060502095954.GA693>