public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Iain D Sandoe <iains@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r11-11390] testsuite, Objective-C: Fix duplicate libobjc cases. Date: Sun, 28 Apr 2024 14:39:28 +0000 (GMT) [thread overview] Message-ID: <20240428143928.9F0573858D20@sourceware.org> (raw) https://gcc.gnu.org/g:e07bed1e7f67aebc288e8e220402b6d628d4b443 commit r11-11390-ge07bed1e7f67aebc288e8e220402b6d628d4b443 Author: Iain Sandoe <iain@sandoe.co.uk> Date: Thu Jan 25 20:17:42 2024 +0000 testsuite, Objective-C: Fix duplicate libobjc cases. Two of the encode testcases include '-lobjc' as their dg-options. Since the library is already appended as part of the generic testsuite handling, this means that two instances appear on the link line leading to spurious warnings from Darwin's new linker. gcc/testsuite/ChangeLog: * obj-c++.dg/encode-10.mm: Remove unneeded '-lobjc' option addition. * obj-c++.dg/encode-9.mm: Likewise. Signed-off-by: Iain Sandoe <iain@sandoe.co.uk> (cherry picked from commit 30d9e81c19d69e15b2e9c53e4377879cbf9b0b84) Diff: --- gcc/testsuite/obj-c++.dg/encode-10.mm | 1 - gcc/testsuite/obj-c++.dg/encode-9.mm | 1 - 2 files changed, 2 deletions(-) diff --git a/gcc/testsuite/obj-c++.dg/encode-10.mm b/gcc/testsuite/obj-c++.dg/encode-10.mm index 2b3af88dcb1..2477400b7f3 100644 --- a/gcc/testsuite/obj-c++.dg/encode-10.mm +++ b/gcc/testsuite/obj-c++.dg/encode-10.mm @@ -1,5 +1,4 @@ /* Test for @encode in templates. */ -/* { dg-options "-lobjc" } */ /* { dg-do run } */ #include <string.h> #include <stdlib.h> diff --git a/gcc/testsuite/obj-c++.dg/encode-9.mm b/gcc/testsuite/obj-c++.dg/encode-9.mm index 6b064dfdc09..4fdb5fa50fb 100644 --- a/gcc/testsuite/obj-c++.dg/encode-9.mm +++ b/gcc/testsuite/obj-c++.dg/encode-9.mm @@ -1,5 +1,4 @@ /* Test than @encode is properly instantiated. */ -/* { dg-options "-lobjc" } */ /* { dg-do run } */ #include <string.h>
reply other threads:[~2024-04-28 14:39 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20240428143928.9F0573858D20@sourceware.org \ --to=iains@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: linkBe 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).