2 msgETAPS Conferences
7 msg[RFC/RFT] Improving SMS by data dependence export
8 msgIn future, to replace autotools by cmake like K...
2 msgHelp with the Machine Description
2 msgRe: Git and GCC. Why not with fork, exec and pi...
1 msgRe: update_stmt calls
10 msg[PATCH] gc --aggressive: make it really aggressive
1 msgHow to define a blackbox data type in gcc?
1 msgGenerate Codes for a something like stack/dataf...
1 msg: RE : CONSIGNMENT DELIVERY TO YOUR DOOR-STEP
1 msggcc-4.2-20071205 is now available

Re: iWMMXt/Linux EABI toolchain
\ Daniel Jacobowitz (5 Dec 2007)
. \ Paul Brook (6 Dec 2007)

1 msgBroken regression testing on Intel Darwin9
1 msgCommon logging config
2 msgRe: ACATS c460008 and VRP (was: Bootstrap failu...
9 msgPatch manager dying for a week or two
103 msgGit and GCC
2 msglibbid and floatingpoint exception access funcs
2 msgBad offset to struct member in generated code
1 msgClarification on section variable attribute usage
Subject:Re: iWMMXt/Linux EABI toolchain
Group:Gcc
From:Paul Brook
Date:6 Dec 2007


> > > > Thanks for the quick response!
> > > > I'm sure it seems I like to make hard wok for myself! It gets worse,
> > > > I'm porting Gentoo Linux to iWMMXt with pure EABI kernel and
> > > > userspace. I'm not concerned about being able to run old binaries.
> > > > So is using abi=iwmmxt really not what I want? A really bad idea?
> > >
> > > Absolutely. You want the AAPCS, not Intel's pre-AAPCS ABI.
> >
> > Actually, -mabi=iwmmxt is AAPCS based. It's diffferent from the old intel
> > iwmmxt ABI.

Yes, but not all AAPCS ABIs are equal. There are some aspects of the ABI (e.g.
enum sizes) that are target specific. gcc currently does not have an option
for both Linux and iwmmxt.

Paul


© 2004-2008 readlist.com