On Sat, Oct 24, 2020 at 12:31:43PM -0500, Segher Boessenkool wrote:
> On Sat, Oct 24, 2020 at 02:59:34PM +1030, Alan Modra wrote:
> > Those instructions aren't generated, we don't see them anywhere on a
> > power10 all-lang bootstrap except in one testcase designed to exercise
> > them.
>
> But th
On Fri, Oct 23, 2020 at 09:33:38PM -0400, Jason Merrill via Gcc-patches wrote:
> On 10/23/20 3:01 PM, Marek Polacek wrote:
> > This patch implements the -Wvexing-parse warning to warn about the
> > sneaky most vexing parse rule in C++: the cases when a declaration
> > looks like a variable definiti
Here, in r11-155, I changed the call to uses_template_parms to
type_dependent_expression_p_push to avoid a crash in C++98 in
value_dependent_expression_p on a non-constant expression. But that
prompted a host of complaints that we now warn for value-dependent
expressions in templates. Those warni
Hello world,
here's a patch which corrects some wrong declarations (and fixes
the segfault for FINDLOC on Darwin ARM).
Regression-tested. OK for trunk?
ping?
Regards
Thomas
On Sat, Oct 24, 2020 at 02:59:34PM +1030, Alan Modra wrote:
> On Fri, Oct 23, 2020 at 04:06:57PM -0500, Segher Boessenkool wrote:
> > On Fri, Oct 23, 2020 at 09:41:30AM +1030, Alan Modra wrote:
> > > On Thu, Oct 22, 2020 at 11:03:14AM -0500, Segher Boessenkool wrote:
> > > > On Thu, Oct 22, 2020 at
On Sat, Oct 24, 2020 at 6:05 PM Qing Zhao wrote:
>
> Hi,
>
> This is the 4th version of the implementation of patch -fzero-call-used-regs.
>
> The major change compared to the previous version are:
>
> 1. Documentation change per Richard’s suggestion;
> 2. Command sub options handling per Richar
Hi,
This is the 4th version of the implementation of patch -fzero-call-used-regs.
The major change compared to the previous version are:
1. Documentation change per Richard’s suggestion;
2. Command sub options handling per Richard’s suggestion;
3. I386 part, clearing ST registers per Uros’s
On Sat, Oct 24, 2020 at 08:28:08AM -0700, H.J. Lu wrote:
> The updated patch to check
>
> https://sourceware.org/bugzilla/show_bug.cgi?id=26778
>
> OK for master?
Ok, thanks.
> From 7130dea1f39692a8a00e48ef119233595f9284c9 Mon Sep 17 00:00:00 2001
> From: "H.J. Lu"
> Date: Fri, 16 Oct 2020 05:
On Sat, Oct 24, 2020 at 03:11:29AM +0300, Ville Voutilainen wrote:
> On Sat, 24 Oct 2020 at 03:07, Marek Polacek wrote:
> > > Ha, we have the same thing in is_trivially_xible, so I'll drive-by
> > > change that one as well.
> >
> > Please. Thanks!
>
> The tree is also on a separated line in is_t
Hi, Carl
Not commenting on the implementation.
Please stop using powerpc*-*-* in the test cases. The test cases
already are in the gcc.target/powerpc directory.
Do the test cases really need lp64, or should this require something
like int128?
Thanks, David
On Fri, Oct 23, 2020 at 9:56 PM Carl
On Sat, Oct 17, 2020 at 6:23 AM H.J. Lu wrote:
>
> On Fri, Oct 16, 2020 at 11:29 AM H.J. Lu wrote:
> >
> > On Fri, Oct 16, 2020 at 11:17 AM Jakub Jelinek wrote:
> > >
> > > On Fri, Oct 16, 2020 at 10:58:34AM -0700, H.J. Lu wrote:
> > > > Don't set HAVE_AS_GDWARF_5_DEBUG_FLAG nor HAVE_AS_WORKING_
Hi
Just a rebase of this patch.
François
On 17/10/20 6:21 pm, François Dumont wrote:
I eventually would like to propose the following resolution.
For multi-key containers I kept the same resolution build the node
first and compute has code from the node key.
For unique-key ones I chang
An undefined range was leaking through to the end of this function,
which leads us to use an uninitialized wide_int.
Pushed.
gcc/ChangeLog:
PR tree-optimization/97538
* calls.c (get_size_range): Handle undefined ranges.
gcc/testsuite/ChangeLog:
* g++.dg/pr97538.C: New t
13 matches
Mail list logo
