Re: QT/E 2.3.12 built
Lorn Potter <[email protected]>
| Newsgroups | gmane.comp.handhelds.opie.devel |
|---|---|
| Organization | Trolltech Pty Ltd |
| Message-ID | <[email protected]> |
On Monday 23 January 2006 03:54, Holger Freyther wrote: > Am 22.01.2006 um 16:34 schrieb robert evert: > > Hi, > > > > I really did not want to raise this discussion (again). > > But it is very interesting, and as you speak of compatibility: > > Ah don't worry. I just find it funny that some one who never > comitted to library/ tries to make a point on the compability... you are really pissing me off.. give me a frickin break, and stop with this condescending crap. i have made commits to all parts of opie. and what does it matter if I didnt. does that make me any less member of opie? > > > Wasn't the break to Qtopia when you (Familiar) switched the GCC > > version? > > What was the reason for this, apart from some new features of 3.4. The compat to sharp apps, was broken with oz's switch to gcc3, yes. > > gcc 2.95.3 is a gcc version from a development branch that was never > released, really. i seem to be able to download it just fine. even still. heck, i know commercial vendors still using it, because it generates smaller code (and not reliant on libgcc), and it works fine. > it has known issues in the parser, code generation etc. ALL software has issues. > But the point to switch to gcc3 was quite simple: > 1.) it is actively maintained > 2.) it generates better and faster code and dont forget its much bigger also because of it. > 3.) it can optimize for XScale > 4.) many other reasons prelinking, new glibc.. > 5.) many more things... AND breaks compatibility with previous gcc binaries. Sharp had the ONLY linux pda on the market, with many 3rd party developers creating applications for it. > > As most of the PDA's released the last two years use XScale it is > benefitically yes, and all of the linux pdas released were, in fact from Sharps. which were created using gcc 2 _for compatiblity reasons for all the apps out there_!! > to use a gcc that can optimize for your target. Specially if you know > that > multiple load+store is quite slow... > > And now gcc has support for visibility this allows you to control > which symbols > are visible. This means code will run faster, binaries are smaller... > which is pretty > appealing to me... -- Lorn 'ljp' Potter Trolltech Qtopia Community Manager Opie Core Developer http://qtopia.net _______________________________________________ http://opie.handhelds.org/cgi-bin/moin.cgi/DeveloperWikiIndex Opie-devel mailing list [email protected] https://handhelds.org/mailman/listinfo/opie-devel