gcc 4.3.0 status, was: Re: Building ubuntu/gcc-4_2-branch to get GCJ for arm EABI

[Koen Kooi <k.kooi@student.utwente.nl>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Robert Schuster schreef:

| Which perhaps it makes sense then to get everything working from GCJ
| 4.3.0 onwards. AFAIK this release contains all the ARM GCJ stuff we need
| and we can ask Andrew Haley if important GCJ patches have been
| introduced after the 4.3.0 release.
|
| GCC 4.3.0 support in OE is still in its infancy and requires some
| workarounds. Keep an eye on this list for news about that.

I had a look at gcc 4.3.0 last week (I need it for armv7-a[1] support),
and the situation has improved a bit:

* armv4t works again
* all debian and fedora patches were imported into OE

Debian has a few libjava patches that I didn't apply (they use a mixture
of p0 and p1 patches which I was too lazy to sort out, they are in
packages/gcc/gcc-4.3.0/debian/), so you could have a look at those.

There are still a few problems, one of which is the includes-fixed
problem, the other that gcc refuses to find stdlib.h even when passed
the correct -I${STAGING_INCDIR}. Gcc also likes to ICE like crazy on
*_Load.c in libmikmod. It's also lacking the uclibc patches.

regards,

Koen

[1] Starting with armv7 gcc distinguishes between various modes (arm,
thumb, etc), so you need to pass -march=armv7-a (the cortex-a8 tunefile
does that for you) if you want regular ARM mode and set PACKAGE_ARCH to
armv7a (without any hyphen, the cortex-a8 tunefile does that for you as
well).
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFIAO2pMkyGM64RGpERAuafAJ9Vy39Qhs53IWBPww3PmBvyIPpsQQCfSTIC
NYTbeqatKb/vJL0RiQ8fbTI=
=rIdj
-----END PGP SIGNATURE-----