On Mon, 23 Sep 2013 17:33:19 +0800 Jian-feng Ding <[email protected]>
said:

> Carsten,
> 
> All the embarrassings you are talking about just does not exist :)
> 
> Current Tizen pkg build is self-hosted, both ARM and IA, both 32bit and
> 64bit.
> 
> Current problem we are talking about is the developers' working distro, not
> the Tizen runtime:)

if the DEVELOPERS DISTRO were tizen... and it SHOULD be, and tizen cannot be
build on a 32bit system because 32bit support were to be REMOVED (ie qemu bugs
with 32bit memory space)... then they are. :) 

> thanks
> - jf.ding
> 
> 
> On Mon, Sep 23, 2013 at 06:23:37PM +0900, Carsten Haitzler wrote:
> > On Mon, 23 Sep 2013 08:28:06 +0300 Leon Anavi <[email protected]> said:
> > 
> > > Hi Daniel, Carsten, All,
> > > 
> > > On 2013-09-23 03:46, Daniel Juyung Seo wrote:
> > > > On Mon, Sep 23, 2013 at 8:53 AM, Carsten Haitzler
> > > >> imagine if all the engineers and executives etc. at bmw drove fords
> > > >> because
> > > >> "bmw's can't manage to get us to the office without breaking down".
> > > > 
> > > > Awesome analogy.
> > > > 
> > > > I am also against dropping 32 bit system support for dev tools.
> > > > 
> > > > I bet many people I know use 32 bit system yet.
> > > > 
> > > 
> > > The example with the cars is nice but I don't think it's very 
> > > appropriate. In my opinion it is fine to drop 32-bit support although I 
> > > still keep 32-bit distributions on some of my older computers.
> > > 
> > > Today nobody uses 16-bit OS for development of Tizen and in long term I 
> > > don't expect anybody to be using 32-bit. So dropping 32-bit support is 
> > > just a matter of time. Almost all of the CPU for personal computers 
> > > produced in the last 5 years are with 64-bit instruction sets. The 
> > > majority of developers (including me) that still have 32-bit OS on some 
> > > computers actually have a compatible 64-bit hardware and just have to 
> > > replace the OS and the dev environment with a 64-bit version.
> > 
> > 64bit os's come with a major cost in memory footprint for pointers... it's
> > quite measurable. and that doesn't change the fact that:
> > 
> > 1. arm is STILL 32bit and will be for a long time still. if tizen can't be
> > built ON an arm platform (which is 32bit) then it can't self-host on arm...
> > which is embarrassing.
> > 2. reality is that on x86 we likely might support 32bit tizen simply due to
> > the memory footprint issues, and there is still x32 which is 32bit address
> > space WITH 64bit instructions for max perf and best footprint. if we can't
> > work on x32 or ix86 we can't self host. embarrassing.
> > 3. you do know that intel mobile chips (for tablets/phones) are not 64bit
> > still (i thought baytrail may support 64bit in at least some configs, but
> > older ones... no 64bit, and baytrail devices as best i know are still not
> > shipping as of today)... :) again - if we can't self host on these...
> > embarrassing.
> > 
> > :)
> > 
> > > Best regards,
> > > Leon
> > 
> > 
> > -- 
> > Carsten Haitzler (The Rasterman) <[email protected]>
> > _______________________________________________
> > General mailing list
> > [email protected]
> > https://lists.tizen.org/listinfo/general
> 


-- 
Carsten Haitzler (The Rasterman) <[email protected]>
_______________________________________________
General mailing list
[email protected]
https://lists.tizen.org/listinfo/general

Reply via email to