From: Bruno Larsen <blarsen@redhat.com>
To: gdb-patches@sourceware.org
Subject: [PATCH v5 4/7] gdb/testsuite: fix gdb.base/msym-bp-shl when running with Clang
Date: Wed, 14 Sep 2022 15:14:24 +0200 [thread overview]
Message-ID: <20220914131427.269689-5-blarsen@redhat.com> (raw)
In-Reply-To: <20220914131427.269689-1-blarsen@redhat.com>
When trying to test gdb.base/msym-bp-shl.exp using clang, it would have
many failures because one of the version of the foo function was being
optimized away. Adding __attribute__ ((used)) to it fixed this.
---
gdb/testsuite/gdb.base/msym-bp-shl-main-2.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gdb/testsuite/gdb.base/msym-bp-shl-main-2.c b/gdb/testsuite/gdb.base/msym-bp-shl-main-2.c
index e047ac1145a..009656fd9ea 100644
--- a/gdb/testsuite/gdb.base/msym-bp-shl-main-2.c
+++ b/gdb/testsuite/gdb.base/msym-bp-shl-main-2.c
@@ -15,7 +15,7 @@
You should have received a copy of the GNU General Public License
along with this program. If not, see <http://www.gnu.org/licenses/>. */
-static void
+static void __attribute__ ((used))
foo (void)
{
}
--
2.37.3
next prev parent reply other threads:[~2022-09-14 13:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-14 13:14 [PATCH v5 0/7] Clean gdb.base when testing with clang Bruno Larsen
2022-09-14 13:14 ` [PATCH v5 1/7] gdb/testsuite: Add a proc to test where compiler links the epilogue Bruno Larsen
2022-09-14 13:14 ` [PATCH v5 2/7] Change gdb.base/skip-solib.exp deal with lack of epilogue information Bruno Larsen
2022-09-14 13:14 ` [PATCH v5 3/7] gdb/testsuite: fix testing gdb.base/skip-inline.exp with clang Bruno Larsen
2022-09-14 13:14 ` Bruno Larsen [this message]
2022-09-14 13:14 ` [PATCH v5 5/7] fix gdb.base/jit-elf.exp when testing " Bruno Larsen
2022-09-14 13:14 ` [PATCH v5 6/7] gdb.base/skip.exp: Use finish to exit functions Bruno Larsen
2022-09-14 13:14 ` [PATCH v5 7/7] gdb/testsuite: Add test to step through function epilogue Bruno Larsen
2022-09-21 16:05 ` [PATCH v5 0/7] Clean gdb.base when testing with clang Tom Tromey
2022-09-22 9:05 ` Bruno Larsen
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=20220914131427.269689-5-blarsen@redhat.com \
--to=blarsen@redhat.com \
--cc=gdb-patches@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).