Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 27 May 2009 18:40:51 +0200 (CEST)
From:      Wojciech Puchar <wojtek@wojtek.tensor.gdynia.pl>
To:        Kirk Strauser <kirk@strauser.com>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: FreeBSD & Software RAID
Message-ID:  <alpine.BSF.2.00.0905271832320.53013@wojtek.tensor.gdynia.pl>
In-Reply-To: <200905271048.27837.kirk@strauser.com>
References:  <4A1AA3DC.5020300@network-i.net> <4A1CD688.4020604@infracaninophile.co.uk> <alpine.BSF.2.00.0905271651550.52163@wojtek.tensor.gdynia.pl> <200905271048.27837.kirk@strauser.com>

next in thread | previous in thread | raw e-mail | index | archive | help
>> in C, there will work as good in 64-bit mode and in 32-bit mode.
>
> Wojciech, I have to ask: are you actually a programmer or are you repeating

yes i am. if you are interested i wrote programs for x86, ARM (ARM7TDMI), 
MIPS32 (4Kc), and once for alpha. I have quite good knowledge for ARM and 
MIPS assembly, for x86 - quite outdated as i wrote my last assembly 
program when 486 was new CPU.

> things you've read elsewhere?

you probably mistaken me with some poeple on that list that do this.

If you are reading my posts on that list (and maybe others) you know that 
the last thing i do is to repeat and repeat know and popular opinions :)

> I can think of a whole list of reasons why code
> written to target a 64-bit system would be non-trivial to port to 32-bit,

you talk about performance or if it work at all?

i already wrote a lot of programs, and after moving to 64-bit (amd64) only 
one wasn't working just after recompiling, because i assumed that pointer 
is 4 byte long.

do you have any other examples of code non-portability between amd64 and 
i386?

I say "between amd64 and i386" because there are more issues with other 
archs, where for example non-aligned memory access is not allowed.




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.0905271832320.53013>