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 r14-10024] [testsuite] [i386] require fpic for pr111497.C
Date: Thu, 18 Apr 2024 11:15:27 +0000 (GMT)	[thread overview]
Message-ID: <20240418111527.812DD384AB55@sourceware.org> (raw)

https://gcc.gnu.org/g:514c6b1cb766dc0a14121016ce84b9f5a1ef4e41

commit r14-10024-g514c6b1cb766dc0a14121016ce84b9f5a1ef4e41
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Thu Apr 18 08:01:29 2024 -0300

    [testsuite] [i386] require fpic for pr111497.C
    
    Fix another test that uses -fPIC without requiring fpic support.
    
    
    for  gcc/testsuite/ChangeLog
    
            * g++.target/i386/pr111497.C: Require fpic support.

Diff:
---
 gcc/testsuite/g++.target/i386/pr111497.C | 1 +
 1 file changed, 1 insertion(+)

diff --git a/gcc/testsuite/g++.target/i386/pr111497.C b/gcc/testsuite/g++.target/i386/pr111497.C
index a645bb95907..30e2e0409ad 100644
--- a/gcc/testsuite/g++.target/i386/pr111497.C
+++ b/gcc/testsuite/g++.target/i386/pr111497.C
@@ -1,5 +1,6 @@
 // { dg-do compile { target ia32 } }
 // { dg-options "-march=i686 -mtune=generic -fPIC -O2 -g" }
+// { dg-require-effective-target fpic }
 
 class A;
 struct B { const char *b1; int b2; };

                 reply	other threads:[~2024-04-18 11:15 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=20240418111527.812DD384AB55@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).