R30_REGNUM could also be used as a component in shrink-wrapping
separate, this patch enables it in aarch64.
gcc/ChangeLog:
* config/aarch64/aarch64.cc (aarch64_get_separate_components):
Remove bitmap clear of R30_REGNUM.
(aarch64_components_for_bb): Support R30_REGNUM as
On Thu, 24 Feb 2022, Tamar Christina wrote:
> Hi All,
>
> This is a backport of the GCC 12 patch backporting only the correctness part
> of
> the fix. This also backports two small helper functions and documentation
> update on the optabs.
>
> The patch boosts the analysis for complex
On Thu, 24 Feb 2022, Qing Zhao wrote:
> I briefly checked all the usages of suppress_warning within the current gcc,
> and see that most of them are not guarded by any condition.
>
> So, the current change should be fine without introducing new issues. -:)
>
> Another thing is, if we use
On Fri, Feb 25, 2022 at 1:50 PM liuhongt wrote:
>
> The patch fixes ICE in ix86_gimple_fold_builtin.
>
Bootstrapped and regtested on x86_64-linux-gnu{-m32,}.
Ok for main trunk?
> gcc/ChangeLog:
>
> PR target/104666
> * config/i386/i386-expand.cc
>
The patch fixes ICE in ix86_gimple_fold_builtin.
gcc/ChangeLog:
PR target/104666
* config/i386/i386-expand.cc
(ix86_check_builtin_isa_match): New func.
(ix86_expand_builtin): Move code to
ix86_check_builtin_isa_match and call it.
*
On Thu, Feb 24, 2022 at 08:07:28AM +0100, Robin Dapp wrote:
> Hi,
>
> > Robin's patch has the effct making rs6000_emit_int_cmove return false for
> > floating point comparisons, so I marked the bug as being a duplicate of PR
> > target/104335.
>
> Didn't I just return false for MODE_CC? This
Richard Biener writes:
> On Thu, 24 Feb 2022, Jiufu Guo wrote:
>
>> Jiufu Guo via Gcc-patches writes:
>>
>> > Segher Boessenkool writes:
>> >
>> >> On Wed, Feb 23, 2022 at 02:02:59PM +0100, Richard Biener wrote:
>> >>> I'm assuming we're always dealing with
>> >>>
>> >>> (set (reg:MODE ..)
Hi, Jakub and Richard:
This is the 3rd version of the patch, the major change compared to the previous
version are:
1. Add warning_enabled_at guard before “suppress_warning”
2. Add location to the call to __builtin_clear_padding for auto init.
The patch has been bootstrapped and regress tested
On Thu, 24 Feb 2022, Marek Polacek via Gcc-patches wrote:
> gmp/mpfr/mpc/isl are DSOs I believe and therefore always PIC.
They are *not* DSOs when built in-tree (see the use of --disable-shared in
the relevant parts of Makefile.def).
> intl: I have no idea about this; I don't see any binaries
Tested powerpc64le-linux, pushed to trunk.
-- >8 --
This fixes a problem for Clang, which is going to return a non-void
pointer from __builtin_source_location(). The current definition of
std::source_location::current() converts that to void* and then has to
cast it back again in the body (which
On Thu, Feb 10, 2022 at 09:10:17PM +, Joseph Myers wrote:
> Some general observations:
Thanks for the comment and sorry for the delay (I was on vacation).
> * There are various toplevel GCC subdirectories that are built for the
> host (possibly in addition to the target in some cases) but
Hi All,
This is a backport of the GCC 12 patch backporting only the correctness part of
the fix. This also backports two small helper functions and documentation
update on the optabs.
The patch boosts the analysis for complex mul,fma and fms in order to ensure
that it doesn't create an
Hello, gentle maintainer.
This is a message from the Translation Project robot.
A revised PO file for textual domain 'gcc' has been submitted
by the German team of translators. The file is available at:
https://translationproject.org/latest/gcc/de.po
(This file,
Dear Jerry, Mikael,
thanks for the feedback!
Am 24.02.22 um 12:50 schrieb Mikael Morin:
Le 23/02/2022 à 23:21, Harald Anlauf via Fortran a écrit :
Dear Fortranners,
Fortran 2018 added a QUIET= specifier to STOP and ERROR STOP statements.
Janne already implemented the library side code four
On Sat, 2022-02-12 at 11:11 +0800, xucheng...@loongson.cn wrote:
> + /* Clean up the vars set above. Note that final_end_function resets
> + the global pointer for us. */
We don't have a global pointer. Let's kill this MIPS remenant :).
> + reload_completed = 0;
--
Xi Ruoyao
School
On Tue, 18 Jan 2022 18:58:00 PST (-0800), Kito Cheng wrote:
LGTM, thanks for adding those comments :)
Committed
On Wed, Jan 19, 2022 at 1:21 AM Palmer Dabbelt wrote:
The code generated by -mcmodel=medany is defined to be
position-independent, but is not guaranteed to function correctly
On Sat, 2022-02-12 at 11:11 +0800, xucheng...@loongson.cn wrote:
> From: chenglulu
>
> 2022-02-12 Chenghua Xu
> Lulu Cheng
>
> gcc/testsuite/
spec-barrier tests fail with:
./testsuite/c-c++-common/spec-barrier-1.c:21:3: warning: this target
does not define a speculation
On Sat, 2022-02-12 at 11:11 +0800, xucheng...@loongson.cn wrote:
> +mstrict-align
> +Target Var(TARGET_STRICT_ALIGN) Init(0)
> +Do not generate unaligned memory accesses.
Any update on the rational to make -mno-strict-align the default?
Note that I'm not against this decision: I'm really not a
On Thu, 2022-02-24 at 19:53 +0100, Jakub Jelinek wrote:
> On Fri, Feb 25, 2022 at 02:35:07AM +0800, Xi Ruoyao via Gcc-patches
> wrote:
> > Bootstrapped on x86_64-linux-gnu. OK for master?
> >
> > The third parameter of find_fde_tail is an _Unwind_Ptr (which is an
> > integer type instead of a
On Fri, Feb 25, 2022 at 02:35:07AM +0800, Xi Ruoyao via Gcc-patches wrote:
> Bootstrapped on x86_64-linux-gnu. OK for master?
>
> The third parameter of find_fde_tail is an _Unwind_Ptr (which is an
> integer type instead of a pointer), but we are passing NULL to it. This
> causes a
Bootstrapped on x86_64-linux-gnu. OK for master?
The third parameter of find_fde_tail is an _Unwind_Ptr (which is an
integer type instead of a pointer), but we are passing NULL to it. This
causes a -Wint-conversion warning.
libgcc/
* unwind-dw2-fde-dip.c (_Unwind_Find_FDE): Call
On Thu, Feb 10, 2022 at 04:17:00PM -0600, Pat Haugen wrote:
> Per Alan's comment in the bugzilla, fix attr-retain-* tescases for 32-bit
> PowerPC.
> --- a/gcc/testsuite/gcc.c-torture/compile/attr-retain-1.c
> +++ b/gcc/testsuite/gcc.c-torture/compile/attr-retain-1.c
> @@ -1,4 +1,5 @@
> /* {
On Sat, 2022-02-12 at 11:11 +0800, xucheng...@loongson.cn wrote:
> + sc = _->uc.uc_mcontext;
Get a warning:
In file included from ../../../libgcc/unwind-dw2.c:412:
./md-unwind-support.h: In function ‘loongarch_fallback_frame_state’:
./md-unwind-support.h:55:10: warning: assignment to
Ping.
On 2/10/22 4:17 PM, Pat Haugen via Gcc-patches wrote:
Per Alan's comment in the bugzilla, fix attr-retain-* tescases for 32-bit
PowerPC.
Bootstrapped and regression tested on powerpc64(32/64) and powerpc64le.
Ok for master?
-Pat
2022-02-10 Pat Haugen
PR testsuite/100407
I briefly checked all the usages of suppress_warning within the current gcc,
and see that most of them are not guarded by any condition.
So, the current change should be fine without introducing new issues. -:)
Another thing is, if we use “warning_enable_at” to guard, I just checked,
this
Folks,
> On 22 Feb 2022, at 14:44, Vladimir Makarov wrote:
>
>
> On 2022-02-20 12:34, Iain Sandoe wrote:
>>
>> ^^^ this is mostly for my education - the stuff below is a potential
>> solution to leaving lra-constraints unchanged and fixing the Darwin bug….
>>
> I'd be really glad if you do
On 2/21/22 17:48, Martin Liška wrote:
Ready to be installed?
I'm going to install this as obvious.
Martin
> On Thu, Feb 24, 2022 at 2:49 PM Jose E. Marchesi
> wrote:
>>
>>
>> > On Wed, Feb 23, 2022 at 8:56 PM Jose E. Marchesi
>> > wrote:
>> >>
>> >> This patch changes the build machinery in order to disable the build
>> >> of GCOV (both compiler and libgcc) in bpf-*-* targets. The reason for
>>
> On Feb 24, 2022, at 4:16 AM, Richard Biener wrote:
>
> On Sat, 19 Feb 2022, Qing Zhao wrote:
>
>> Hi,
>>
>> This is the 2nd patch for fixing pr102276.
>>
>> Adding -Wtrivial-auto-var-init and update documentation.
>>
>> Adding a new warning option -Wtrivial-auto-var-init to report cases
> On Feb 24, 2022, at 4:10 AM, Richard Biener wrote:
>
> On Sat, 19 Feb 2022, Qing Zhao wrote:
>
>> Hi,
>>
>> Per our discussion in the bug report
>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102276
>>
>> We decided to go with the following solution:
>>
>> 1. avoid emitting
On Thu, Feb 24, 2022 at 04:00:33PM +0100, Richard Biener wrote:
> > > --- a/gcc/gimple-fold.cc
> > > +++ b/gcc/gimple-fold.cc
> > > @@ -4379,7 +4379,12 @@ clear_padding_flush (clear_padding_struct *buf,
> > > bool full)
> > > else
> > > {
> > > src = make_ssa_name
On Thu, 24 Feb 2022, Jakub Jelinek wrote:
> On Thu, Feb 24, 2022 at 02:30:05PM +, Qing Zhao wrote:
> > PR middle-end/104550
> >
> > gcc/ChangeLog:
> >
> > * gimple-fold.cc (clear_padding_flush): Suppress warnings for new
> > created uses.
> >
> > gcc/testsuite/ChangeLog:
> >
>
On Thu, Feb 24, 2022 at 02:30:05PM +, Qing Zhao wrote:
> PR middle-end/104550
>
> gcc/ChangeLog:
>
> * gimple-fold.cc (clear_padding_flush): Suppress warnings for new
> created uses.
>
> gcc/testsuite/ChangeLog:
>
> * gcc.dg/auto-init-pr104550-1.c: New test.
>
Hi,
This is the 2nd version for this bug per our discussion.
Compared to the previous patch, this patch ONLY suppresses warnings for the
fake read that was introduced with folding.
The patch has been bootstrapped and regress tested on both x86 and aarch64.
Okay for trunk?
Thanks.
Qing
> On Feb 24, 2022, at 2:46 AM, Richard Biener wrote:
>
> On Wed, 23 Feb 2022, Qing Zhao wrote:
>
>>
>>
>>> On Feb 23, 2022, at 11:49 AM, Jakub Jelinek wrote:
>>>
>>> On Wed, Feb 23, 2022 at 05:33:57PM +, Qing Zhao wrote:
From my understanding, __builtin_clear_padding (), does not
Loop distribution can release SSA names used in nb_iterations, make
sure to release those.
Bootstrapped on x86_64-unknown-linux-gnu, testing in progress.
2022-02-24 Richard Biener
PR tree-optimization/104676
* tree-loop-distribution.cc (loop_distribution::execute):
Do
On Thu, Feb 24, 2022 at 2:49 PM Jose E. Marchesi
wrote:
>
>
> > On Wed, Feb 23, 2022 at 8:56 PM Jose E. Marchesi
> > wrote:
> >>
> >> This patch changes the build machinery in order to disable the build
> >> of GCOV (both compiler and libgcc) in bpf-*-* targets. The reason for
> >> this change
> On Wed, Feb 23, 2022 at 8:56 PM Jose E. Marchesi
> wrote:
>>
>> This patch changes the build machinery in order to disable the build
>> of GCOV (both compiler and libgcc) in bpf-*-* targets. The reason for
>> this change is that BPF is (currently) too restricted in order to
>> support the
Przemyslaw Wirkus writes:
> Ping :)
Sorry, guess I missed this.
>> This patch is sorting issue with LS64 intrinsics tests failing with
>> aarch64-linux-gnu_ilp32 target.
>>
>> Regtested on aarch64-linux-gnu_ilp32, aarch64-elf and aarch64_be-elf
>> and no issues.
>>
>> OK to install?
>>
>>
Le 23/02/2022 à 23:21, Harald Anlauf via Fortran a écrit :
Dear Fortranners,
Fortran 2018 added a QUIET= specifier to STOP and ERROR STOP statements.
Janne already implemented the library side code four (4!) years ago,
but so far the frontend implementation was missing.
Furthermore, F2018
On Thu, May 14, 2015 at 9:33 AM Marc Glisse wrote:
>
> Hello,
>
> after this patch I think I'll close the PR. This was regtested on
> ppc64le-redhat-linux.
>
> Apparently I wrote this patch in a file that already had a trivial hunk:
> -1-A -> ~A is rejected for complex while -A-1 isn't, there is
On Thu, Feb 24, 2022 at 11:32:53AM +0100, Tom de Vries wrote:
> libgomp/ChangeLog:
>
> 2022-02-24 Tom de Vries
>
> * testsuite/libgomp.c/declare-variant-3-sm30.c: New test.
> * testsuite/libgomp.c/declare-variant-3-sm35.c: New test.
> *
On Wed, Feb 23, 2022 at 11:47 PM Alexandre Oliva via Gcc-patches
wrote:
>
>
> This problem was already fixed as part of PR104263: the abnormal edge
> that remained from before inlining didn't make sense after inlining.
> So this patch adds only the testcase.
>
> Regstrapped on x86_64-linux-gnu.
On Wed, Feb 23, 2022 at 11:46 PM Alexandre Oliva via Gcc-patches
wrote:
>
>
> In def_cfa_0, we may set the 2nd operand's dw_cfi_cfa_loc to NULL, but
> then cfi_oprnd_equal_p calls cfa_equal_p with a NULL dw_cfa_location*.
> This patch aranges for us to tolerate NULL dw_cfi_cfa_loc.
>
>
On 2/24/22 11:09, Jakub Jelinek wrote:
On Thu, Feb 24, 2022 at 11:01:22AM +0100, Tom de Vries wrote:
[ was: Re: [Patch] nvptx: Add -mptx=6.0 + -misa=sm_70 ]
On 2/24/22 09:29, Tom de Vries wrote:
I'll try to submit a patch with one or more test-cases.
Hi,
These test-cases exercise the omp
On Wed, Feb 23, 2022 at 11:44 PM Alexandre Oliva via Gcc-patches
wrote:
>
>
> When we duplicate a throwing compare for hardening, the EH edge from
> the original compare gets duplicated for the inverted compare, but we
> failed to adjust any PHI nodes in the EH block. This patch adds the
>
On Wed, Feb 23, 2022 at 8:56 PM Jose E. Marchesi
wrote:
>
> This patch changes the build machinery in order to disable the build
> of GCOV (both compiler and libgcc) in bpf-*-* targets. The reason for
> this change is that BPF is (currently) too restricted in order to
> support the coverage
On Sat, 19 Feb 2022, Qing Zhao wrote:
> Hi,
>
> This is the 2nd patch for fixing pr102276.
>
> Adding -Wtrivial-auto-var-init and update documentation.
>
> Adding a new warning option -Wtrivial-auto-var-init to report cases when
> -ftrivial-auto-var-init cannot initialize the auto variable. At
On Sat, 19 Feb 2022, Qing Zhao wrote:
> Hi,
>
> Per our discussion in the bug report
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102276
>
> We decided to go with the following solution:
>
> 1. avoid emitting switch-unreachable warnings for -ftrivial-auto-var-init;
> 2. adding a new option
On Thu, Feb 24, 2022 at 11:01:22AM +0100, Tom de Vries wrote:
> [ was: Re: [Patch] nvptx: Add -mptx=6.0 + -misa=sm_70 ]
>
> On 2/24/22 09:29, Tom de Vries wrote:
> > I'll try to submit a patch with one or more test-cases.
>
> Hi,
>
> These test-cases exercise the omp declare variant construct
On Thu, 24 Feb 2022, Jakub Jelinek wrote:
> Hi!
>
> The following testcase is miscompiled, because -fipa-pure-const discovers
> that bar is const, but when sccvn during fre3 sees
> # .MEM_140 = VDEF <.MEM_96>
> *__pred$__d_43 = _50 (_49);
> where _50 value numbers to , it value numbers
[ was: Re: [Patch] nvptx: Add -mptx=6.0 + -misa=sm_70 ]
On 2/24/22 09:29, Tom de Vries wrote:
I'll try to submit a patch with one or more test-cases.
Hi,
These test-cases exercise the omp declare variant construct using the
available nvptx isas.
OK for trunk?
Thanks,
- Tom[libgomp,
I would suggest implementing that in riscv_subset_list::parse so that
it also affect the ELF attribute emission.
On Wed, Feb 23, 2022 at 5:44 PM wrote:
>
> From: LiaoShihua
>
> gcc/ChangeLog:
>
> * config/riscv/riscv-c.cc (riscv_cpu_cpp_builtins):Add __riscv_zks,
> __riscv_zk,
Hi!
The following testcase is miscompiled, because -fipa-pure-const discovers
that bar is const, but when sccvn during fre3 sees
# .MEM_140 = VDEF <.MEM_96>
*__pred$__d_43 = _50 (_49);
where _50 value numbers to , it value numbers .MEM_140 to
vuse_ssa_val (gimple_vuse (stmt)). For const/pure
On Thu, 24 Feb 2022, Jiufu Guo wrote:
> Jiufu Guo via Gcc-patches writes:
>
> > Segher Boessenkool writes:
> >
> >> On Wed, Feb 23, 2022 at 02:02:59PM +0100, Richard Biener wrote:
> >>> I'm assuming we're always dealing with
> >>>
> >>> (set (reg:MODE ..) )
> >>>
> >>> here and CSE is not
On Wed, 23 Feb 2022, Qing Zhao wrote:
>
>
> > On Feb 23, 2022, at 11:49 AM, Jakub Jelinek wrote:
> >
> > On Wed, Feb 23, 2022 at 05:33:57PM +, Qing Zhao wrote:
> >> From my understanding, __builtin_clear_padding (), does not _use_
> >> any variable,
> >> therefore, no uninitialized usage
On 2/22/22 17:03, Tobias Burnus wrote:
Hi Tom,
On 22.02.22 15:43, Tom de Vries wrote:
On 2/17/22 18:24, Tobias Burnus wrote:
--- a/gcc/config/nvptx/t-omp-device
+++ b/gcc/config/nvptx/t-omp-device
@@ -1,4 +1,4 @@
echo kind: gpu > $@
echo arch: nvptx >> $@
- echo isa: sm_30 sm_35
On 2/23/22 12:40, Tom de Vries wrote:
Hi,
Ptx contains funnel shift operations shf.l.wrap and shf.r.wrap that can be
used to implement 32-bit left or right rotate.
Add define_insns rotlsi3 and rotrsi3.
Currently testing.
And committed.
Thanks,
- Tom
[nvptx] Add shf.{l,r}.wrap insn
On 2/23/22 12:58, Thomas Schwinge wrote:
Hi!
On 2022-02-23T12:14:57+0100, Tom de Vries via Gcc-patches
wrote:
[ Re: [committed][nvptx] Add -mptx-comment ]
On 2/22/22 14:53, Tom de Vries wrote:
Add functionality that indicates which insns are added by -minit-regs, such
that for instance we
59 matches
Mail list logo
