From: Alan Modra <amodra@sourceware.org>
To: bfd-cvs@sourceware.org
Subject: [binutils-gdb] lto test fails with -fno-inline in CFLAGS
Date: Fri, 23 Jun 2023 11:33:14 +0000 (GMT) [thread overview]
Message-ID: <20230623113314.C6AFA3858404@sourceware.org> (raw)
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=0ec2cde4f48fbe19c72d0963101888743015041e
commit 0ec2cde4f48fbe19c72d0963101888743015041e
Author: Alan Modra <amodra@gmail.com>
Date: Fri Jun 23 11:36:13 2023 +0930
lto test fails with -fno-inline in CFLAGS
Putting -fno-inline in CFLAGS results in these failures.
FAIL: Build liblto-17b.so 1
FAIL: PR ld/12365
FAIL: PR ld/13183
* ld-plugin/lto.exp: Add -finline to compiler flags in some tests.
Diff:
---
ld/testsuite/ld-plugin/lto.exp | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/ld/testsuite/ld-plugin/lto.exp b/ld/testsuite/ld-plugin/lto.exp
index e7e7952bb1b..9a11de315b8 100644
--- a/ld/testsuite/ld-plugin/lto.exp
+++ b/ld/testsuite/ld-plugin/lto.exp
@@ -79,7 +79,7 @@ set lto_link_tests [list \
"" "-flto $lto_fat" \
{lto-5b.c} {} ""] \
[list "Compile PR ld/12365" \
- "" "-flto -O2 $lto_fat" \
+ "" "-flto -O2 $lto_fat -finline" \
{pr12365a.c pr12365b.c pr12365c.c} {} ""] \
[list "Compile 9" \
"" "-O2 -finline -flto" \
@@ -131,10 +131,10 @@ set lto_link_tests [list \
"$NOSANITIZE_CFLAGS" \
{dummy.c} {} "pr12758.exe"] \
[list "Build libpr13183.a" \
- "-T" "-flto -O2 $lto_fat" \
+ "-T" "-flto -O2 $lto_fat -finline" \
{pr13183a.c} {} "libpr13183.a"] \
[list "Compile PR ld/13183" \
- "" "-flto -O2" \
+ "" "-flto -O2 -finline" \
{pr13183b.c} {} ""] \
[list "Compile PR ld/13201" \
"" "-flto -O2" \
@@ -288,10 +288,10 @@ set lto_link_elf_tests [list \
"-shared" "-O2 -fpic" \
{lto-7d.c} {} "liblto-7.so" "c"] \
[list "Build liblto-17a.so" \
- "-shared -O2 -fpic -flto -fuse-linker-plugin" "-O2 -fpic -flto" \
+ "-shared -O2 -fpic -flto -fuse-linker-plugin" "-O2 -fpic -flto -finline" \
{lto-17a.c} {{"nm" {} "lto-17a.d"}} "liblto-17a.so" "c"] \
[list "Build liblto-17b.so 1" \
- "-shared -O2 -fpic -flto -fuse-linker-plugin tmpdir/lto-17a.o" "-O2 -fpic -flto" \
+ "-shared -O2 -fpic -flto -fuse-linker-plugin tmpdir/lto-17a.o" "-O2 -fpic -flto -finline" \
{lto-17b.c} {{"nm" {} "lto-17b-1.d"}} "liblto-17b.so"] \
[list "Build liblto-17b.so 2" \
"-shared -O2 -fpic -flto -fuse-linker-plugin tmpdir/lto-17a.o" "-O2 -fpic -flto" \
reply other threads:[~2023-06-23 11:33 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=20230623113314.C6AFA3858404@sourceware.org \
--to=amodra@sourceware.org \
--cc=bfd-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).