public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
From: Carl Love <carll@sourceware.org>
To: gdb-cvs@sourceware.org
Subject: [binutils-gdb] Fix gdb.base/step-indirect-call-thunk.exp
Date: Wed, 13 Jul 2022 15:13:58 +0000 (GMT)	[thread overview]
Message-ID: <20220713151358.15BBE384F01E@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=43127ae5714999118898511e0ec862d892af8106

commit 43127ae5714999118898511e0ec862d892af8106
Author: Carl Love <cel@us.ibm.com>
Date:   Wed Jul 13 15:09:33 2022 +0000

    Fix gdb.base/step-indirect-call-thunk.exp
    
    Due to recent changes in the default value of -fcf-protection for gcc, the
    test gdb.base/step-indirect-call-thunk.exp fails on Intel X86-64 with the
    error:
    
    Executing on host: gcc  -fno-stack-protector  -fdiagnostics-color=never
    -mindirect-branch=thunk -mfunction-return=thunk -c -g
    -o /.../gdb/testsuite/outputs/gdb.base/step-indirect-call-thunk/step-indirect-call-thunk0.o
    /.../gdb/testsuite/gdb.base/step-indirect-call-thunk.c
    (timeout = 300) builtin_spawn -ignore SIGHUP gcc -fno-stack-protector
    -fdiagnostics-color=never -mindirect-branch=thunk -mfunction-return=thunk -c
    -g -o /.../gdb/testsuite/outputs/gdb.base/step-indirect-call-thunk/step-indirect-call-thunk0.o
    /.../binutils-gdb-current/gdb/testsuite/gdb.base/step-indirect-call-thunk.c
    /.../gdb/testsuite/gdb.base/step-indirect-call-thunk.c:
     In function 'inc': /.../gdb/testsuite/gdb.base/step-indirect-call-thunk.c:
    22:1: error: '-mindirect-branch' and '-fcf-protection' are not compatible
       22 | {                /* inc.1 */
    
    As stated in the error message the default "-fcf-protection" and
    "-mindirect-branch' are in compatible.  The fcf-protection argument needs
    to be "-fcf-protection=none" for the test to compile on Intel.
    
    The gcc command line "-mindirect-branch' is an Intel specific and will give
    an error on other platforms.  A check for X86 is added so the test will
    only run on X86 platforms.
    
    The patch has been tested and verified on Power 10 and Intel X86-64 systems
    with no regressions.

Diff:
---
 gdb/testsuite/gdb.base/step-indirect-call-thunk.exp | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/gdb/testsuite/gdb.base/step-indirect-call-thunk.exp b/gdb/testsuite/gdb.base/step-indirect-call-thunk.exp
index 761e1d9a280..7c1b53c99be 100644
--- a/gdb/testsuite/gdb.base/step-indirect-call-thunk.exp
+++ b/gdb/testsuite/gdb.base/step-indirect-call-thunk.exp
@@ -15,7 +15,11 @@
 
 standard_testfile
 
-set cflags "-mindirect-branch=thunk -mfunction-return=thunk"
+if { ![istarget "x86*"] } {
+    return
+}
+
+set cflags "-mindirect-branch=thunk -mfunction-return=thunk -fcf-protection=none"
 if { [prepare_for_testing "failed to prepare" $testfile $srcfile \
         [list debug "additional_flags=$cflags"]] } {
     return -1


                 reply	other threads:[~2022-07-13 15:13 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=20220713151358.15BBE384F01E@sourceware.org \
    --to=carll@sourceware.org \
    --cc=gdb-cvs@sourceware.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).