From: Jeff Law <jeffreyalaw@gmail.com>
To: Kito Cheng <kito.cheng@gmail.com>, Romain Naour <romain.naour@gmail.com>
Cc: gcc-patches@gcc.gnu.org, kito.cheng@sifive.com, juzhe.zhong@rivai.ai
Subject: Re: [PATCH] RISC-V: fix build issue with gcc 4.9.x
Date: Tue, 2 May 2023 09:44:38 -0600 [thread overview]
Message-ID: <e0038f52-9ab0-f904-cf11-8b025dd39c88@gmail.com> (raw)
In-Reply-To: <CA+yXCZAFf8_F8V8Xm+cXTmUXzKbzwzWC_y4Rk8DRAFCG6vdr4A@mail.gmail.com>
On 5/2/23 08:31, Kito Cheng via Gcc-patches wrote:
> Hi Romain:
>
> Pushed to trunk, thanks for catching that, that's definitely should
> use log2 no matter C++03 or C++11,
> but I think GCC allows the usage of C++11 according to
> https://gcc.gnu.org/install/prerequisites.html :P
Yes, we should be able to use C++11. I'd like to get that to C++17 at
some point, but I think the biggest problem is the desire to support
bootstrapping on something like centos7/rhel7.
jeff
next prev parent reply other threads:[~2023-05-02 15:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-02 12:21 Romain Naour
2023-05-02 14:31 ` Kito Cheng
2023-05-02 15:44 ` Jeff Law [this message]
2023-05-02 15:51 ` Kito Cheng
2023-05-02 20:46 ` Romain Naour
2023-05-03 0:37 ` Kito Cheng
2023-05-03 0:47 ` Andrew Pinski
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=e0038f52-9ab0-f904-cf11-8b025dd39c88@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=juzhe.zhong@rivai.ai \
--cc=kito.cheng@gmail.com \
--cc=kito.cheng@sifive.com \
--cc=romain.naour@gmail.com \
/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).