29.10.2010 20:29, KP Kirchdoerfer пишет:
>
> What about the switch of gcc you mentioned a week ago? This should be done
> before beta1, so we have a fixed environment to work with for the release
> cycle.
>
What you mean?
>
> I'd say as generic as possible (486 as with 3.x) and to decicde about all the
> optimizations later.
We can provide generic i486, or i486-compatible code that is optimized 
for execution of i686 or higher CPUs, and on i686 isn't much slower than 
native i686 code.
> I have no idea what's needed to build for different cpu's,
> no idea how make usweful performance tests.
For dhrystone package I make build executables for different archs with 
optimizations. - so we can at least in one synthetic test look at 
efficiency..
>> Also I still not know opinions of members about these questions:
>> Anybody tries to test dhrystone benchmark with different
>> archs/optimizations on different CPUs? Is i486 arch with optimization
>> for i686 will be good for all? Or this optimization will cause
>> significant performance loss on some archs (Geode, i486)?
>>
>> Also, maybe it'll be good to compile all packages that are included into
>> initrd (busybox, uClibc) with optimization for specific platforms for
>> maximal performance - in any case, we must provide kernel+modules+initrd
>> for each platform?
> Let us pls fix remaining bugs (echo -e in initrd build, apkg -u) and then we
> have organizational questions that needs solutions:
> - I still miss a leaf-trac mailinglist, to keep track of TRAC entries
> - Documentation improves thx to David currently on a daily basis, but still a
> lot of work to do (though it doesn't need to be completly ready for beta1)
Ok, I'll look on scripts in this weekend.
> - Shall we provide compiled packages, as we did with Bering-uClibc ("packages
> page"), better ideas?
IMHO it'll be good to provide separate packages and prebuilt full image 
- like it was earlier.
> - What about write permissions in cvs, shall we revive the contrib section
> (see http://sourceforge.net/apps/mediawiki/leaf/index.php?title=Talk:Bering-
> uClibc_4.x_-_Developer_Guide_-_Policies_and_Guidelines)
>
Yes, IMHO it'll be good.
> Some of this should be solved before beta1, some until beta2, performance and
> different kernel etc are something for around beta3, once the dust settles and
> we have time to invest work on these.
>
> Currently we are three active developers (and working in our spare time), so
> it's necessary to focus on the most needed and important things first.
>
> And I think we have made good progress towards a release, I'm shure it can be
> done next month. Would be good to see all the work in the wild.
>
> ymmv
> kp
I also sure that we can do beta release in some weeks.

------------------------------------------------------------------------------
Nokia and AT&T present the 2010 Calling All Innovators-North America contest
Create new apps & games for the Nokia N8 for consumers in  U.S. and Canada
$10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing
Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store 
http://p.sf.net/sfu/nokia-dev2dev

_______________________________________________
leaf-devel mailing list
leaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-devel

Reply via email to