public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tejas Belagod <tbelagod@arm.com>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: [Patch, AArch64]: Fix test harness to for unaligned vector mem access.
Date: Wed, 19 Dec 2012 14:47:00 -0000	[thread overview]
Message-ID: <50D1D38C.7010205@arm.com> (raw)

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


Hi,

Currently on the trunk, we have many vect tests that fail for aarch64-*-*
because check_effective_target_vect_no_align () in target-supports.exp returns
true for aarch64 where in fact it should be returning false. This causes the
tests that check for vect_no_align and expect messages for loop versioning to
fail. The attached patch drops aarch64 from the list of targets in
check_effective_target_vect_no_align () as unaligned access is supported.

Tested on trunk for aarch64-none-elf with no regressions. OK for trunk?

Thanks,
Tejas Belagod
ARM.

Changelog:

2012-12-19  Tejas Belagod  <tejas.belagod@arm.com>

testsuite/
	* lib/target-supports.exp
	(check_effective_target_vect_no_align): Remove aarch64 from list of
	targets.

[-- Attachment #2: vect-no-align-2.txt --]
[-- Type: text/plain, Size: 556 bytes --]

diff --git a/gcc/testsuite/lib/target-supports.exp b/gcc/testsuite/lib/target-supports.exp
index e541c12..c20ec5e 100644
--- a/gcc/testsuite/lib/target-supports.exp
+++ b/gcc/testsuite/lib/target-supports.exp
@@ -3488,7 +3488,6 @@ proc check_effective_target_vect_no_align { } {
 	if { [istarget mipsisa64*-*-*]
 	     || [istarget sparc*-*-*]
 	     || [istarget ia64-*-*]
-	     || [istarget aarch64-*-*]
 	     || [check_effective_target_arm_vect_no_misalign]
 	     || ([istarget mips*-*-*]
 		 && [check_effective_target_mips_loongson]) } {

             reply	other threads:[~2012-12-19 14:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-19 14:47 Tejas Belagod [this message]
2012-12-19 14:55 ` 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=50D1D38C.7010205@arm.com \
    --to=tbelagod@arm.com \
    --cc=gcc-patches@gcc.gnu.org \
    /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).