From: Mike Gilbert <floppym@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Will a 64-bit-no-multilib machine cross-compile 32-bit code?
Date: Mon, 23 Mar 2015 18:18:46 -0400 [thread overview]
Message-ID: <CAJ0EP43qFSgO5ZDG1Oc-_7eGUgN_egp3Pp1j=j74E5b0h-wCYQ@mail.gmail.com> (raw)
In-Reply-To: <20150324015104.GA32732@waltdnes.org>
On Mon, Mar 23, 2015 at 9:51 PM, Walter Dnes <waltdnes@waltdnes.org> wrote:
> On Sun, Mar 22, 2015 at 09:25:53PM -0400, Fernando Rodriguez wrote
>
>> I guess gcc devs are careful when using the model numbers (Intel
>> lists 3 for Atoms, gcc uses only two so that may account for the
>> models I mentioned) but the chance of error is there. The -mno-xxx
>> flags would safeguard against it.
>
> I have one of the earliest Atom chips. Some people have a hard time
> believing this, but it's a 32-bit-only chip; a couple of lines from
> /proc/cpuinfo
>
> model name : Intel(R) Atom(TM) CPU Z520 @ 1.33GHz
> address sizes : 32 bits physical, 32 bits virtual
>
> Intel gives the CPU's specs at...
>
> http://ark.intel.com/products/35466/Intel-Atom-Processor-Z520-512K-Cache-1_33-GHz-533-MHz-FSB
>
> ...where it specifically says...
>
> Intel 64 # No
>
> I want to make absolutely certain that "illegal instructions" are not
> compiled for it.
You will probably need to add -m32 to CFLAGS to avoid building 64-bit
objects on the 64-bit machine.
next prev parent reply other threads:[~2015-03-23 22:19 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 1:56 [gentoo-user] Will a 64-bit-no-multilib machine cross-compile 32-bit code? Walter Dnes
2015-03-19 2:27 ` Fernando Rodriguez
2015-03-19 4:20 ` Walter Dnes
2015-03-19 5:12 ` Fernando Rodriguez
2015-03-21 12:46 ` Mike Gilbert
2015-03-21 19:52 ` Fernando Rodriguez
2015-03-22 14:03 ` Mike Gilbert
2015-03-22 14:05 ` Mike Gilbert
2015-03-23 0:56 ` Fernando Rodriguez
2015-03-23 1:25 ` Fernando Rodriguez
2015-03-24 1:51 ` Walter Dnes
2015-03-23 22:18 ` Mike Gilbert [this message]
2015-03-23 22:41 ` Fernando Rodriguez
2015-03-23 22:48 ` Mike Gilbert
2015-03-24 0:37 ` Fernando Rodriguez
2015-03-24 6:06 ` Walter Dnes
2015-03-24 7:17 ` Walter Dnes
2015-03-24 17:18 ` Mike Gilbert
2015-03-24 19:01 ` Fernando Rodriguez
2015-03-25 2:01 ` Walter Dnes
2015-03-25 5:20 ` Walter Dnes
2015-03-25 6:44 ` Walter Dnes
2015-03-24 0:26 ` Peter Humphrey
2015-03-22 11:32 ` Walter Dnes
2015-03-28 11:13 ` Frank Steinmetzger
2015-03-28 13:03 ` Walter Dnes
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='CAJ0EP43qFSgO5ZDG1Oc-_7eGUgN_egp3Pp1j=j74E5b0h-wCYQ@mail.gmail.com' \
--to=floppym@gentoo.org \
--cc=gentoo-user@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