From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [committed][gdb/testsuite] Compile compile-ifunc.c with -Wno-attribute-alias
Date: Wed, 6 May 2020 05:32:05 +0200 [thread overview]
Message-ID: <f686badd-0f46-f215-af7b-5806a0ef4a3a@suse.de> (raw)
In-Reply-To: <20200501142617.GA31389@delia>
[-- Attachment #1: Type: text/plain, Size: 336 bytes --]
On 01-05-2020 16:26, Tom de Vries wrote:
> Fix the warning by compiling with -Wno-attribute-alias.
I ran into this with clang:
...
warning: unknown warning option '-Wno-attribute-alias'; did you mean^M
'-Wno-attributes'? [-Wunknown-warning-option]^M
...
So, I've limited the fix to when gcc is used.
Committed.
Thanks,
- Tom
[-- Attachment #2: 0001-gdb-testsuite-Compile-compile-ifunc.c-with-Wno-attribute-alias.patch --]
[-- Type: text/x-patch, Size: 3485 bytes --]
[gdb/testsuite] Compile compile-ifunc.c with -Wno-attribute-alias
Consider the following test-case:
...
$ cat 1.c
typedef int (*final_t) (int arg);
int final (int arg)
{ return arg + 1; }
final_t gnu_ifunc (void)
{ return final; }
int gnu_ifunc_alias (int) __attribute__ ((ifunc ("gnu_ifunc")));
int main (void)
{ return gnu_ifunc_alias (10); }
...
with result:
...
$ gcc 1.c
$ ./a.out; echo $?
11
...
The test-case uses the ifunc attribute, but there's another solution using
%gnu_indirect_function. Consider 2.c and 3.c:
...
$ cat 2.c
typedef int (*final_t) (int arg);
int final (int arg)
{ return arg + 1; }
asm (".type gnu_ifunc, %gnu_indirect_function");
final_t gnu_ifunc (void)
{ return final; }
$ cat 3.c
extern int gnu_ifunc (int);
int main (void)
{ return gnu_ifunc (10); }
...
However, it can be inconvenient to have seperate files for the incompatible
decls of gnu_ifunc, so we can use this in a single file like this:
...
$ cat 4.c
typedef int (*final_t) (int arg);
int final (int arg)
{ return arg + 1; }
asm (".type gnu_ifunc, %gnu_indirect_function");
final_t gnu_ifunc (void)
{ return final; }
extern int gnu_ifunc_alias (int arg) __attribute__ ((alias ("gnu_ifunc")));
int main (void)
{ return gnu_ifunc_alias (10); }
...
This alias trick works ok at -O0, but not at -O2:
...
$ gcc 4.c
$ ./a.out; echo $?
11
$ gcc 4.c
$ ./a.out; echo $?
176
...
and produces a warning with gcc-8 and later:
...
$ gcc-8 4.c
4.c:7:12: warning: 'gnu_ifunc_alias' alias between functions of incompatible \
types 'int(int)' and 'int (*(void))(int)' [-Wattribute-alias]
extern int gnu_ifunc_alias (int arg) __attribute__ ((alias ("gnu_ifunc")));
^~~~~~~~~~~~~~~
4.c:5:9: note: aliased declaration here
final_t gnu_ifunc (void)
^~~~~~~~~
...
The warning is correct, but the mismatch is intentional.
The last variant (%gnu_indirect_function + alias) is used in
gdb.compile/compile-ifunc.c, so we run into the warning with recent gcc.
Fix the warning by compiling with -Wno-attribute-alias.
Tested the test-case on x86_64-linux with gcc-10, and observed I no longer see
the warning:
...
Running src/gdb/testsuite/gdb.compile/compile-ifunc.exp ...
=== gdb Summary ===
nr of untested testcases 1
...
gdb/testsuite/ChangeLog:
2020-05-01 Tom de Vries <tdevries@suse.de>
* gdb.compile/compile-ifunc.exp: Use -Wno-attribute-alias.
---
gdb/testsuite/gdb.compile/compile-ifunc.exp | 12 ++++++++++--
1 file changed, 10 insertions(+), 2 deletions(-)
diff --git a/gdb/testsuite/gdb.compile/compile-ifunc.exp b/gdb/testsuite/gdb.compile/compile-ifunc.exp
index ff81e2f87aa..9239c5adf1e 100644
--- a/gdb/testsuite/gdb.compile/compile-ifunc.exp
+++ b/gdb/testsuite/gdb.compile/compile-ifunc.exp
@@ -19,9 +19,16 @@ if {[skip_ifunc_tests]} {
standard_testfile
+get_compiler_info
+set flags ""
+if [test_compiler_info gcc*] {
+ set flags additional_flags=-Wno-attribute-alias
+}
+
with_test_prefix "nodebug" {
- if { [prepare_for_testing "failed to prepare" "$testfile-nodebug" $srcfile {}] } {
+ if { [prepare_for_testing "failed to prepare" "$testfile-nodebug" \
+ $srcfile $flags] } {
return -1
}
@@ -51,7 +58,8 @@ with_test_prefix "nodebug" {
with_test_prefix "debug" {
- if { [prepare_for_testing "failed to prepare" "$testfile-debug" $srcfile] } {
+ if { [prepare_for_testing "failed to prepare" "$testfile-debug" \
+ $srcfile "debug $flags"] } {
return -1
}
prev parent reply other threads:[~2020-05-06 3:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-01 14:26 [PATCH][gdb/testsuite] " Tom de Vries
2020-05-06 3:32 ` Tom de Vries [this message]
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=f686badd-0f46-f215-af7b-5806a0ef4a3a@suse.de \
--to=tdevries@suse.de \
--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).