RISC-V has received a very nice section in the GCC 11 release notes
thanks to Kito.
This are a couple of editorial changes, completing some sentence and
breaking longer sentences among others, and a bit of grammar.
Pushed.
Gerald
---
htdocs/gcc-11/changes.html | 33 ++--
On 11.06.21 09:43, Martin Liška wrote:
I support the patch, please install it (except the not intentional change
in gcc/c/c-parser.c).
Committed as r12-1408-gd554f43c98eb07f222afef5e90b5582d65519f7e
Then, please ask Jonathan for updating of the server hook.
@Jonathan: ↑ - thanks.
Tobais
---
On Linux/x86_64,
c0f769fa3114ea852a26d93f0ee3f9595463de0b is the first bad commit
commit c0f769fa3114ea852a26d93f0ee3f9595463de0b
Author: Jason Merrill
Date: Fri Jun 11 16:10:50 2021 -0400
c-family: don't warn for [[maybe_unused]] on data member
caused
FAIL: gcc.dg/c2x-attr-maybe_unused-
The C++17 standard (and C2x) says that [[maybe_unused]] may be applied to a
non-static data member, so we shouldn't warn about it. And I don't see a
reason not to handle a FIELD_DECL the same as any other decl, by setting
TREE_USED on it. It doesn't look like anything yet cares about that flag on
build_vec_init_elt exits early if we're initializing a zero-element array,
so build_vec_init needs to do the same to avoid trying to instantiate things
after we've already started throwing important bits away.
Tested x86_64-pc-linux-gnu, applying to trunk.
PR c++/101029
gcc/cp/ChangeLog:
Hi, all.
Please CC me when I am mentioned into a mail.
On Thu, 2021-05-20 at 15:16 +0200, Richard Biener via Gcc wrote:
> On Thu, May 20, 2021 at 3:06 PM Martin Liška wrote:
> >
> > On 5/20/21 2:54 PM, Richard Biener wrote:
> > > So why did you go from applying this per-file to multiple files?
On Fri, Jun 11, 2021 at 08:45:53PM +0800, Kewen.Lin wrote:
> on 2021/6/10 下午6:58, Segher Boessenkool wrote:
> > On Thu, Jun 10, 2021 at 05:32:23PM +0800, Kewen.Lin wrote:
> >> +/* { dg-do compile { target lp64 } } */
> >
> > One final thing: what requires lp64 here? Could you try without please?
