Apologies! Forgot to attach the patch v2.
Done now.
>From 1d986ffd8b20007a6a2140e50935ade1bebc2228 Mon Sep 17 00:00:00 2001
From: Avinash Sonawane
Date: Tue, 22 Mar 2022 07:32:44 +0530
Subject: [PATCH] Docs: Document that taint analyzer checker disables some
warnings
---
gcc/doc/invoke.texi |
On Tue, 22 Mar 2022 19:15:02 -0400
David Malcolm wrote:
> So it would be even better if the text listed the warnings that are
> affected by this: basically all of the ones that are implemented in
> checkers i.e. analyzer/sm-*.cc (apart from sm-taint, of course).
Done! I could find 13 warnings in
On Wed, Mar 23, 2022 at 2:05 PM liuhongt via Gcc-patches
wrote:
>
> In validate_subreg, both (subreg:V2HF (reg:SI) 0)
> and (subreg:V8HF (reg:V2HF) 0) are valid, but not
> for (subreg:V8HF (reg:SI) 0) which causes ICE.
>
> Ideally it should be handled in validate_subreg to support
> subreg for all
In validate_subreg, both (subreg:V2HF (reg:SI) 0)
and (subreg:V8HF (reg:V2HF) 0) are valid, but not
for (subreg:V8HF (reg:SI) 0) which causes ICE.
Ideally it should be handled in validate_subreg to support
subreg for all modes available in TARGET_CAN_CHANGE_MODE_CLASS, but
that would be too risky
Segher Boessenkool writes:
> Hi!
>
> On Tue, Mar 22, 2022 at 01:50:39PM +0800, Jiufu Guo wrote:
>> Segher Boessenkool writes:
>> > On Mon, Mar 21, 2022 at 02:14:08PM -0400, David Edelsohn wrote:
>> >> On Mon, Mar 21, 2022 at 5:13 AM Jiufu Guo wrote:
>> >> > There is a rare corner case: where __
This is a crash where a FIX_TRUNC_EXPR gets into tsubst_copy_and_build
where it hits gcc_unreachable ().
The history of tsubst_copy_and_build/FIX_TRUNC_EXPR is such that it
was introduced in r181478, but it did the wrong thing, whereupon it
was turned into gcc_unreachable () in r258821 (see this t
On Tue, 2022-03-22 at 23:43 +0530, Avinash Sonawane via Gcc-patches
wrote:
> Hello!
>
> $ man gcc says that "Some checkers are disabled by default (even with
> -fanalyzer), such as the "taint" checker that implements
> -Wanalyzer-tainted-array-index, and this option is required to enable
> them."
On Tue, Mar 22, 2022 at 08:39:21PM +, Ed Catmur wrote:
> If two arrays do not have the exact same element type including
> qualification, this could be e.g. f(int (&&)[]) vs. f(int const (&)[]), which
> can still be distinguished by the lvalue-rvalue tiebreaker.
>
> By tightening this branch
If two arrays do not have the exact same element type including qualification,
this could be e.g. f(int (&&)[]) vs. f(int const (&)[]), which can still be
distinguished by the lvalue-rvalue tiebreaker.
By tightening this branch (in accordance with the letter of the Standard) we
fall through to
On Tue, 22 Mar 2022, Marek Polacek via Gcc-patches wrote:
> PR c/82283
> PR c/84685
>
> gcc/c/ChangeLog:
>
> * c-typeck.cc (struct initializer_stack): Add 'designated' member.
> (start_init): Set it.
> (finish_init): Restore constructor_designated.
> (push_ini
This patch fixes two kinds of wrong -Wmissing-field-initializers
warnings. Our docs say that this warning "does not warn about designated
initializers", but we give a warning for
1) the array case:
struct S {
struct N {
int a;
int b;
} c[1];
} d = {
.c[0].a = 1,
.
Dear all,
as reported by Martin Liška, a sanitized compiler hits an uninitialized stride
value when simplifying CSHIFT in testcase gfortran.dg/simplify_cshift_1.f90.
Committed as obvious after confirmation in the PR by Martin that the attached
patch fixes the issue.
commit r12-7771-g774ab2edcb5f3
---
htdocs/contribute.html | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/htdocs/contribute.html b/htdocs/contribute.html
index c0223738..2d04b1f0 100644
--- a/htdocs/contribute.html
+++ b/htdocs/contribute.html
@@ -267,7 +267,7 @@ characters.
The classifier identifi
---
htdocs/codingrationale.html | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/htdocs/codingrationale.html b/htdocs/codingrationale.html
index 0b44f1da..f523f3e2 100644
--- a/htdocs/codingrationale.html
+++ b/htdocs/codingrationale.html
@@ -18,7 +18,7 @@
Inlining funct
---
htdocs/codingconventions.html | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/htdocs/codingconventions.html b/htdocs/codingconventions.html
index e4d30510..86b63b89 100644
--- a/htdocs/codingconventions.html
+++ b/htdocs/codingconventions.html
@@ -141,7 +141,7 @@ a la
---
htdocs/branch-closing.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/htdocs/branch-closing.html b/htdocs/branch-closing.html
index c36ad1ab..15fb90e3 100644
--- a/htdocs/branch-closing.html
+++ b/htdocs/branch-closing.html
@@ -54,7 +54,7 @@ is listed in "Known to work
While working on a separate patch, I found several typos on the website.
I have only looked within the htdocs directory, not its subdirectories.
These are individual patches per file, since that seemed reasonable to me.
I believe this is a small enough change that I do not need to go through
copy
On Tue, 22 Mar 2022, Patrick Palka wrote:
> Here we're neglecting to clear cp_unevaluated_operand when substituting
> into the arguments of the alias template-id skip<(T(), 0), T> with T=A,
> which means cp_unevaluated_operand remains set during mark_used for
> A::A() and so we never synthesize it
Hello!
$ man gcc says that "Some checkers are disabled by default (even with
-fanalyzer), such as the "taint" checker that implements
-Wanalyzer-tainted-array-index, and this option is required to enable
them." but still lists the -Wanalyzer-tainted-* checkers under
-fanalyzer saying "Enabling thi
Here we're neglecting to clear cp_unevaluated_operand when substituting
into the arguments of the alias template-id skip<(T(), 0), T> with T=A,
which means cp_unevaluated_operand remains set during mark_used for
A::A() and so we never synthesize it. Later constant evaluation for
the substituted te
On Tue, 22 Mar 2022 at 15:48, Hans-Peter Nilsson via Libstdc++
wrote:
>
> Ok to commit?
OK, thanks.
>
> - 8< -
>
> Without this, for a typical soft-float target such as cris-elf, after
> commit r12-7676-g5a4e208022e704 you'll see, in libstdc++.log:
> ...
> FAIL: 20_util/from_chars/6.cc
Hi Jakub, hi Richi,
On 22.03.22 15:27, Jakub Jelinek wrote:
On Tue, Mar 22, 2022 at 01:56:27PM +0100, Tobias Burnus wrote:
name = lto_get_decl_name_mapping (file_data, name);
[...]
+ name = lto_get_decl_name_mapping (file_data, name);
This looks weird. IMHO we should make sure that the h
Ok to commit?
- 8< -
Without this, for a typical soft-float target such as cris-elf, after
commit r12-7676-g5a4e208022e704 you'll see, in libstdc++.log:
...
FAIL: 20_util/from_chars/6.cc (test for excess errors)
Excess errors:
/home/hp/tmp/auto0321/gcc/libstdc++-v3/testsuite/20_util/from_
On Tue, Mar 22, 2022 at 01:39:12PM +0100, Martin Liška wrote:
> Pushed to master as obvious.
An obvious what? It is not an improvement, just a change.
> - error ("unknown vectorization library ABI type (%qs) for "
> + error ("unknown vectorization library ABI type %qs for "
>
On Tue, Mar 22, 2022 at 01:50:09PM +0100, Martin Liška wrote:
> Pushed as obvious.
> - warning (0, "passing argument %d of %qE discards const qualifier
> "
> - "from pointer target type", n + 1, fndecl);
> + warning (0, "passing argument %d of %qE discards % "
>
Hi!
This got broken with r12-3529 and fixed with r12-5255.
Tested on x86_64-linux, committed to trunk as obvious.
2022-03-22 Jakub Jelinek
PR c++/102489
* g++.dg/coroutines/pr102489.C: New test.
--- gcc/testsuite/g++.dg/coroutines/pr102489.C.jj 2022-03-22
15:34:00.372
This reverts commit r12-1434-g046a3beb1673bf to fix PR target/104882.
As discussed in the PR, it turns out that the MVE ISA has no natural
mapping with GCC's vec_pack_trunc / vec_unpack standard patterns, unlike
Neon or SVE for instance.
This patch also adds the executable testcase provided in th
On Thu, Mar 17, 2022 at 8:05 AM H.J. Lu wrote:
>
> On Mon, Mar 14, 2022 at 7:31 AM H.J. Lu wrote:
> >
> > Push target("general-regs-only") in if x87 is enabled.
> >
> > gcc/
> >
> > PR target/104890
> > * config/i386/x86gprintrin.h: Also check _SOFT_FLOAT before
> > pushi
On Mon, Mar 21, 2022 at 2:59 PM Uros Bizjak wrote:
>
> On Mon, Mar 21, 2022 at 10:57 PM H.J. Lu wrote:
> >
> > On Mon, Mar 21, 2022 at 10:50:11PM +0100, Uros Bizjak wrote:
> > > On Mon, Mar 21, 2022 at 10:47 PM H.J. Lu wrote:
> > > >
> > > > On Mon, Mar 21, 2022 at 10:23:59PM +0100, Uros Bizjak
On Tue, Mar 22, 2022 at 01:56:27PM +0100, Tobias Burnus wrote:
> --- a/gcc/cgraph.cc
> +++ b/gcc/cgraph.cc
> @@ -3980,6 +3980,9 @@ cgraph_node::get_untransformed_body ()
>
>/* We may have renamed the declaration, e.g., a static function. */
>name = lto_get_decl_name_mapping (file_data, n
Hi!
On Tue, Mar 22, 2022 at 01:50:39PM +0800, Jiufu Guo wrote:
> Segher Boessenkool writes:
> > On Mon, Mar 21, 2022 at 02:14:08PM -0400, David Edelsohn wrote:
> >> On Mon, Mar 21, 2022 at 5:13 AM Jiufu Guo wrote:
> >> > There is a rare corner case: where __vector is followed only with ";"
> >>
On Mon, 21 Mar 2022, Jason Merrill via Gcc-patches wrote:
> Our C++20 designated initializer handling was broken with members of class
> type; we would find the relevant member and then try to find a member of
> the member with the same name. Or we would sometimes ignore the designator
> entirely
Hi,
The percentage sign as first character of a ptx identifier can be used to
avoid name conflicts, e.g., between user-defined variable names and
compiler-generated names.
The insn nvptx_uniform_warp_check contains register names without '%' prefix,
which potentially could lead to name conflicts
Hi,
With PR104489 still open and end-of-stage-4 approaching, classify HFmode
support as experimental, which is not enabled by default but can be enabled
using -mexperimental.
This fixes the nvptx build when the default sm_xx is set to sm_53 or higher.
Note that we're not using -mfp16 or some suc
Hi,
Add new option -mexperimental.
This allows, rather than developing a new feature to completion in a
development branch, to develop a new feature on trunk, without disturbing
trunk.
The equivalent of the feature branch merge then becomes making the
functionality available for -mno-experimenta
Hi,
Starting with ptx isa version 6.3, a ptx directive .alias is available.
Use this directive to support symbol aliases, as far as possible.
The alias support is off by default. It can be turned on using a switch
-malias.
Furthermore, for pre-sm_75, it's not effective unless the ptx version is
Hi,
Consider this code (with N defined to 1024):
...
float v = 0.0;
#pragma omp target map(tofrom: v)
#pragma omp parallel for simd
for (int i = 0 ; i < N; i++)
{
#pragma omp atomic update
v = v + 1.0;
}
...
It hangs when executing on target board unix/-foffload=-misa=
The following guards dse_classify_store with the same condition as
the DSE pass does - availability of a virtual definition. For
the PR we run into the fortran frontend generating a clobber for
a FUNCTION_DECL lhs which is ignored by the operand scanner and has
no virtual operands assigned. Apart
This patch fixes some same-local-name issues with offloading.
The first issue can also occur with -flto with -foffload=disable (I think).
Otherwise, all three issues apply to the non-host lto1 run
(defined ACCEL_COMPILER).
First, for omp declare link(var), a variable is declared
based on DECL
Pushed to master as obvious.
Martin
PR target/104902
gcc/ChangeLog:
* config/nvptx/nvptx.cc (handle_ptx_version_option):
Fix option wrapping in an error message.
---
gcc/config/nvptx/nvptx.cc | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/gcc/c
On 3/22/22 13:50, Martin Liška wrote:
+warning (0, "passing argument %d of %qE discards % "
I've just installed version only with one space. Sorry for noise.
Martin
Pushed as obvious.
Martin
PR target/104903
gcc/ChangeLog:
* config/rs6000/rs6000-c.cc (altivec_resolve_overloaded_builtin):
Wrap const keyword.
---
gcc/config/rs6000/rs6000-c.cc | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/gcc/config/rs6000/r
Pushed as obvious.
Martin
PR target/104904
gcc/ChangeLog:
* config/v850/v850-c.cc (pop_data_area): Fix typo in pragma
name.
---
gcc/config/v850/v850-c.cc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gcc/config/v850/v850-c.cc b/gcc/config/v850/v850-
Pushed to master as obvious.
Use '%qs' instead of '(%qs)'.
gcc/ChangeLog:
* config/i386/i386-options.cc (ix86_option_override_internal):
Use '%qs' instead of '(%qs)'.
gcc/testsuite/ChangeLog:
* gcc.target/i386/pr99753.c: Update test.
* gcc.target/i386/spellch
Pushed to master as obvious.
PR target/104898
gcc/ChangeLog:
* config/rs6000/rs6000.cc (rs6000_option_override_internal):
Use %qs instead of (%qs).
---
gcc/config/rs6000/rs6000.cc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gcc/config/rs6000/rs60
Pushed to master.
Martin
Use 'qs' and remove usage '(%qs)'.
PR target/104898
gcc/ChangeLog:
* config/aarch64/aarch64.cc (aarch64_handle_attr_arch):
Use 'qs' and remove usage '(%qs)'.
(aarch64_handle_attr_cpu): Likewise.
(aarch64_handle_attr_tune): Likew
chenglulu writes:
> Hi, all:
>
> This is the v9 version of LoongArch Port based on
> 9fc8f278ebebc57537dc0cb9d33e36d932be0bc3.
> Please review.
Thanks for the update. I've sent follows-up for parts 4, 6, 11 and 12,
but otherwise v9 addresses all the comments I had. The series LGTM
with those i
chenglulu writes:
> +@item -msmall-data-limit=@var{number}
> +@opindex -msmall-data-limit
> +Put global and static data smaller than @code{number} bytes into a special
> +section (on some targets). The default value is 0.
One minor left-over from v8: this should be @var{number}
rather than @code
chenglulu writes:
> diff --git a/gcc/testsuite/lib/target-supports.exp
> b/gcc/testsuite/lib/target-supports.exp
> index 737e1a8913b..843b508b010 100644
> --- a/gcc/testsuite/lib/target-supports.exp
> +++ b/gcc/testsuite/lib/target-supports.exp
> @@ -286,6 +286,10 @@ proc check_configured_with {
Hi,
Thanks for the update. It looks like there are some unaddressed
comments from the v8 review:
chenglulu writes:
> gcc/
>
> * config/loongarch/larchintrin.h: New file.
> * config/loongarch/loongarch-builtins.cc: New file.
> ---
> gcc/config/loongarch/larchintrin.h | 409 +
> Am 22.03.2022 um 10:28 schrieb Rainer Orth :
>
> Hi Jakub,
>
>> As reported, libtool -export-symbols-regex doesn't work on Solaris
>> when using GNU ld instead of Sun ld, libtool just always assumes Sun ld.
>> As I'm unsure what is the maintainance status of libtool right now,
>
> as it ha
Hi Jakub,
> As reported, libtool -export-symbols-regex doesn't work on Solaris
> when using GNU ld instead of Sun ld, libtool just always assumes Sun ld.
> As I'm unsure what is the maintainance status of libtool right now,
as it happens, libtool 2.4.7 has just been released on 2022-03-16 after
a
Hi!
As reported, libtool -export-symbols-regex doesn't work on Solaris
when using GNU ld instead of Sun ld, libtool just always assumes Sun ld.
As I'm unsure what is the maintainance status of libtool right now,
this patch solves it on the lto-plugin side instead, tests at configure time
similar w
On Tue, Mar 22, 2022 at 3:51 AM H.J. Lu wrote:
>
> On Mon, Mar 14, 2022 at 8:44 AM Richard Sandiford
> wrote:
> >
> > Richard Biener writes:
> > > On Wed, Mar 9, 2022 at 7:04 PM Richard Sandiford
> > > wrote:
> > >>
> > >> Richard Biener via Gcc-patches writes:
> > >> > On Wed, Mar 2, 2022 at
On Tue, 22 Mar 2022, Jakub Jelinek wrote:
> Hi!
>
> This test started ICEing with r12-3876 but stopped with r12-5264.
>
> Committed to trunk as obvious.
>
> Can we close the PR (are the unroll-and-jam bugs if any are latent) tracked
> elsewhere?
I think we can close the bug, I don't think ther
Hi!
This test started ICEing with r12-3876 but stopped with r12-5264.
Committed to trunk as obvious.
Can we close the PR (are the unroll-and-jam bugs if any are latent) tracked
elsewhere?
2022-03-22 Jakub Jelinek
PR tree-optimization/102645
* gcc.c-torture/compile/pr102645.c
Hi!
C++14 to C++20 apparently should allow extern thread_local declarations in
constexpr functions, however useless they are there (because accessing
such vars is not valid in a constant expression, perhaps sizeof/decltype).
P2242 changed that for C++23 to passing through declaration but
https://c
On Tue, 22 Mar 2022, Jakub Jelinek wrote:
> Hi!
>
> On Mon, Feb 28, 2022 at 07:52:56AM -, Roger Sayle wrote:
> > This patch resolves PR c++/84964 which is an ICE in the middle-end after
> > emitting a "sorry, unimplemented" message, and is a regression from
> > earlier releases of GCC. This
Hi!
On Mon, Feb 28, 2022 at 07:52:56AM -, Roger Sayle wrote:
> This patch resolves PR c++/84964 which is an ICE in the middle-end after
> emitting a "sorry, unimplemented" message, and is a regression from
> earlier releases of GCC. This issue is that after encountering a
> function call requ
On Mon, Mar 21, 2022 at 2:08 PM liuhongt via Gcc-patches
wrote:
>
> Failed to match this instruction:
> (set (reg/v:SI 88 [ z ])
> (if_then_else:SI (eq (zero_extract:SI (reg:SI 92)
> (const_int 1 [0x1])
> (zero_extend:SI (subreg:QI (reg:SI 93) 0)))
>
60 matches
Mail list logo
