From: Luis Machado via Gdb-patches <gdb-patches@sourceware.org>
To: Bernd Edlinger <bernd.edlinger@hotmail.de>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
Simon Marchi <simon.marchi@polymtl.ca>
Subject: Re: [PATCH] Fix building gdb with gcc-4.x
Date: Mon, 4 Jan 2021 18:16:57 -0300 [thread overview]
Message-ID: <4c952eae-317a-bbf9-d0c9-38c4b2b3fa8c@linaro.org> (raw)
In-Reply-To: <AM0PR0602MB3410CF3FCFD75CC32A681896E4D20@AM0PR0602MB3410.eurprd06.prod.outlook.com>
Hi Bernd,
On 1/4/21 5:57 PM, 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
>
Sorry for the breakage. It looks like GCC 4.x does not fully support
C++11, although it used to be able to build GDB.
> I am not sure about what's the best approach for conditionally
> enabling the code, especially for compilers other than g++.
Right now it looks like GDB's requirement is a compiler that (fully?)
supports C++ 11. It doesn't seem to name specific minimum versions of
compilers.
With that said, I wouldn't mind a conditional in the code to support
builds with GCC 4.x, if that is deemed important. But as we start using
more and more C++ 11 constructs, breakages may happen again in the future.
>
>
> This fixes the build for me.
> Is it OK for trunk?
>
>
> Thanks
> Bernd.
>
next prev parent reply other threads:[~2021-01-04 21:17 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 [this message]
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
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=4c952eae-317a-bbf9-d0c9-38c4b2b3fa8c@linaro.org \
--to=gdb-patches@sourceware.org \
--cc=bernd.edlinger@hotmail.de \
--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