Re: Compiling for a different architecture?

From: Thomas Schweikle (tps_at_vr-web.de)
Date: 03/27/05 

Date: Sun, 27 Mar 2005 01:53:27 +0100

Jed Clear wrote:

> Thomas Schweikle wrote:
>> Mathieu Arnold schrieb:
>> > You should taste alpha or sparc64, those are different
>> > architectures :-)
>>
>> Or 65816, 8051, Z80, 6502, 6809, 6802, 8080, 8085, ...
>
> Never one not to run a good joke into the ground, how about
>
> 68000, PA-RISC, ARM ...
>
> This is starting to sound like the NetBSD supported architecture
> list. ;-)
>
> How about the one that started it all, the 4004? Anybody recall
> when Intel was a memory company, and they created the 4004 to sell
> more memory?
>
> How about a 74LS181 4 bit ALU? Had to dust off my old hard bound
> TI TTL
> Data Book to make sure, but I did remember that number. They were
> fairly tasty. Of course give me a few bags full of 74LS00 chips,
> and I can go to the moon, rule the world, or crack DES.
>
> I expect someone to start adding transistor or tube part number
> next, but I'm only as old as dirt, not rocks. :-)

Yes it is a bit off topic now, but: you are one of the few able to
build a CPU from ground up. They are dieing away. How long and no
one even knows what a ALU is?

But To come back to what I wanted to say: sure --- a PII and an i586
are the same architecture. But I can't consider them being
identical. PII at least has an extended instruction set compared
against an i586. Thus it would be wise to have them distinct, not
packed into the same "i386" architecture type.

Doing it that way has consequences: it is impossible to take only
one "/usr/src", then compile for different CPU (PII, PIII, i586).
You'll have to make it a lot more complicated:

have "/usr/src", copy it to "/usr/PII", then change to this
directory, compile. The same for all other CPU you are willing to
compile for. I'd like to have a way to do this with only one source
(I have to cvsup), keeping the resulting binaries in differrent
directories. Is this possible at all at the moment? 

-- 
Thomas

Relevant Pages

  • =?windows-1252?q?Re=3A_Intel=28r=29_Core=992_Duo_Processors=22?=
    ... Can I still run program from the i386 architecture? ... I've bought a program some months ago. ... Do I still compile them for i386? ... CPU.) ...
    (Fedora)
  • Re: [PATCH] 2.6 workaround for Athlon/Opteron prefetch errata
    ... >optimisations independently of each other', is fairly simple, (in ... >concept), and elegant, (as it lets you compile the most finely tuned ... >Up to now, selecting a CPU to compile for basically means, "Use ... it's silly to include them all in a kernel for a 386. ...
    (Linux-Kernel)
  • Re: FreeRTOS context switch time
    ... It takes time and effort to become fluent with any complex cpu ... identify your assumptions and adjust your mental model ... when programming resource scarce micro-controllers ... peripheral on a particular cpu/os architecture. ...
    (comp.arch.embedded)
  • Re: Packet loss with traffic shaper and routing
    ... I did that and compiled the kernel. ... #error DEVICE_POLLING is not compatible with SMP ... It should compile with both SMP and POLLING. ... There is no other major services in this machine, cpu utilization is ...
    (freebsd-net)
  • RE: [PATCH v2:3/3]Export cpu topology by sysfs
    ... >>To: Yanmin Zhang ... >>> If one architecture wants to support this feature, ... >>group for cpu online/offline events. ... The topology information for an ...
    (Linux-Kernel)