public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc(refs/users/aoliva/heads/testme)] aarch64: testsuite: symbol-range compile only
Date: Tue, 21 Jun 2022 00:08:05 +0000 (GMT)	[thread overview]
Message-ID: <20220621000805.EF83C38418B1@sourceware.org> (raw)

https://gcc.gnu.org/g:e1cef6c8085ca460aa4757740a7fb6d4bc25bdf7

commit e1cef6c8085ca460aa4757740a7fb6d4bc25bdf7
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Mon Jun 20 19:43:45 2022 -0300

    aarch64: testsuite: symbol-range compile only
    
    On some of our embedded aarch64 targets, RAM size is too small for
    this test to fit.  It doesn't look like this test requires linking,
    and if it does, the -tiny version may presumably get most of the
    coverage without going overboard in target system requirements.
    
    
    for  gcc/testsuite/ChangeLog
    
            * gcc.target/aarch64/symbol-range.c: Compile only.
    
    TN: V527-021

Diff:
---
 gcc/testsuite/gcc.target/aarch64/symbol-range.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/testsuite/gcc.target/aarch64/symbol-range.c b/gcc/testsuite/gcc.target/aarch64/symbol-range.c
index d8e82fa1b28..cc68c19ca85 100644
--- a/gcc/testsuite/gcc.target/aarch64/symbol-range.c
+++ b/gcc/testsuite/gcc.target/aarch64/symbol-range.c
@@ -1,4 +1,4 @@
-/* { dg-do link } */
+/* { dg-do compile } */
 /* { dg-options "-O3 -save-temps -mcmodel=small" } */
 
 char fixed_regs[0x80000000];


             reply	other threads:[~2022-06-21  0:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-21  0:08 Alexandre Oliva [this message]
2022-06-21  0:15 Alexandre Oliva

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=20220621000805.EF83C38418B1@sourceware.org \
    --to=aoliva@gcc.gnu.org \
    --cc=gcc-cvs@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).