public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tom de Vries <vries@codesourcery.com>
To: Richard Earnshaw <rearnsha@arm.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH, PR43920, 2/9] ARM specific part - test case
Date: Fri, 01 Apr 2011 16:10:00 -0000	[thread overview]
Message-ID: <4D95F905.6010901@codesourcery.com> (raw)
In-Reply-To: <1301672077.4104.15.camel@e102346-lin.cambridge.arm.com>

[-- Attachment #1: Type: text/plain, Size: 418 bytes --]

On 04/01/2011 05:34 PM, Richard Earnshaw wrote:
> On Fri, 2011-04-01 at 16:47 +0200, Tom de Vries wrote:
>> Reposting, with ChangeLog.
> 
> +/* { dg-options "-march=armv7-a -mthumb -Os" } */
> 
> No, use dg-require-effective-target.  The above doesn't work properly
> with multilib testing.
> 

Changed it into:

+/* { dg-options "-mthumb -Os" }  */
+/* { dg-require-effective-target arm_thumb2_ok } */

Thanks,
- Tom

[-- Attachment #2: 2_arm-size-branch_cost.test.patch --]
[-- Type: text/x-patch, Size: 807 bytes --]

2011-04-01  Tom de Vries  <tom@codesourcery.com>

	PR target/43920
	* gcc.target/arm/pr43920-1.c: New test.

Index: gcc/testsuite/gcc.target/arm/pr43920-1.c
===================================================================
--- gcc/testsuite/gcc.target/arm/pr43920-1.c	(revision 0)
+++ gcc/testsuite/gcc.target/arm/pr43920-1.c	(revision 0)
@@ -0,0 +1,21 @@
+/* { dg-do compile } */
+/* { dg-options "-mthumb -Os" }  */
+/* { dg-require-effective-target arm_thumb2_ok } */
+
+int
+f (int start, int end, int *start_)
+{
+  if (start == -1 || end == -1)
+    return -1;
+
+  if (end - start)
+    return -1;
+
+  *start_ = start;
+
+  return 0;
+}
+
+/* { dg-final { scan-assembler-times "\torr" 0 } } */
+/* { dg-final { scan-assembler-times "\tit\t" 0 } } */
+/* { dg-final { scan-assembler "\tbeq" } } */

  reply	other threads:[~2011-04-01 16:10 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-31 18:27 [PATCH, PR43920] Improve code-size optimizations Tom de Vries
2011-03-31 18:29 ` [PATCH, PR43920, 1/9] ARM specific part Tom de Vries
2011-04-01 14:46   ` Tom de Vries
2011-04-01 15:19     ` Richard Earnshaw
2011-04-01 16:06       ` Tom de Vries
2011-04-02  7:47         ` Richard Guenther
2011-04-02 17:06           ` Tom de Vries
2011-04-03  7:38             ` Richard Guenther
2011-04-03 17:03               ` Tom de Vries
     [not found]                 ` <BANLkTikEruAfGJ392FXtasLv6-yV2tYSRQ@mail.gmail.com>
2011-04-04 12:14                   ` Richard Guenther
2011-04-04 12:23                     ` Rainer Orth
2011-04-05 13:35                       ` Tom de Vries
2011-05-03 18:19                         ` Rainer Orth
2011-04-03 18:40               ` Mike Stump
2011-03-31 18:31 ` [PATCH, PR43920, 2/9] ARM specific part - test case Tom de Vries
2011-04-01 14:47   ` Tom de Vries
2011-04-01 15:17     ` Tom de Vries
2011-04-01 15:34     ` Richard Earnshaw
2011-04-01 16:10       ` Tom de Vries [this message]
2011-04-05 10:43         ` Tom de Vries
2011-04-05 12:20           ` Richard Earnshaw
2011-04-06 10:48           ` Ramana Radhakrishnan
2011-04-06 12:29             ` Tom de Vries
2011-03-31 18:35 ` [PATCH, PR43920, 3/9] Cleanup Tom de Vries
2011-03-31 18:43   ` Jeff Law
2011-04-01 14:48   ` Tom de Vries
2011-04-01 15:15     ` Tom de Vries
2011-04-04 18:26       ` Jeff Law
2011-03-31 18:35 ` [PATCH, PR43920, 4-9/9] Cross-jumping Tom de Vries
2011-03-31 18:36   ` [PATCH, PR43920, 4/9] Cross-jumping - Don't count use or clobber Tom de Vries
2011-03-31 18:40     ` Jeff Law
2011-03-31 19:09       ` Tom de Vries
2011-03-31 19:19         ` Jeff Law
2011-04-01 14:48     ` Tom de Vries
2011-04-04 19:11       ` Jeff Law
2011-03-31 18:42   ` [PATCH, PR43920, 5/9] Cross-jumping - Add missing use of return register Tom de Vries
2011-03-31 18:52     ` Jeff Law
2011-04-01 14:49     ` Tom de Vries
2011-04-04 19:11       ` Jeff Law
2011-03-31 18:44   ` [PATCH, PR43920, 6/9] Cross-jumping - Use reg-notes Tom de Vries
2011-03-31 18:56     ` Jeff Law
2011-03-31 21:25       ` Tom de Vries
2011-04-01 14:54         ` Tom de Vries
2011-04-04 16:14           ` Tom de Vries
2011-04-06 17:41           ` Jeff Law
2011-03-31 18:45   ` [PATCH, PR43920, 7/9] Cross-jumping - Extend search scope Tom de Vries
2011-03-31 18:58     ` Jeff Law
2011-04-05 11:44       ` Tom de Vries
2011-04-01 14:55     ` Tom de Vries
2011-04-05 21:45       ` Jeff Law
2011-03-31 18:46   ` [PATCH, PR43920, 8/9] Cross-jumping - Extend search scope - test case Tom de Vries
2011-03-31 19:00     ` Jeff Law
2011-04-01 14:56     ` Tom de Vries
2011-04-01 15:01       ` Jakub Jelinek
2011-04-01 15:18         ` Tom de Vries
2011-04-01 16:14           ` Tom de Vries
2011-04-05 21:46           ` Jeff Law
2011-03-31 18:56   ` [PATCH, PR43920, 9/9] Cross-jumping - Allow both directions Tom de Vries
2011-03-31 19:02     ` Jeff Law
2011-04-01 14:56     ` Tom de Vries
2011-04-05 21:46       ` Jeff Law
2011-03-31 21:16 ` [PATCH, PR43920] Improve code-size optimizations Eric Botcazou
2011-04-01 15:06   ` Tom de Vries
2011-04-01 16:06     ` Eric Botcazou

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=4D95F905.6010901@codesourcery.com \
    --to=vries@codesourcery.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=rearnsha@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).