public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Earnshaw <rearnsha@arm.com>
To: Zhenqiang Chen <zhenqiang.chen@arm.com>,
	 "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: Ramana Radhakrishnan <Ramana.Radhakrishnan@arm.com>
Subject: Re: [PATCH, testsuite, ARM] Check lr other than r3
Date: Fri, 07 Nov 2014 12:51:00 -0000	[thread overview]
Message-ID: <545CC031.50400@arm.com> (raw)
In-Reply-To: <000001cff73e$b36f90e0$1a4eb2a0$@arm.com>

On 03/11/14 08:18, Zhenqiang Chen wrote:
> Hi,
> 
> pr45701-1.c FAIL for all tests. The patch updates it to check lr other than
> r3, based on the comments in arm_compute_save_reg_mask,
> 
>   /* ...
>      Otherwise if we do not use the link register we do not need to save
>      it.  If we are pushing other registers onto the stack however, we
>      can save an instruction in the epilogue by pushing the link register
>      now and then popping it back into the PC.  This incurs extra memory
>      accesses though, so we only do it when optimizing for size, and only
>      if we know that we will not need a fancy return sequence.  */
> 
> The updated case PASS for Cortex-M0/M4 and Cortext-A15 (THUMB and ARM
> modes).
> 
> OK for trunk?
> 
> Thanks!
> -Zhenqiang
> 
> testsuite/ChangeLog:
> 2014-11-03  Zhenqiang Chen  <zhenqiang.chen@arm.com>
> 
> 	* gcc.target/arm/pr45701-1.c: Check LR used.

Have you checked that this doesn't cause regressions on ARMv4T?  I
suspect the code was originally intended to support targets where
interworking was not trivial.

R.

> 
> diff --git a/gcc/testsuite/gcc.target/arm/pr45701-1.c
> b/gcc/testsuite/gcc.target/arm/pr45701-1.c
> index 2c690d5..c087cfc 100644
> --- a/gcc/testsuite/gcc.target/arm/pr45701-1.c
> +++ b/gcc/testsuite/gcc.target/arm/pr45701-1.c
> @@ -1,7 +1,7 @@
>  /* { dg-do compile } */
>  /* { dg-skip-if "" { ! { arm_thumb1_ok || arm_thumb2_ok } } } */
>  /* { dg-options "-mthumb -Os" }  */
> -/* { dg-final { scan-assembler "push\t\{r3" } } */
> +/* { dg-final { scan-assembler "lr\}" } } */
>  /* { dg-final { scan-assembler-not "r8" } } */
>  
>  extern int hist_verify;
> 
> 
> 
> 
> 
> 


  reply	other threads:[~2014-11-07 12:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-03  8:18 Zhenqiang Chen
2014-11-07 12:51 ` Richard Earnshaw [this message]
2014-11-12  8:25   ` Zhenqiang Chen

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=545CC031.50400@arm.com \
    --to=rearnsha@arm.com \
    --cc=Ramana.Radhakrishnan@arm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=zhenqiang.chen@arm.com \
    /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).