From: Michael Hope <michael.hope@linaro.org>
To: Richard Henderson <rth@twiddle.net>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
ramana.radhakrishnan@arm.com, richard.earnshaw@arm.com
Subject: Re: [RFC, ARM] Convert thumb1 prologue completely to rtl
Date: Sun, 19 Jun 2011 21:41:00 -0000 [thread overview]
Message-ID: <BANLkTik0AQksV2-Ue=WQqahzfo=pv080QA@mail.gmail.com> (raw)
In-Reply-To: <4DFCF630.4080908@twiddle.net>
On Sun, Jun 19, 2011 at 7:02 AM, Richard Henderson <rth@twiddle.net> wrote:
> I couldn't find anything terribly tricky about the conversion.
>
> The existing push_mult pattern would service thumb1 with just
> a tweak or two to the memory predicate and the length.
>
> The existing emit_multi_reg_push wasn't set up to handle a
> complete switch of registers for unwind info. I thought about
> trying to merge them, but thought chickened out.
>
> I havn't cleaned out the code that is now dead in thumb_pushpop.
> I'd been thinking about maybe converting epilogues completely
> to rtl as well, which would allow the function to be deleted
> completely, rather than incrementally.
>
> I'm unsure what testing should be applied. I'm currently doing
> arm-elf, which does at least have a thumb1 multilib, and uses
> newlib so I don't have to fiddle with setting up a full native
> cross environment. What else should be done? arm-eabi?
Hi Richard. arm-linux-gnueabi bootstraps in Thumb1 mode. I haven't
done many builds in that way, but here's the latest:
http://builds.linaro.org/toolchain/gcc-4.6.0-RC-20110321/logs/armv7l-maverick-cbuild93-ursa1-armv5thumbr1/
-- Michael
next prev parent reply other threads:[~2011-06-19 20:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-18 19:31 Richard Henderson
2011-06-19 21:41 ` Michael Hope [this message]
2011-06-24 4:24 ` Richard Henderson
2011-06-24 10:30 ` Richard Earnshaw
2011-06-27 18:52 ` Richard Henderson
2011-06-28 9:29 ` Richard Earnshaw
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='BANLkTik0AQksV2-Ue=WQqahzfo=pv080QA@mail.gmail.com' \
--to=michael.hope@linaro.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=ramana.radhakrishnan@arm.com \
--cc=richard.earnshaw@arm.com \
--cc=rth@twiddle.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).