[haiku-development] The technical implications of making GCC 4 Hybrid the default?
- From: Matt Madia <mattmadia@xxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Sat, 20 Nov 2010 23:49:21 +0000
I'm curious what the technical (dis)advantages would be of switching
official releases to be GCC 4 Hybrids, and more importantly if it
would be feasible.
Issues:
1. GCC 2 replicants will not embed themselves into a GCC 4 compiled
application (and vice versa)
2. Looking past R1, there is (currently) no promise for GCC 4
compatibility (running R1-gcc4 apps in a post-R1 environment)
3. Having gcc4 as the default compiler may confuse users about
An example of 1) would SoundPlay not being able to replicate onto a
GCC 4 Tracker.
Benefits:
1. reduces the negativity associated with GCC 2.95.3 (eg, the
incorrect assumption of "Ew! This thing doesn't even have a modern
compiler!")
Drawbacks:
1. reduced BeOS compatibility (or rather interoperability)
Would there be any other issues other than the replicant issue?
Anything I overlooked?
Thoughts?
--mmadia
Other related posts:
