[haiku-development] Re: Disabling Strict Aliasing for GCC4 Builds
- From: Ingo Weinhold <ingo_weinhold@xxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Fri, 18 Apr 2008 16:56:07 +0200
On 2008-04-18 at 11:22:28 [+0200], Andreas Färber <andreas.faerber@xxxxxx>
wrote:
> Am 18.04.2008 um 06:55 schrieb scott mc:
>
> > Just wondering if you are also going to be checking the BePorts ports
> > on Haiku in both GCC2.95 and GCC4? I see the plan is to shift focus
> > to Haiku, so might be good to test out on both, so if/when the move is
> > made to GCC4 we'll have a better idea of where the various ports
> > stand.
>
> I did start some porting with gcc4 but shifted back to gcc2 since the
> availability of the Development Optional Package. Native compilation
> is easier than cross-compilation for many packages. And sharing
> working copies between Linux and Haiku is a little problematic at this
> stage... thus pushing my WC patches in progress to SVN is a first step
> to merge them on Linux for gcc4 later on.
>
> But I must say, I don't expect real trouble in that direction since
> most packages I know (all apart from QEMU!) are compiled using gcc4 on
> other platforms anyway. The opposite direction of getting recent
> packages to work with gcc2 seems more complicated, as heard from
> Ryan's WebKit.
>
> If with some more testing my gcc4 Haiku turns out to be usable to some
> degree, maybe someone can hint me on how to get a gcc4 onto Haiku. --
> Or maybe, since most packages are C only, it might work to create a
> gcc4 compiler for gcc2 based Haiku?
My plan is to adjust the runtime loader to seamlessly support a mixed
gcc2/gcc4 environment. (Will do that probably quite soon when I need some
recreational hacking.) Then, at least theoretically, it should be fairly
easy to build a native gcc4 using gcc2, since the gcc2-built tool chain
would be available under a gcc4 Haiku.
CU, Ingo
Other related posts:
