From: Bernd Edlinger <bernd.edlinger@hotmail.de>
To: Simon Marchi <simon.marchi@polymtl.ca>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
Luis Machado <luis.machado@linaro.org>
Subject: Re: [PATCH] Fix building gdb with gcc-4.x
Date: Thu, 14 Jan 2021 07:36:46 +0100 [thread overview]
Message-ID: <AM0PR0602MB3410A4B187BE6D4799E304F9E4A80@AM0PR0602MB3410.eurprd06.prod.outlook.com> (raw)
In-Reply-To: <13ad5646-78f6-27dc-2e26-f250bb4b8c52@polymtl.ca>
[-- Attachment #1: Type: text/plain, Size: 1478 bytes --]
On 1/4/21 10:30 PM, Simon Marchi wrote:
> On 2021-01-04 3:57 p.m., Bernd Edlinger wrote:
>> Hi,
>>
>> with Luis' commit of today the trunk is no longer able to
>> be compiled with gcc-4.x.
>>
>> The problem is std::is_trivially_default_constructible is
>> not defined before gcc-5 although the compiler supports C++11
>>
>> I am not sure about what's the best approach for conditionally
>> enabling the code, especially for compilers other than g++.
>>
>>
>> This fixes the build for me.
>> Is it OK for trunk?
>>
>>
>> Thanks
>> Bernd.
>>
>
> We have other instances of this, I'd suggest inspiring yourself from:
>
> https://sourceware.org/git/?p=binutils-gdb.git;a=blob;f=gdb/unittests/enum-flags-selftests.c;h=e3b6cf81d07f1eaefec72bce131d1c75ce00ef82;hb=HEAD#l66
>
> These defines are defined here:
>
> https://sourceware.org/git/?p=binutils-gdb.git;a=blob;f=gdbsupport/traits.h;h=f545edbb0d93e95f65e954fbf54cbc8843e5239a;hb=HEAD#l28
>
> As you see, we already have a HAVE_IS_TRIVIALLY_CONSTRUCTIBLE, we could
> use it. The code in trad-frame.c could be changed to use
> std::is_trivially_constructible instead of
> std::is_trivially_default_constructible, I believe it's the same when
> passing no Args... to is_trivially_constructible. See "Possible
> implementation" in:
>
> https://en.cppreference.com/w/cpp/types/is_default_constructible
>
> Simon
>
Okay, good point.
I updated the patch following your suggestion.
Is the updated patch OK?
Thanks
Bernd.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-Fix-building-gdb-with-gcc-4.x.patch --]
[-- Type: text/x-patch; name="0001-Fix-building-gdb-with-gcc-4.x.patch", Size: 2005 bytes --]
From 588e7a57056e8aabdd6906993dd3d27354cc70fc Mon Sep 17 00:00:00 2001
From: Bernd Edlinger <bernd.edlinger@hotmail.de>
Date: Mon, 4 Jan 2021 21:40:41 +0100
Subject: [PATCH] Fix building gdb with gcc-4.x
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Since is_trivially_default_constructible was not implemented before gcc-5
it cannot be used with gcc-4.x.
../../binutils-gdb/gdb/trad-frame.c: In function ‘trad_frame_saved_reg* trad_frame_alloc_saved_regs(gdbarch*)’:
../../binutils-gdb/gdb/trad-frame.c:64:22: error: ‘is_trivially_default_constructible’ is not a member of ‘std’
gdb_static_assert (std::is_trivially_default_constructible<trad_frame_saved_reg>::value);
Fix the build by using conditional compilation around that line.
Use the equivalent is_trivially_constructible<T> instead, since
we already have HAVE_IS_TRIVIALLY_CONSTRUCTIBLE for that purpose.
Fixes: 098caef485a ("Refactor struct trad_frame_saved_regs")
gdb:
2021-01-14 Bernd Edlinger <bernd.edlinger@hotmail.de>
* trad-frame.c (trad_frame_alloc_saved_regs): Avoid compile-error
because is_trivially_default_constructible was first implemented with
gcc-5.
---
gdb/trad-frame.c | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/gdb/trad-frame.c b/gdb/trad-frame.c
index 17375e8..3284c45 100644
--- a/gdb/trad-frame.c
+++ b/gdb/trad-frame.c
@@ -25,6 +25,7 @@
#include "target.h"
#include "value.h"
#include "gdbarch.h"
+#include "gdbsupport/traits.h"
struct trad_frame_cache
{
@@ -60,7 +61,9 @@ struct trad_frame_cache *
trad_frame_saved_reg *
trad_frame_alloc_saved_regs (struct gdbarch *gdbarch)
{
- gdb_static_assert (std::is_trivially_default_constructible<trad_frame_saved_reg>::value);
+#ifdef HAVE_IS_TRIVIALLY_CONSTRUCTIBLE
+ gdb_static_assert (std::is_trivially_constructible<trad_frame_saved_reg>::value);
+#endif
int numregs = gdbarch_num_cooked_regs (gdbarch);
trad_frame_saved_reg *this_saved_regs
--
1.9.1
next prev parent reply other threads:[~2021-01-14 6:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-04 20:57 Bernd Edlinger
2021-01-04 21:16 ` Luis Machado via Gdb-patches
2021-01-04 21:34 ` Luis Machado via Gdb-patches
2021-01-04 21:30 ` Simon Marchi via Gdb-patches
2021-01-14 6:36 ` Bernd Edlinger [this message]
2021-01-14 15:56 ` Simon Marchi via Gdb-patches
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=AM0PR0602MB3410A4B187BE6D4799E304F9E4A80@AM0PR0602MB3410.eurprd06.prod.outlook.com \
--to=bernd.edlinger@hotmail.de \
--cc=gdb-patches@sourceware.org \
--cc=luis.machado@linaro.org \
--cc=simon.marchi@polymtl.ca \
/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