On Mon, Jul 13, 2020 at 6:46 AM Hans-Peter Nilsson wrote:
>
> > From: Richard Biener
> > Date: Tue, 7 Jul 2020 09:00:22 +0200
>
> > On Tue, Jul 7, 2020 at 6:03 AM Hans-Peter Nilsson via Gcc-patches
> > wrote:
> > >
> > > We say very little about reads and writes to aggregate /
> > > compound obj
On 2020/7/13 上午8:32, Jim Wilson wrote:
This looks like a security leak that the canary value is left in a4.
The i386 implementation operates directly on memory without loading
into registers. The rs6000 implementation is careful to load 0 into
the other register in the stack_protector_test cod
This eliminates the visited bitmap and makes whether a to be processed
block goes to the next or the current iteration only depend on its
position in RPO order rather than on whether it was visited in the
current iteration. As optimization single-BB iteration is processed
immediately.
Bootstrappe
gcc/
* config/riscv/riscv-opts.h (stack_protector_guard): New enum.
* config/riscv/riscv.c (riscv_option_override): Handle
the new options.
* config/riscv/riscv.md (stack_protect_set): New pattern to handle
flexible stack protector guard settings.
(st
Together with the combine.c patch posted (but remaining a WIP),
all coremark performance regressions are gone for CRIS, compared
to cc0. Unfortunately, I looked further, and found some issues
when running gcc.c-torture/execute/arith-rand.c and
arith-rand-ll.c, in those functions and the target-spe
Hi!
The _mm512_{,mask_}cmp_p[ds]_mask and also _mm_{,mask_}cmp_s[ds]_mask
intrinsics have an argument which must have a constant passed to it
and so use an inline version only for ifdef __OPTIMIZE__ and have
a #define for -O0. But the _mm512_{,mask_}cmp*_p[ds]_mask intrinsics
don't need a constan
Whoops. This little gem had the effect of making the output
operand (0) constraints disappear but not the input operand (1)
constraints for define_subst:ed patterns, probably because
there's another (match_dup 1) in the output template (not
investigated).
That went surprisingly unnoticed until I
Getting tired of:
make[1]: Entering directory 'x/gccobj/gcc'
Makefile:2682: warning: overriding recipe for target 'gt-cris.h'
xx/gcc/gcc/config/cris/t-cris:29: warning: ignoring old recipe for target
'gt-cris.h'
I'm just going to assume it is just stale cruft no longer (if
ever) needed since not
Comparing to the cc0 version of the CRIS port, I ran a few
microbenchmarks, for example gcc.c-torture/execute/arith-rand.c,
where there's sometimes an addition between an operation of
interest and the test on the result.
Unfortunately this patch doesn't remedy all the performance
regression for th
This is a series of patches essentially adding order statistics directly into
pb_ds binary search trees. The main purpose is to resolve PR 81806 (spliting a
splay tree needs linear time).
The first patch removes two redundant statements which are confusing. It should
be applied anyway, disregard
(All patches are committed.)
Delayed-branch-slot-filling a.k.a. reorg or dbr, often causes
opportunities for more compare-elimination than were visible for
the cmpelim pass. With cc0, these were caught by the
elimination pass run in "final", thus the missed opportunities
is a regression. A simpl
> The first patch removes two redundant statements which are confusing. It
> should
> be applied anyway, disregarding other patches.
The patch is attached, to prevent my mail client from destroying it :(.
libstdc++-v3/ChangeLog:
* include/ext/pb_ds/detail/bin_search_tree_/insert_fn_imp
*PING*
On 6/24/20 7:32 PM, Tobias Burnus wrote:
(OpenMP 5 extends this a lot, but this is about OpenMP 4.5.
It touches code which is also used by OpenACC's attach/detach.)
@OpenACC/Julian: I think the character attach/detach for
deferred-length strings does not work properly with OpenACC;
I did
> The first patch removes two redundant statements which are confusing. It
> should
> be applied anyway, disregarding other patches.
The patch is attached, to prevent my mail client from destroying it :(.
Please ignore a previous duplication of this mail with wrong title :(.
libstdc++-v3/Change
> The second and third patch together resolve PR 81806.
The attached patch keeps the subtree size in binary search tree nodes.
libstdc++-v3/ChangeLog:
* include/ext/pb_ds/detail/rb_tree_map_/node.hpp
(rb_tree_node_::size_type): New typedef.
(rb_tree_node_::m_subtree_
> The second and third patch together resolve PR 81806.
The attached patch modifies split_finish to use the subtree size we maintained
in the previous patch, resolving libstdc++/81806.
libstdc++-v3/ChangeLog:
PR libstdc++/81806
* include/ext/pb_ds/detail/bin_search_tree_/split_j
> The fourth patch converts the point_iterator of rb_tree and splay_tree based
> maps to random access iterator. With the subtree size kept we can implement
> the
> operators required by random access iterator in logarithm time.
The patch is attached.
libstdc++-v3/ChangeLog:
* include/
> The fifth patch moves the functionality of tree_order_statistics_node_update
> into the implementation of binary search trees (they are now order-statistics
> trees), makes tree_order_statistics_node_update no-op, and deprecates it.
The patch is attached.
libstdc++-v3/ChangeLog:
* inc
The testcase was errorneously accessing the global variable via a
type that might require bigger alignment than provided. Fix that
via an appropriate attribute.
2020-07-13 Richard Biener
PR testsuite/96180
* gcc.dg/torture/pr96133.c: Align global variable.
---
gcc/testsuite/g
Szabolcs Nagy writes:
> Mangling, currently only used on AArch64 for return address signing,
> is an internal representation that should not be exposed via
>
> __builtin_return_address return value,
> __builtin_eh_return handler argument,
> _Unwind_DebugHook handler argument.
>
> Note that a
Szabolcs Nagy writes:
> The expected semantics and valid usage of __builtin_return_address is
> not clear since it exposes implementation internals that are normally
> not meaningful to portable c code.
>
> This documentation change tries to clarify the semantics in case the
> return address is st
On 6/17/20 3:11 PM, Richard Biener wrote:
> On Wed, 17 Jun 2020, H.J. Lu wrote:
>
>> On Wed, Jun 17, 2020 at 5:33 AM Richard Biener wrote:
>>>
>>> On Wed, 17 Jun 2020, H.J. Lu wrote:
>>>
On Wed, Jun 17, 2020 at 5:00 AM Richard Biener wrote:
>
> On Wed, 17 Jun 2020, H.J. Lu wrote:
>>
My previous fix for PR 94749 did fix the reported case, so that the next
character is not discarded if it happens to equal the delimiter when __n
characters have already been read. But it introduced a new bug, which is
that the delimiter character would *not* be discarded if the number of
character
Hi,
For very small loops (< 6 insns), it would be fine to unroll 4
times to run fast with less latency and better cache usage. Like
below loops:
while (i) a[--i] = NULL; while (p < e) *d++ = *p++;
With this patch enhances, we could see some performance improvement
for some workloads(e.g. SPE
Hi!
On Wed, Jul 08, 2020 at 12:59:00PM -0700, Carl Love wrote:
> [PATCH 2/6] rs6000 Add vector insert builtin support
> +For little-endian,
> +the generated code will be semantically equivalent to vinsbrx, vinshrx,
> +or vinswrx instructions. Similarly for big-endian it will be semantically
> +e
The intent was that this was implied by powerpc64-unknown-linux-gnu,
but this not very obvious because of the ELFv1 vs ELFv2 ABI
differences.
---
htdocs/gcc-10/criteria.html | 1 +
htdocs/gcc-11/criteria.html | 1 +
htdocs/gcc-9/criteria.html | 1 +
3 files changed, 3 insertions(+)
diff --git a
On Thu, Jul 09, 2020 at 11:02:39AM -0500, will schmidt wrote:
> > * config/rs6000/rs6000-call.c (P10_BUILTIN_VEC_REPLACE_ELT,
> > P10_BUILTIN_VEC_REPLACE_UN): New.
>
> New what?
Just "New." is fine :-)
Segher
Change CTZ_DEFINED_VALUE_AT_ZERO/CTZ_DEFINED_VALUE_AT_ZERO to return 0/2
to enable table-based clz/ctz optimization:
-- Macro: CLZ_DEFINED_VALUE_AT_ZERO (MODE, VALUE)
-- Macro: CTZ_DEFINED_VALUE_AT_ZERO (MODE, VALUE)
A C expression that indicates whether the architecture defines a
valu
On 7/10/20 11:43 AM, Marek Polacek via Gcc-patches wrote:
Here's an interesting issue: in this code a ) is missing:
enum { E = (2 } e;
but we compile the code anyway, and E is set to 0 in build_enumerator,
which is sneaky.
The problem is that cp_parser_enum_specifier parses tentatively, bec
Hi!
On Wed, Jul 08, 2020 at 12:59:12PM -0700, Carl Love wrote:
> [PATCH 3/6] rs6000, Add vector replace builtin support
This is okay for trunk. Thanks!
Segher
This avoids placing stmts beyond the vectorizer region begin which
confuses vect_stmt_dominates_stmt_p.
Bootstrapped and tested on x86_64-unknown-linux-gnu, applied.
Richard.
2020-07-13 Richard Biener
PR tree-optimization/96163
* tree-vect-slp.c (vect_schedule_slp_instance):
Hi Richard,
> It seems to be improving TARGET_TRULY_NOOP_TRUNCATION documentation might be
> useful here.
This is an excellent suggestion. How about the following/attached:
2020-07-13 Roger Sayle
gcc/ChangeLog:
* doc/tm.texi (TARGET_TRULY_NOOP_TRUNCATION): Clarify that targets
Hi,
I please take a look at new version (attached).
Thanks,
Dmitrij
On Sat, Jul 11, 2020 at 09:39:13AM +0100, Richard Sandiford wrote:
...
> This should push “newelt” instead.
done
...
> This test is endian-agnostic and should work for all targets, but…
...
>
> …the shuffles in these tests are
pushed as obvious
turned out scan-lang-dump-not was broken in the 3 argument case -- I'd
missed a necessary empty arg. Fixed thusly.
gcc/testsuite/
* lib/scanlang.exp (scan-lang-dump-not): Fix 3-arg case.
--
Nathan Sidwell
diff --git c/gcc/testsuite/lib/scanlang.exp w
On Mon, Jul 13, 2020 at 10:08:52AM -0400, Nathan Sidwell wrote:
> On 7/10/20 11:43 AM, Marek Polacek via Gcc-patches wrote:
> > Here's an interesting issue: in this code a ) is missing:
> >
> >enum { E = (2 } e;
> >
> > but we compile the code anyway, and E is set to 0 in build_enumerator,
>
Hello
(This patch was previously posted for OG7 at:
https://gcc.gnu.org/pipermail/gcc-patches/2018-February/494594.html).
When the version of nvprof in CUDA 9.0 is run on an OpenACC program, it sets up
a callback that is called on device initialization. Inside the callback, it
calls the acc_
On Fri, Jul 10 2020, Jakub Jelinek wrote:
> Hi!
>
> The following testcase ICEs since r10-3199.
> There is a switch with default label, where the controlling expression has
> range just 0..7 and there are case labels for all those 8 values, but
> nothing has yet optimized away the default.
> Since
On Thu, Jul 9, 2020 at 6:35 AM H.J. Lu wrote:
>
> On Thu, Jul 9, 2020 at 5:04 AM Kirill Yukhin wrote:
> >
> > On 07 июл 09:06, H.J. Lu wrote:
> > > On Tue, Jul 7, 2020 at 8:56 AM Kirill Yukhin
> > > wrote:
> > > >
> > > > Hello HJ,
> > > >
> > > > On 28 июн 07:19, H.J. Lu via Gcc-patches wrote:
Hi,
Sorry for the slow review.
Przemyslaw Wirkus writes:
> Hi,
>
> Introduce simple peephole2 optimization which substitutes a sequence of
> four consecutive load or store (LDR, STR) instructions with two load or
> store pair (LDP, STP) instructions for 2 element supported vector modes
> (V2SI,
On 7/13/20 11:15 AM, Marek Polacek wrote:
On Mon, Jul 13, 2020 at 10:08:52AM -0400, Nathan Sidwell wrote:
On 7/10/20 11:43 AM, Marek Polacek via Gcc-patches wrote:
Here's an interesting issue: in this code a ) is missing:
enum { E = (2 } e;
but we compile the code anyway, and E is set to
On Sun, 2020-05-31 at 16:10 -0700, H.J. Lu via Gcc-patches wrote:
> cmpstrnsi expander may pass the actual string length directly to cmpstrnqi
> patterns. For cmpstrnsi, one of the strings must be a constant and
> expand_builtin_strncmp rewrites the length argument to be the minimum of
> the const
Somewhat improved by r11-2064, though we still generate junk that seems
redundant. But at least it says
error: expected ‘}’ before ‘.’ token
PR c++/95288
* g++.dg/diagnostic/enum2.C: New test.
---
gcc/testsuite/g++.dg/diagnostic/enum2.C | 10 ++
1 file changed, 10 inserti
On Mon, Jul 13, 2020 at 12:18:03PM -0400, Nathan Sidwell wrote:
> On 7/13/20 11:15 AM, Marek Polacek wrote:
> > On Mon, Jul 13, 2020 at 10:08:52AM -0400, Nathan Sidwell wrote:
> > > On 7/10/20 11:43 AM, Marek Polacek via Gcc-patches wrote:
> > > > Here's an interesting issue: in this code a ) is mi
The 07/13/2020 12:24, Richard Sandiford wrote:
> Szabolcs Nagy writes:
> > The expected semantics and valid usage of __builtin_return_address is
> > not clear since it exposes implementation internals that are normally
> > not meaningful to portable c code.
> >
> > This documentation change tries
> On Wed, Jun 10, 2020 at 12:11:00PM -0400, David Malcolm wrote:
> > Thanks for the patch; sorry about the delay in reviewing it.
> >
> > Some high-level review points
> >
> > - I like the patch overall
> >
> > - This will deserve an item in the release notes
> >
> > - I don't like adding "glob
I discovered we were deleting cxxmain.c, which we generated at some
point in time. Not anymore.
nathan
--
Nathan Sidwell
diff --git c/gcc/Makefile.in w/gcc/Makefile.in
index d5dcc03d59b..2ba76656dbf 100644
--- c/gcc/Makefile.in
+++ w/gcc/Makefile.in
@@ -3501,7 +3501,6 @@ distclean: clean lang.d
Sigh, last week's success at not breaking things failed with an
incorrect 'fix' this morning. Let's reduce my confusion by making
lib/scanlang.exp the same on trunk as modules.
gcc/testsuite/
* lib/scanlang.exp (scan-lang-dump): Fix breakage.
(scan-lang-dump-times, scan-
On Sat, Jul 11, 2020 at 10:32:55AM -0400, Jason Merrill via Gcc-patches wrote:
> On 7/8/20 4:35 PM, Marek Polacek wrote:
> > On Fri, Jul 03, 2020 at 05:24:34PM -0400, Jason Merrill via Gcc-patches
> > wrote:
> > > On 6/22/20 10:09 PM, Marek Polacek wrote:
> > > > convert_like issues errors about b
On Mon, Jul 13, 2020 at 03:04:20PM -0400, David Malcolm wrote:
> > +@item -fdiagnostics-column-unit=@var{UNIT}
> > +@opindex fdiagnostics-column-unit
> > +Select the units for the column number. This affects traditional
> > diagnostics
> > +(in the absence of @option{-fno-show-column}), as well a
When considering to instantiate a member of a class template as part of an
explicit instantiation of the class template, we need to first check the
member's constraints before proceeding with the instantiation of the member.
Bootstrapped and regtested on x86_64-pc-linux-gnu, does this look OK to c
Because the check for power10_hw is not called
check_effective_target_power10_hw, it needs to be looked
for by is-effective-target-keyword. Also reorder things
in is-effective-target to put power10_hw with the other
ppc stuff.
These little fixes for power10 dejagnu support were pre-approved
for tr
Jakub Jelinek writes:
> On Wed, Jul 08, 2020 at 03:10:14PM +0100, Richard Sandiford wrote:
>> gcc/
>> PR target/95726
>> * config/aarch64/aarch64.c (aarch64_attribute_table): Add
>> "Advanced SIMD type".
>> * config/aarch64/aarch64-builtins.c: Include stringpool.h and
>> a
Ping: https://gcc.gnu.org/pipermail/gcc-patches/2020-July/549225.html
On 7/7/20 2:02 PM, Martin Sebor wrote:
Ping: https://gcc.gnu.org/pipermail/gcc-patches/2020-July/549225.html
On 6/30/20 6:23 PM, Martin Sebor wrote:
An enhancement to GCC 10 to improve the expansion of strncmp
calls with str
Ping: https://gcc.gnu.org/pipermail/gcc-patches/2020-June/548786.html
On 7/7/20 12:56 PM, Martin Sebor wrote:
Ping. Despite its size, there isn't much new in the patch, it
pretty much just splits an existing warning into two, one for
buffer overflow and another for "overread."
https://gcc.gnu.
OK to commit and backport.
On 6/30/20 11:12 PM, Mark Eggleston wrote:
Please find attached a patch which is a fix for PR95612. The original
patch is by Steve Kargl.
OK to commit and backport?
Commit message:
Fortran : ICE in gfc_check_pointer_assign PR95612
Output an error if the right ha
OK to commit and Backport.
On 6/18/20 1:11 AM, Mark Eggleston wrote:
Please find attached fix for PR95585.
OK to commit and backport?
Commit message:
Fortran : ICE in gfc_check_reshape PR95585
Issue an error where an array is used before its definition
instead of an ICE.
2020-06-18 Steven
Hello, Thomas,
Sorry it took me so long to get back to you.
Thanks for the patches you posted a couple of weeks ago, I'm merging
them into my aux-dump-revamp branch, where I'm accumulating the patches
related with this change.
On Jun 30, 2020, Thomas Schwinge wrote:
> For example, if there ar
On Jun 30, 2020, Thomas Schwinge wrote:
>>> I looked for a mkoffload
>>> program for it in the GCC source tree and couldn't find one.
> See 'gcc/config/i386/intelmic-mkoffload.c'. ;-)
Thanks!
> :-) Yes, I quickly tested, and found that similar changes are required
> there, too.
> Can you eas
FWIW, I spotted two bugs in the completely untested patch by running it
through the compiler. s/dmp_filename/dump_filename/g will fix it.
--
Alexandre Oliva, freedom fighterhe/himhttps://FSFLA.org/blogs/lxo/
Free Software Evangelist Stallman was right, but he's left :(
GNU T
*PING*
On 6/25/20 4:06 PM, Tobias Burnus wrote:
The test case was giving an ICE as it recursively called itself.
Rather obvious fix.
OK for the trunk?
Tobias
-
Mentor Graphics (Deutschland) GmbH, Arnulfstraße 201, 80634 München /
Germany
Registergericht München HRB 106955, Ges
On Mon, 13 Jul 2020, Matthias Klose wrote:
> On 6/17/20 3:11 PM, Richard Biener wrote:
> > On Wed, 17 Jun 2020, H.J. Lu wrote:
> >
> >> On Wed, Jun 17, 2020 at 5:33 AM Richard Biener wrote:
> >>>
> >>> On Wed, 17 Jun 2020, H.J. Lu wrote:
> >>>
> On Wed, Jun 17, 2020 at 5:00 AM Richard Biene
61 matches
Mail list logo