From: FX Coudert <fxcoudert@gmail.com>
To: gcc-patches@gcc.gnu.org
Cc: marxin@gcc.gnu.org
Subject: [PATCH] Testsuite: mark IPA test as requiring alias support
Date: Sun, 20 Aug 2023 14:15:31 +0200 [thread overview]
Message-ID: <FF7B03B3-51C8-4122-9C65-4B71D087756A@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 204 bytes --]
Hi,
The fact that this test needs alias support was indicated in https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85656 but never committed. Without it, the test fails on darwin.
OK to commit?
FX
[-- Attachment #2: 0001-Testsuite-mark-IPA-test-as-requiring-alias-support.patch --]
[-- Type: application/octet-stream, Size: 1035 bytes --]
From a9f67235ee5f7e08cd13dfebaa4715b19df911ca Mon Sep 17 00:00:00 2001
From: Francois-Xavier Coudert <fxcoudert@gmail.com>
Date: Sun, 20 Aug 2023 14:13:22 +0200
Subject: [PATCH] Testsuite: mark IPA test as requiring alias support
This was indicated in https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85656
but never committed. Without it, the test fails on darwin.
gcc/testsuite/ChangeLog:
* gcc.dg/ipa/ipa-icf-38.c: Require alias support.
---
gcc/testsuite/gcc.dg/ipa/ipa-icf-38.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/gcc/testsuite/gcc.dg/ipa/ipa-icf-38.c b/gcc/testsuite/gcc.dg/ipa/ipa-icf-38.c
index 452e1b88514..57c5262dd4a 100644
--- a/gcc/testsuite/gcc.dg/ipa/ipa-icf-38.c
+++ b/gcc/testsuite/gcc.dg/ipa/ipa-icf-38.c
@@ -1,4 +1,5 @@
/* { dg-do link } */
+/* { dg-require-alias "" } */
/* { dg-options "-O2 -fdump-ipa-icf-optimized -flto -fdump-tree-optimized" } */
/* { dg-require-effective-target lto } */
/* { dg-additional-sources "ipa-icf-38a.c" }*/
--
2.39.2 (Apple Git-143)
next reply other threads:[~2023-08-20 12:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-20 12:15 FX Coudert [this message]
2023-08-20 13:55 ` Iain Sandoe
2023-08-20 17:42 ` FX Coudert
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=FF7B03B3-51C8-4122-9C65-4B71D087756A@gmail.com \
--to=fxcoudert@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=marxin@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).