This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
Re: wot to do with the Maverick Crunch patches?
- From: "Hasjim Williams" <linux-cirrus at lists dot futaris dot org>
- To: "Joseph S. Myers" <joseph at codesourcery dot com>
- Cc: "Martin Guy" <martinwguy at yahoo dot it>, linux-cirrus at freelists dot org, "GCC" <gcc at gcc dot gnu dot org>, openembedded-devel at lists dot openembedded dot org, binutils at sourceware dot org
- Date: Tue, 01 Apr 2008 15:00:28 +1000
- Subject: Re: wot to do with the Maverick Crunch patches?
- References: <56d259a00803300545t36d77bf2icd9b0ef2ffac3e45@mail.gmail.com> <1206942412.15179.1245142739@webmail.messagingengine.com> <Pine.LNX.4.64.0803311126210.1358@digraph.polyomino.org.uk> <1207015854.25579.1245331423@webmail.messagingengine.com>
On Tue, 01 Apr 2008 12:10:54 +1000, "Hasjim Williams"
<linux-cirrus@lists.futaris.org> said:
> gcc uses the code in unwind-arm.c etal to call the functions
> (create_unwind_entry, unwind_save_mv etc) binutils gas/config/tc-arm.c
> to do the frame unwinding, right? To do the unwind parsing (of table 4
> from 9.3 in IHI 0038A), what function in binutils gas/config/tc-arm.c is
> called?
To answer my own question:
gcc/gcc/config/arm/pr-support.c -> __gnu_unwind_execute
uws is the GNU unwinding state as defined in unwind-arm.h
e.g. for VFP
gnu_Unwind_Save_VFP in libunwind.S called from unwind-arm.c /
_Unwind_VRS_Pop
I'm not sure at the moment, what regclass (UVRSC) MaverickCrunch
registers are being classed as. I guess with my invalid
binutils-crunch.patch they would be classed as UVRSC_WMMXD... Which
never "worked" (or even compiled) in gcc 4.2.2 or gcc 4.1.2 since
Joseph's patch hadn't been merged in, and so the opcode c6 or c1 etc
would fail.
I suppose we need a DEMAND_SAVE_MAVERICK like DEMAND_SAVE_VFP WMMXD etal
...