public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: gdb-buildbot@sergiodj.net
To: gdb-testers@sourceware.org
Subject: [binutils-gdb] [gdb/testsuite] Don't use O2 for inlining in break-inline-psymtab.exp
Date: Mon, 20 Apr 2020 13:52:27 -0400	[thread overview]
Message-ID: <880d97770b63eb722d53b3a0ae2f03deae0c9c72@gdb-build> (raw)

*** TEST RESULTS FOR COMMIT 880d97770b63eb722d53b3a0ae2f03deae0c9c72 ***

commit 880d97770b63eb722d53b3a0ae2f03deae0c9c72
Author:     Tom de Vries <tdevries@suse.de>
AuthorDate: Thu Apr 2 17:12:49 2020 +0200
Commit:     Tom de Vries <tdevries@suse.de>
CommitDate: Thu Apr 2 17:12:49 2020 +0200

    [gdb/testsuite] Don't use O2 for inlining in break-inline-psymtab.exp
    
    In test-case gdb.dwarf2/break-inline-psymtab.exp we use O2 to enable inlining
    of bar into foo in break-inline-psymtab-2.c.
    
    Instead, enforce inlining using __attribute__((always_inline)), to avoid any
    optimization-related test issues.
    
    Tested on x86_64-linux.
    
    gdb/testsuite/ChangeLog:
    
    2020-04-02  Tom de Vries  <tdevries@suse.de>
    
            * gdb.dwarf2/break-inline-psymtab-2.c (bar): Add
            __attribute__((always_inline)).
            * gdb.dwarf2/break-inline-psymtab.exp: Don't use -O2.

diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog
index 99813054d5..d662727ac5 100644
--- a/gdb/testsuite/ChangeLog
+++ b/gdb/testsuite/ChangeLog
@@ -1,3 +1,9 @@
+2020-04-02  Tom de Vries  <tdevries@suse.de>
+
+	* gdb.dwarf2/break-inline-psymtab-2.c (bar): Add
+	__attribute__((always_inline)).
+	* gdb.dwarf2/break-inline-psymtab.exp: Don't use -O2.
+
 2020-04-02  Tom de Vries  <tdevries@suse.de>
 
 	* lib/gdbserver-support.exp (gdbserver_exit): Factor out of ...
diff --git a/gdb/testsuite/gdb.dwarf2/break-inline-psymtab-2.c b/gdb/testsuite/gdb.dwarf2/break-inline-psymtab-2.c
index 38c69336f2..b7fe485b3a 100644
--- a/gdb/testsuite/gdb.dwarf2/break-inline-psymtab-2.c
+++ b/gdb/testsuite/gdb.dwarf2/break-inline-psymtab-2.c
@@ -19,7 +19,7 @@ extern int foo (void);
 
 int a;
 
-static inline int
+static inline int __attribute__((always_inline))
 bar (void)
 {
   a = 2;
diff --git a/gdb/testsuite/gdb.dwarf2/break-inline-psymtab.exp b/gdb/testsuite/gdb.dwarf2/break-inline-psymtab.exp
index adbe8620aa..344d7da0d5 100644
--- a/gdb/testsuite/gdb.dwarf2/break-inline-psymtab.exp
+++ b/gdb/testsuite/gdb.dwarf2/break-inline-psymtab.exp
@@ -16,8 +16,7 @@
 standard_testfile break-inline-psymtab.c break-inline-psymtab-2.c
 
 set sources [list $srcfile $srcfile2]
-set opts {debug optimize=-O2}
-if { [prepare_for_testing "failed to prepare" ${testfile} $sources $opts] } {
+if { [prepare_for_testing "failed to prepare" ${testfile} $sources] } {
     return -1
 }
 


             reply	other threads:[~2020-04-20 17:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-20 17:52 gdb-buildbot [this message]
2020-04-20 17:52 ` Failures on Fedora-i686, branch master gdb-buildbot
2020-04-20 18:23 ` Failures on Fedora-x86_64-cc-with-index, " gdb-buildbot
2020-04-20 18:40 ` Failures on Fedora-x86_64-m32, " gdb-buildbot
2020-04-20 19:13 ` Failures on Fedora-x86_64-m64, " gdb-buildbot
2020-04-20 19:41 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " gdb-buildbot
2020-04-20 20:13 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " gdb-buildbot
2020-04-21 23:44 ` Failures on Fedora-x86_64-native-gdbserver-m32, " gdb-buildbot
2020-04-22 18:20 ` Failures on Fedora-x86_64-native-gdbserver-m64, " gdb-buildbot

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=880d97770b63eb722d53b3a0ae2f03deae0c9c72@gdb-build \
    --to=gdb-buildbot@sergiodj.net \
    --cc=gdb-testers@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).