On Mon, Nov 1, 2021 at 6:18 PM Martin Sebor via Gcc-patches
wrote:
>
> Patch 1 in the series detects a small subset of uses of pointers
> made indeterminate by calls to deallocation functions like free
> or C++ operator delete. To control the conditions the warnings
> are issued under the new -Wu
On Sat, Oct 30, 2021 at 2:29 PM Richard Sandiford
wrote:
> Jason Merrill writes:
> > On 10/18/21 16:35, Richard Sandiford wrote:
> >> Jason Merrill writes:
> >>> On 9/24/21 13:53, Richard Sandiford wrote:
> + if (type == error_mark_node)
> +return lhd_simulate_record_decl (loc, n
David,
My patch file was broken. I am sorry for it. Here is the correct one.
Thanks a lot.
ChangeLog
2021-11-01 Haochen Gui
gcc/
* config/rs6000/rs6000-call.c (rs6000_gimple_fold_builtin): Disable
gimple fold for VSX_BUILTIN_XVMINDP, ALTIVEC_BUILTIN_VMINFP,
VSX_BU
This should address Jonathan's feedback and adds support for atomic_ref
On Wed, Sep 29, 2021 at 5:14 AM Jonathan Wakely wrote:
> On Mon, 27 Sept 2021 at 15:11, Thomas Rodgers
> wrote:
> >
> > From: Thomas Rodgers
> >
> > Now with checks for __has_builtin(__builtin_clear_padding)
> >
> > This c
Hi, Hao
Neither the inlined patch nor the attached patch seem to contain the
change to rs6000-call.c. I only see the new testcases.
Please resend the complete patch.
Thanks David
On Mon, Nov 1, 2021 at 2:48 AM HAO CHEN GUI wrote:
>
> Hi,
>
> This patch disables gimple folding for VSX_BUILTI
2021-11-01 Sandra Loosemore
gcc/fortran/
* gfortran.texi (Projects): Add bullet for helping with
incomplete standards compliance.
(Proposed Extensions): Delete section.
---
gcc/fortran/gfortran.texi | 92 ---
1 file ch
2021-11-01 Sandra Loosemore
gcc/fortran/
* intrinsic.texi (Introduction to Intrinsics): Genericize
references to standard versions.
* invoke.texi (-fall-intrinsics): Likewise.
(-fmax-identifier-length=): Likewise.
---
gcc/fortran/intrinsic.texi | 15
2021-11-01 Sandra Loosemore
gcc/fortran/
* intrinsic.texi (Introduction to Intrinsics): Genericize
references to standard versions.
* invoke.texi (-fall-intrinsics): Likewise.
(-fmax-identifier-length=): Likewise.
---
gcc/fortran/intrinsic.texi | 15
2021-11-01 Sandra Loosemore
gcc/fortran/
* gfortran.texi (Interoperability with C): Copy-editing. Add
more index entries.
(Intrinsic Types): Likewise.
(Derived Types and struct): Likewise.
(Interoperable Global Variables): Likewise.
(Inte
Fix various bit-rot in the discussion of standards conformance, remove
material that is only of historical interest, copy-editing. Also move
discussion of preprocessing out of the introductory chapter.
2021-11-01 Sandra Loosemore
gcc/fortran/
* gfortran.texi (About GNU Fortran
Discussion of conformance with various revisions of the
Fortran standard was split between two separate parts of the
manual. This patch moves it all to the introductory chapter.
2021-11-01 Sandra Loosemore
gcc/fortran/
* gfortran.texi (Standards): Move discussion of specific
This series of patches addresses some areas of bit-rot in the GNU
Fortran manual, mainly relating to the state of standard compliance
and the recently-completed TS29113 work. I also removed some material
that is primarily of historical interest; given that gfortran replaced
g77 almost 17 years ago
Tested powerpc64le-linux, pushed to trunk.
The new 25_algorithms/move/constexpr.cc test fails in debug mode,
because the debug assertions use the non-constexpr overloads in
.
libstdc++-v3/ChangeLog:
* include/debug/stl_iterator.h (__valid_range): Add constexpr
for C++20. Qualify
Tested powerpc64le-linux, pushed to trunk.
In PR libstdc++/103013 Tim Song pointed out that we could reorder the
constraints of this constructor. That's worth doing just to reduce the
work the compiler has to do during overload resolution, even if it isn't
needed to make the code in the PR work.
On 10/11/21 9:17 AM, Marek Polacek via Gcc-patches wrote:
Any thoughts?
I'm a little unsure. Clang just uses the replacement string
as the text of the fix-it note as is, so it does nothing to
help programmers make sure the replacement is in sync with
what it's supposed to replace. E.g., for t
Patch 2 in this series adds support for detecting the uses of
dangling pointers: those to auto objects that have gone out of
scope. Like patch 1, to minimize false positives this detection
is very simplistic. However, thanks to the more deterministic
nature of the problem (all local objects go o
Patch 1 in the series detects a small subset of uses of pointers
made indeterminate by calls to deallocation functions like free
or C++ operator delete. To control the conditions the warnings
are issued under the new -Wuse-after-free= option provides three
levels. At the lowest level the warning
This two-patch series adds support for the detection of uses
of pointers invalidated as a result of the lifetime of
the objects they point to having ended: either explicitly,
after a call to a dynamic deallocation function, or implicitly,
by virtue of an object with automatic storage duration havi
On Mon, 1 Nov 2021, Marek Polacek via Gcc-patches wrote:
> + /* We've read a bidi char, update the current vector as necessary. */
> + void on_char (kind k, bool ucn_p)
> + {
> +switch (k)
> + {
> + case kind::LRE:
> + case kind::RLE:
> + case kind::LRO:
> + case k
Dear Fortranners,
a recent patch uncovered a latent issue with simplification of
array-valued expressions where the resulting shape was not set
from the referenced subobject. Once found, the fix looks obvious.
Regtested on x86_64-pc-linux-gnu. OK?
Thanks,
Harald
Fortran: fix simplification of
Hi,
this patch adds EAF_NOT_RETURNED_DIRECTLY which works similarly as
EAF_NODIRECTESCAPE. Values pointed to by a given argument may be returned but
not the argument itself. This helps PTA quite noticeably because we mostly
care about tracking points to which given memory location can escape.
I
On Mon, 1 Nov 2021 15:21:03 +0100
Aldy Hernandez wrote:
> I'm not convinced this makes the code clearer to read, especially if
> it's not on a critical path. But if you feel strongly, please submit
> a patch ;-).
No i don't feel strongly about it.
Compiling e.g. -O2 ira.o
# Overhead Sampl
On 10/27/21 08:33, Richard Biener wrote:
OK. (btw, can we use opts_set.param_... now instead of -1?)
Yes, we can. Let me try cooking a follow up patch.
Cheers,
Martin
On Mon, 1 Nov 2021, Patrick Palka wrote:
> On Fri, 29 Oct 2021, Jakub Jelinek wrote:
>
> > On Thu, Oct 28, 2021 at 03:35:20PM -0400, Patrick Palka wrote:
> > > > Is there a reason to turn this mode of evaluating everything twice if an
> > > > error should be diagnosed all the time, rather than on
On Mon, Nov 1, 2021 at 5:45 PM Roger Sayle wrote:
>
>
> This simple patch improves the implementation of 128-bit (TImode)
> rotations on x86_64 (a missed optimization opportunity spotted
> during the recent V1TImode improvements).
>
> Currently, the function:
>
> unsigned __int128 rotrti3(unsigned
On Fri, 29 Oct 2021, Jakub Jelinek wrote:
> On Thu, Oct 28, 2021 at 03:35:20PM -0400, Patrick Palka wrote:
> > > Is there a reason to turn this mode of evaluating everything twice if an
> > > error should be diagnosed all the time, rather than only if we actually
> > > see
> > > a TRUTH_*_EXPR we
Hello,
I'd like to ping this patch.
Thanks,
Martin
On Wed, Oct 13 2021, Martin Jambor wrote:
> Hi,
>
> in spring I added code eliminating any statements using parameters
> removed by IPA passes (to fix PR 93385). That patch fixed issues such
> as divisions by zero that such code could perform
This simple patch improves the implementation of 128-bit (TImode)
rotations on x86_64 (a missed optimization opportunity spotted
during the recent V1TImode improvements).
Currently, the function:
unsigned __int128 rotrti3(unsigned __int128 x, unsigned int i) {
return (x >> i) | (x << (128-i));
This adds support and a basic turning model for the Ampere Computing
"Ampere-1" CPU.
The Ampere-1 implements the ARMv8.6 architecture in A64 mode and is
modelled as a 4-wide issue (as with all modern micro-architectures,
the chosen issue rate is a compromise between the maximum dispatch
rate and t
Pushed as obvious.
Martin
Fixes:
UNRESOLVED: g++.dg/ipa/modref-1.C scan-ipa-dump local-pure-const1 "Function found
to be const: {anonymous}::B::genB"
UNRESOLVED: g++.dg/ipa/modref-1.C scan-ipa-dump modref1 "Retslot flags: direct
noescape nodirectescape not_returned noread"
gcc/testsuite/
On 11/1/21 16:32, David Malcolm wrote:
|Thanks. Here's an updated version of the script that fixes the above issues.|
Thanks. Please install it (there are no strict approval rules for contrib
folder).
Cheers,
Martin
On Mon, 2021-11-01 at 15:36 +0100, Martin Liška wrote:
> On 11/1/21 15:14, David Malcolm via Gcc-patches wrote:
> > > This script may be useful when debugging issues relating to
> > > Unicode encoding (e.g. when investigating source files with
> > > bidirectional control characters).|
>
> I like t
On 11/1/21 15:14, David Malcolm via Gcc-patches wrote:
|This script may be useful when debugging issues relating to Unicode encoding
(e.g. when investigating source files with bidirectional control characters).|
I like the script except the following flake8 issues:
$ flake8 contrib/unicode/ut
I'm not convinced this makes the code clearer to read, especially if
it's not on a critical path. But if you feel strongly, please submit
a patch ;-).
Aldy
On Mon, Nov 1, 2021 at 3:10 PM Bernhard Reutner-Fischer
wrote:
>
> On Thu, 28 Oct 2021 01:55:30 +0200
> Bernhard Reutner-Fischer wrote:
>
This script may be useful when debugging issues relating to Unicode
encoding (e.g. when investigating source files with bidirectional control
characters).
It dump a UTF-8 file as a list of numbered lines (mimicking GCC's
diagnostic output format), interleaved with lines per character showing
the U
On Thu, 28 Oct 2021 01:55:30 +0200
Bernhard Reutner-Fischer wrote:
> On Wed, 27 Oct 2021 20:13:21 +0200
> Aldy Hernandez via Gcc-patches wrote:
> > @@ -1306,6 +1307,24 @@ path_oracle::killing_def (tree ssa)
> >ptr->m_next = m_equiv.m_next;
> >m_equiv.m_next = ptr;
> >bitmap_ior_into
On Thu, Oct 21, 2021 at 12:56 PM H.J. Lu wrote:
>
> On Wed, Sep 22, 2021 at 7:02 PM H.J. Lu wrote:
> >
> > Changes in the v4 patch.
> >
> > 1. Add nodirect_extern_access attribute.
> >
> > Changes in the v3 patch.
> >
> > 1. GNU_PROPERTY_1_NEEDED_INDIRECT_EXTERN_ACCESS support has been added to
>
On 11/1/2021 3:54 AM, Tamar Christina via Gcc-patches wrote:
Hi All,
Some targets have overriden the default unroll factor and so do not have enough
data to succeed for SLP vectorization if loop vect is turned off.
To fix this just always unroll in these testcases.
Bootstrapped Regtested on
This patch adds support to GCC's diagnostic subsystem for escaping certain
bytes and Unicode characters when quoting source code.
Specifically, this patch adds a new flag rich_location::m_escape_on_output
which is a hint from a diagnostic that non-ASCII bytes in the pertinent
lines of the user's s
The testcase in question has a stmt of the form:
_10 = _4 <= _4;
We know this resolves to true, but when proce3ssing outgoing edges on
the following branch, we try to register the relations
_4 <= _4 and _4 > _4 on the 2 outgoing edges... which is nonsense of
course.
this patch simply c
Tested powerpc64le-linux, pushed to trunk.
The std::begin and std::end overloads for std::valarray are defined in
terms of std::addressof(v[0]) which is undefined for an empty valarray.
libstdc++-v3/ChangeLog:
PR libstdc++/103022
* include/std/valarray (begin, end): Do not deref
On Mon, Nov 1, 2021 at 2:03 PM Jeff Law wrote:
>
>
>
> On 11/1/2021 3:53 AM, Aldy Hernandez wrote:
> > This patch moves all the static functions into the pass class, and
> > cleans up things a little. The goal is to shuffle things around such
> > that we can add debug counters that depend on diff
On 11/1/2021 3:53 AM, Aldy Hernandez wrote:
This patch moves all the static functions into the pass class, and
cleans up things a little. The goal is to shuffle things around such
that we can add debug counters that depend on different threading
passes, but it's a clean-up on its own right.
On 11/1/2021 3:54 AM, Aldy Hernandez wrote:
Chasing down stage3 miscomparisons is never fun, and having no way to
distinguish between jump threads registered by a particular
pass, is even harder. This patch adds debug counters for the individual
back threading passes. I've left the ethread p
Fix a build regression from commit 04a9b554ba1a ("RISC-V: Cost model
for zba extension."):
.../gcc/config/riscv/riscv.c: In function 'bool riscv_rtx_costs(rtx,
machine_mode, int, int, int*, bool)':
.../gcc/config/riscv/riscv.c:2018:11: error: 'and' of mutually exclusive
equal-tests is always 0
Hi!
On Wed, Sep 01, 2021 at 11:13:43AM -0500, Bill Schmidt wrote:
> * config/rs6000/rs6000-call.c (rs6000_invalid_new_builtin):
> Implement.
That fits on one line. Don't wrap early, esp. not if that leaves a
colon without anything following it on that line: it looks like
something is
On Fri, Oct 29, 2021 at 3:04 PM Eric Gallager wrote:
>
> On Thu, Oct 21, 2021 at 12:49 PM H.J. Lu via Gcc-patches
> wrote:
> >
> > PR target/98667
> > * doc/invoke.texi: Document -fcf-protection requires i686 or
> > new.
> > ---
> > gcc/doc/invoke.texi | 3 ++-
> > 1 file
Dan Li via Gcc-patches writes:
> During the generation of the epilogue of aarch64(aarch64_expand_epilogue),
> the value of crtl->calls_eh_return does not need to be checked again.
> This value has been checked during aarch64_return_address_signing_enabled.
Ah, yeah, looks like this code became de
Chasing down stage3 miscomparisons is never fun, and having no way to
distinguish between jump threads registered by a particular
pass, is even harder. This patch adds debug counters for the individual
back threading passes. I've left the ethread pass alone, as that one is
usually benign, but we
Hi All,
Some targets have overriden the default unroll factor and so do not have enough
data to succeed for SLP vectorization if loop vect is turned off.
To fix this just always unroll in these testcases.
Bootstrapped Regtested on aarch64-none-linux-gnu, x86_64-pc-linux-gnu
and no issues.
Ok fo
Hi All,
The complex FMS detection is missing a check on if the nodes of the VEC_PERM
has the amount of children we expect before it recurses.
This check is there on MUL and FMA but was missing for FMS, due to this the
compiler goes on further than it should and hits an assert.
Bootstrapped Regte
This patch moves all the static functions into the pass class, and
cleans up things a little. The goal is to shuffle things around such
that we can add debug counters that depend on different threading
passes, but it's a clean-up on its own right.
Tested on x86-64 Linux.
OK?
gcc/ChangeLog:
When vxcrtstuff.c was created, the set of #includes was copied from
crtstuff.c. But crtstuff.c also has a bunch of #undefs after the first
#include, because, as the comment says, including auto-host.h when
building objects that are meant for target is technically not
correct.
This manifests when I
When the translation unit itself creates pointers to the ctors/dtors
in a specific section handled by the linker (whether .init_array or
.ctors.*), there's no reason for the functions to have external
linkage. That ends up polluting the symbol table in the running
kernel.
This makes vxcrtstuff.c o
These declarations prevent the priority given in the
constructor/destructor attributes from taking effect, thus emitting
the function pointers in the ordinary (lowest-priority)
.init_array/.fini_array sections.
libgcc/
* config/vxcrtstuff.c: Remove constructor/destructor
declaratio
Since commit 78e49fb1bc (Introduce vxworks specific crtstuff support),
the generic crtbegin.o/crtend.o have been unnecessary to build. So
remove them from extra_parts.
This is effectively a revert of commit 9a5b8df70 (libgcc: add
crt{begin,end} for powerpc-wrs-vxworks target).
libgcc/
* c
From: Rasmus Villemoes
A few things I hit when trying to upgrade our VxWorks5 toolchain. I
don't think these can break anything for VxWorks 6+, and patch 2
should be an improvement for all in that the current code doesn't get
compiled as it was clearly intended - though the real bug is likely in
On Mon, Nov 1, 2021 at 9:43 AM Jakub Jelinek wrote:
>
> On Mon, Nov 01, 2021 at 08:27:12AM +0100, Uros Bizjak wrote:
> > > Also, I wonder for all these patterns (previously and now added),
> > > shouldn't
> > > they have && TARGET_64BIT in conditions? I mean, we don't really support
> > > scalar
Tamar Christina writes:
>> -Original Message-
>> From: Richard Sandiford
>> Sent: Friday, October 8, 2021 5:24 PM
>> To: Tamar Christina
>> Cc: gcc-patches@gcc.gnu.org; nd ; Richard Earnshaw
>> ; Marcus Shawcroft
>> ; Kyrylo Tkachov
>> Subject: Re: [PATCH]AArch64 Make use of FADDP in si
Mailing list got lost somewhere, Archiving OK.
> -Original Message-
> From: Richard Sandiford
> Sent: Friday, October 29, 2021 4:52 PM
> To: Tamar Christina
> Cc: jeffreya...@gmail.com; rguent...@suse.de; nd
> Subject: Re: [PATCH 1/2] middle-end Teach CSE to be able to do vector
> extra
On Mon, Nov 01, 2021 at 08:27:12AM +0100, Uros Bizjak wrote:
> > Also, I wonder for all these patterns (previously and now added), shouldn't
> > they have && TARGET_64BIT in conditions? I mean, we don't really support
> > scalar TImode for ia32, but VALID_SSE_REG_MODE includes V1TImode and while
>
During the generation of the epilogue of aarch64(aarch64_expand_epilogue),
the value of crtl->calls_eh_return does not need to be checked again.
This value has been checked during aarch64_return_address_signing_enabled.
gcc/ChangeLog:
* config/aarch64/aarch64.c (aarch64_expand_epilogue):
gcc/ChangeLog:
* config/aarch64/aarch64.c (aarch64_expand_epilogue):
* config/aarch64/aarch64.md:
Signed-off-by: Dan Li
---
gcc/config/aarch64/aarch64.c | 6 +-
gcc/config/aarch64/aarch64.md | 3 +--
2 files changed, 2 insertions(+), 7 deletions(-)
diff --git a/gcc/config/
Hi,
this is patchs teaches ipa-modref about the static chain that is, like
retslot, a hiden argument. The patch is pretty much symemtric to what
was done for retslot handling and I verified it does the intended job
for Ada LTO bootstrap.
Bootstrapped/regtested x86_64-linux, OK?
Honza
gcc/Change
> -Original Message-
> From: Richard Sandiford
> Sent: Friday, October 8, 2021 5:24 PM
> To: Tamar Christina
> Cc: gcc-patches@gcc.gnu.org; nd ; Richard Earnshaw
> ; Marcus Shawcroft
> ; Kyrylo Tkachov
> Subject: Re: [PATCH]AArch64 Make use of FADDP in simple reductions.
>
> Tamar Chr
On Sun, Oct 31, 2021 at 11:02 AM Roger Sayle wrote:
>
>
> Very many thanks to Jakub for proof-reading my patch, catching my silly
> GNU-style
> mistakes and making excellent suggestions. This revised patch incorporates
> all of
> his feedback, and has been tested on x86_64-pc-linux-gnu with make
66 matches
Mail list logo
