From: Tom de Vries via Gdb-patches <gdb-patches@sourceware.org>
To: gdb-patches@sourceware.org
Subject: [PATCH][gdb/testsuite] Fix gdb.cp/align.exp with gcc 12.1 / 11.3
Date: Mon, 2 May 2022 17:08:48 +0200 [thread overview]
Message-ID: <20220502150847.GA12665@delia.home> (raw)
Hi,
Starting with gcc 12.1 / gcc 11.3, for test-case gdb.cp/align.exp we run into:
...
align.cc:29:23: error: invalid application of 'alignof' to a void type^M
29 | unsigned a_void = alignof (void);^M
| ^~~~~~~~~~~~~~^M
...
Fix this by using __alignof__ instead.
Tested on x86_64-linux, with gcc 7.5.0, gcc 12.1 and clang 12.0.1.
Any comments?
Thanks,
- Tom
[gdb/testsuite] Fix gdb.cp/align.exp with gcc 12.1 / 11.3
---
gdb/testsuite/gdb.cp/align.exp | 25 ++++++++++++++-----------
1 file changed, 14 insertions(+), 11 deletions(-)
diff --git a/gdb/testsuite/gdb.cp/align.exp b/gdb/testsuite/gdb.cp/align.exp
index 6cda04798e8..018a297cde9 100644
--- a/gdb/testsuite/gdb.cp/align.exp
+++ b/gdb/testsuite/gdb.cp/align.exp
@@ -80,8 +80,19 @@ puts $outfile {
unsigned a_int3 = alignof (int[3]);
-#if !defined (__clang__)
- unsigned a_void = alignof (void);
+#if defined __GNUC__ && !defined __clang__
+ /* As a GNU C extension, GCC allows void pointer arithmetic, with
+ sizeof (void) == 1.
+ Another GNU C extension is __alignof__, which can be used to get
+ __alignof__ (void), which is also 1. This is unavailabe on clang.
+ GCC used to only warn for alignof (void), but starting with GCC 12.1,
+ as well as GCC 11.3, it will generate an error (note that using
+ -std=gnu++11 does not prevent the error).
+ So we avoid using alignof, and use __alignof__ instead. */
+ unsigned a_void = __alignof__ (void);
+#else
+ /* No support for __alignof__ (void), hardcode value. */
+ unsigned a_void = 1;
#endif
struct base { char c; };
@@ -173,13 +184,5 @@ foreach type $typelist {
set expected [get_integer_valueof a_int3 0]
gdb_test "print alignof(int\[3\])" " = $expected"
-# As an extension, GCC allows void pointer arithmetic, with
-# sizeof(void) and alignof(void) both 1. This test checks
-# GDB's support of GCC's extension.
-if [test_compiler_info clang*] {
- # Clang doesn't support GCC's extension.
- set expected 1
-} else {
- set expected [get_integer_valueof a_void 0]
-}
+set expected [get_integer_valueof a_void 0]
gdb_test "print alignof(void)" " = $expected"
next reply other threads:[~2022-05-02 15:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 15:08 Tom de Vries via Gdb-patches [this message]
2022-05-02 16:43 ` Tom Tromey
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=20220502150847.GA12665@delia.home \
--to=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/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