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: Paul Brook <paul at codesourcery dot com>
- To: binutils at sourceware dot org
- Cc: "Joseph S. Myers" <joseph at codesourcery dot com>, Hasjim Williams <linux-cirrus at lists dot futaris dot org>, 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
- Date: Tue, 1 Apr 2008 15:36:11 +0100
- Subject: Re: wot to do with the Maverick Crunch patches?
- References: <56d259a00803300545t36d77bf2icd9b0ef2ffac3e45@mail.gmail.com> <1207015854.25579.1245331423@webmail.messagingengine.com> <Pine.LNX.4.64.0804011403230.31882@digraph.polyomino.org.uk>
> That only covers call-preserved registers. Testing call-clobbered
> registers is harder (but normally unwind information won't be generated
> for them, so they matter less); for iWMMXt I tried testing using
> -fcall-saved-wr0 -fcall-saved-wr1 ... but found that
> CONDITIONAL_REGISTER_USAGE overrides -fcall-saved-* for the wr registers
> and there is no prologue/epilogue support for saving/restoring wcgr
> registers. You may need to temporarily modify GCC to save and restore
> such registers in order to test the unwinding for them.
Or write testcases by hand in assembly.
Paul