https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54
--- Comment #3 from Tomas Chang ---
(In reply to Richard Biener from comment #2)
> Confirmed. Reproduces with -O3 -march=armv8.3-a and
>
> unsigned char desta[8];
> void copya(unsigned char *src, int size)
> {
> for (int i = 0; i < size;
After r14-2885-gb9237226fdc938, this pattern becomes
redundant as we match it using bitwise_inverted_equal_p.
There is already a testcase (gcc.dg/nand.c) for this pattern
and it still passes after the removal.
OK? Bootstrapped and tested on x86_64-linux-gnu with no regressions.
gcc/ChangeLog:
> @@ -11100,6 +11101,15 @@ proc check_vect_support_and_set_flags { } {
> }
> } elseif [istarget amdgcn-*-*] {
> set dg-do-what-default run
> +} elseif [istarget riscv64-*-*] {
> + if [check_effective_target_riscv_vector_hw] {
> + lappend
v1 -> v2:
1. Modify Changelog information format.
gcc/ChangeLog:
* common/config/loongarch/loongarch-common.cc:
Enable '-free' on O2 and above.
* doc/invoke.texi: Modify the description information
of the '-free' compilation option and add the LoongArch
gcc/ChangeLog:
* common/config/loongarch/loongarch-common.cc:
Enable '-free' on O2 and above.
* doc/invoke.texi:
Modify the description information of the '-free'
compilation option and add the LoongArch description.
gcc/testsuite/ChangeLog:
*
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86
vivek changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86
Bug ID: 86
Summary: food
Product: gcc
Version: 11.4.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83
--- Comment #1 from Nitesh Tiwari ---
dsafdsaf
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83
Bug ID: 83
Summary: dsaf
Product: gcc
Version: og13 (devel/omp/gcc-13)
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libbacktrace
Hi, this patch is enabling vec_init for RVV VLA vectorization since we have
almost
support all RVV-related features to the middle-end loop vectorizer.
Test report:
FAIL: gcc.dg/vect/bb-slp-10.c -flto -ffat-lto-objects scan-tree-dump slp2
"unsupported unaligned access"
FAIL:
Hi,
For PowerPC, some INT mode and FLOAT modes can be marked as tieable,
for example: DI<->DF.
One note SFmode is special, it would only tieable with itself.
I updated previous patch more reasonable:
https://gcc.gnu.org/pipermail/gcc-patches/2023-January/609504.html
Bootstrap and regtest pass
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=76
Bug ID: 76
Summary: test summary
Product: gcc
Version: 4.0.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: web
Assignee:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111076
xuli1 at eswincomputing dot com changed:
What|Removed |Added
CC||xuli1 at
Pushed to r14-3511.
在 2023/8/25 下午5:31, Lulu Cheng 写道:
v1 -> v2:
1. Modify description information
Since the SLT instruction does not distinguish between 64-bit operations and
32-bit
operations under the 64-bit LoongArch architecture, if the operand of slt is
SImode,
the sign
Thanks for taking care of this issue.
Ok to backport GCC-13.
juzhe.zh...@rivai.ai
From: Li Xu
Date: 2023-08-28 10:33
To: xuli1; gcc-patches
CC: kito.cheng; palmer; juzhe.zhong
Subject: Re: [PATCH V2] RISC-V: Insert vsetivli zero, 0 for vmv.x.s/vfmv.f.s
instructions satisfying
This patch should be backported to releases/gcc-13 to address
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111076
--
Li Xu
>This issue happens is because the operand1 of scalar move can be
>REG_P (operand[1]) in the O0 case, which causes the VSETVL PASS to
>not insert the vsetvl
Ok.
I am not familiar with scheduling stuff but I hope you can fix those 2 issues.
I have no objection with this patch and I prefer Jeff or kito make the decision
for this patch.
Thanks.
juzhe.zh...@rivai.ai
From: Robin Dapp
Date: 2023-08-23 22:56
To: 钟居哲; gcc-patches; palmer; kito.cheng;
Hi, Jeff,
Ping this patch since 18 days have passed. Is there any problem with
this patch after the last discussion? This is a bugfix patch, it will
affect the correctness, hope to have another look, thank you very much.
There seems to be a major question at the moment as to why I add a
Hi Carl,
on 2023/8/25 03:53, Carl Love wrote:
> GCC maintainers:
>
> Version 3, fixed the built-in instance names. Missed removing the "n"
> the name. Added the tighter constraints on the predicates for the
> define_insn. Updated the wording for the built-ins in the
> documentation file.
on 2023/8/26 06:04, Peter Bergner wrote:
> On 8/25/23 6:20 AM, Kewen.Lin wrote:
>> Assuming the current PCREL_SUPPORTED_BY_OS unchanged, when
>> PCREL_SUPPORTED_BY_OS is true, all its required conditions are
>> satisfied, it should be safe. while PCREL_SUPPORTED_BY_OS is
>> false, it means the
Committed.
Fix failures:
FAIL: gcc.target/riscv/rvv/vsetvl/vlmax_bb_prop-10.c -O2
scan-assembler-times
add\\ta[0-7],a[0-7],a[0-7]\\s+\\.L[0-9][0-9][0-9]\\:\\s+vle32\\.v\\s+(?:v[0-9]|v[1-2][0-9]|v3[0-1]),0\\s*\\([a-x0-9]+\\)
1
FAIL: gcc.target/riscv/rvv/vsetvl/vlmax_bb_prop-10.c -O2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111022
--- Comment #14 from john.harper at vuw dot ac.nz ---
To add to my email copied below, you may find a reference to the standards
helpful. k is the scale factor referred to in F2018 or F2023 13.7.2.3.3.
The last paragraph of that says that in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=19
--- Comment #5 from Hongtao.liu ---
Fixed in GCC14.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=19
--- Comment #4 from CVS Commits ---
The master branch has been updated by hongtao Liu :
https://gcc.gnu.org/g:945217845db7edb499d66ac56480ce569002b83e
commit r14-3509-g945217845db7edb499d66ac56480ce569002b83e
Author: liuhongt
Date: Fri Aug
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111022
--- Comment #13 from john.harper at vuw dot ac.nz ---
Hmmm. If I read anlauf correctly, our versions of ifort differ when
writing ES0.0E0 and EN0.0E0 with the value 666.0. Both give the same
correct numerical values but one version omits the E
Thanks kito.
Address all comments and committed with V3:
https://gcc.gnu.org/pipermail/gcc-patches/2023-August/628423.html
juzhe.zh...@rivai.ai
From: Kito Cheng
Date: 2023-08-25 01:01
To: Juzhe-Zhong
CC: gcc-patches; kito.cheng; jeffreyalaw; rdapp.gcc
Subject: Re: [PATCH V2] RISC-V: Refactor
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110891
Andrew Pinski changed:
What|Removed |Added
URL||patch
--- Comment #6 from Andrew
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67
--- Comment #2 from Andrew Pinski ---
>Take reduced from GCC's sources for lookup_attribute:
Note it shows up even not in a reduced version of lookup_attribute too.
This adds a simple case to remove an outer condition if the two inner
condtionals are the same and lead the same location.
This can show up due to jump threading or inlining or someone wrote code
like this.
ifcombine-1.c shows the simple case where this is supposed to solve.
Even though PRE can
Snapshot gcc-14-20230827 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/14-20230827/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 14 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111022
--- Comment #12 from Jerry DeLisle ---
(In reply to john.harper from comment #11)
I have the error check commented out during some of my checking on things. I
will revise the test case to test for the correct error.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111022
--- Comment #11 from john.harper at vuw dot ac.nz ---
Jerry's test program is identical with mine.
Because E format is supposed to give no digits before the decimal point
except possibly a leading zero, E0.0 and E0.0E0 are both pointless, and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109938
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |FIXED
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109828
Andrew Pinski changed:
What|Removed |Added
CC||Araknod at hotmail dot it
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=75
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=75
Bug ID: 75
Summary: Initialization of a structure with a flexible array
member with c23 storage class specifier causes
corruption, and ICE
Product: gcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99585
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |FIXED
Known to work|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111022
--- Comment #10 from anlauf at gcc dot gnu.org ---
(In reply to Jerry DeLisle from comment #9)
> I am using this:
>
> program teste0es0en0
> integer,parameter::p1 = kind(1e0), p2 = kind(1d0), &
>p3 =
Hello,
this fixes an old error-recovery bug.
Tested on x86_64-pc-linux-gnu.
OK for master?
-- >8 --
Keep memory of the content of the current interface body being parsed
and restore it to its previous state if it has been modified at the time
a parse attempt fails.
This fixes memory errors
Jivan's work also results in using a different save/restore function for
the spill-11 test. So the expected output needs minor adjusting.
Committed to the trunk.
Jeff
commit 3745feb19ed072e0865b12a891d7dbf7ba12c337
Author: Jeff Law
Date: Sun Aug 27 13:00:13 2023 -0600
RISC-V: Fix
Jivan's recent work on IRA results in more efficient code for this test.
This adjusts the expected output for the removal of 5 instructions and
conversion of an addi into a simple mv.
Pushed to the trunk,
Jeffcommit 6567837fd823a93f7f7948a73ff9dc1153592e8c
Author: Jeff Law
Date: Sun Aug
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110595
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |FIXED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110720
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |RESOLVED
The pressure sensitive scheduling change perturbs the output ever so
slightly for this test. Seemed easiest to just turn that off rather
than generalize the expected output enough to work across all the
relevant optimization options.
Pushed to the trunk.
Jeff
commit
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=74
Andrew Pinski changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52953
Andrew Pinski changed:
What|Removed |Added
CC||janschultke at googlemail dot
com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=74
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2023-08-27
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=74
Bug ID: 74
Summary: G++ allows re-declaring function parameters as
functions
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2023-08-27
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=73
--- Comment #2 from Jan Schultke ---
I think the problem is that GCC treats "constinit" exactly like "const" for the
purpose of diagnostics. In https://eel.is/c++draft/dcl.fct#11, it is said that
const applied to functions is ignored.
GCC
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=73
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2023-08-27
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96395
--- Comment #6 from CVS Commits ---
The trunk branch has been updated by Benjamin Priour :
https://gcc.gnu.org/g:55f6a7d949abc708d1c6ebc01eb3053f96d1472b
commit r14-3503-g55f6a7d949abc708d1c6ebc01eb3053f96d1472b
Author: benjamin priour
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=73
Bug ID: 73
Summary: G++ allows constinit functions
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111022
--- Comment #9 from Jerry DeLisle ---
I am using this:
program teste0es0en0
integer,parameter::p1 = kind(1e0), p2 = kind(1d0), &
p3 = selected_real_kind(precision(1.0_p2)+1), &
hp = selected_real_kind(precision(1.0_p3)+1), &
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=72
Bug ID: 72
Summary: Dead code in std::get for variant?
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70
--- Comment #2 from LIU Hao ---
(In reply to Costas Argyris from comment #1)
> Looks like '... @ Windows XP' is the Host, not the Target, in the PR.
> Target seems irrelevant here.
>
> LH, is this the issue you originally mentioned about my
f0d35ef-checking-yes-rtl-df-extra-riscv64
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 14.0.0 20230827 (experimental) (GCC)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70
Costas Argyris changed:
What|Removed |Added
CC||lh_mouse at 126 dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70
Bug ID: 70
Summary: Malformed manifest does not allow to run gcc on
Windows XP (Accessing a corrupted shared library)
Product: gcc
Version: 13.2.0
Status:
After two months on trunk, this has been backported:
Fortran: Fix some problems blocking associate meta-bug [PR87477]
2023-08-27 Paul Thomas
gcc/fortran
PR fortran/87477
* parse.cc (parse_associate): Replace the existing evaluation
of the target rank with calls to gfc_resolve_ref and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109948
--- Comment #21 from CVS Commits ---
The releases/gcc-13 branch has been updated by Paul Thomas :
https://gcc.gnu.org/g:d6997a5aab7aaa325946a6283bfee8ac2bd9f540
commit r13-7761-gd6997a5aab7aaa325946a6283bfee8ac2bd9f540
Author: Paul Thomas
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102190
--- Comment #4 from CVS Commits ---
The releases/gcc-13 branch has been updated by Paul Thomas :
https://gcc.gnu.org/g:d6997a5aab7aaa325946a6283bfee8ac2bd9f540
commit r13-7761-gd6997a5aab7aaa325946a6283bfee8ac2bd9f540
Author: Paul Thomas
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102532
--- Comment #5 from CVS Commits ---
The releases/gcc-13 branch has been updated by Paul Thomas :
https://gcc.gnu.org/g:d6997a5aab7aaa325946a6283bfee8ac2bd9f540
commit r13-7761-gd6997a5aab7aaa325946a6283bfee8ac2bd9f540
Author: Paul Thomas
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99326
--- Comment #8 from CVS Commits ---
The releases/gcc-13 branch has been updated by Paul Thomas :
https://gcc.gnu.org/g:d6997a5aab7aaa325946a6283bfee8ac2bd9f540
commit r13-7761-gd6997a5aab7aaa325946a6283bfee8ac2bd9f540
Author: Paul Thomas
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87477
--- Comment #6 from CVS Commits ---
The releases/gcc-13 branch has been updated by Paul Thomas :
https://gcc.gnu.org/g:d6997a5aab7aaa325946a6283bfee8ac2bd9f540
commit r13-7761-gd6997a5aab7aaa325946a6283bfee8ac2bd9f540
Author: Paul Thomas
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102112
--- Comment #4 from CVS Commits ---
The releases/gcc-13 branch has been updated by Paul Thomas :
https://gcc.gnu.org/g:d6997a5aab7aaa325946a6283bfee8ac2bd9f540
commit r13-7761-gd6997a5aab7aaa325946a6283bfee8ac2bd9f540
Author: Paul Thomas
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102109
--- Comment #5 from CVS Commits ---
The releases/gcc-13 branch has been updated by Paul Thomas :
https://gcc.gnu.org/g:d6997a5aab7aaa325946a6283bfee8ac2bd9f540
commit r13-7761-gd6997a5aab7aaa325946a6283bfee8ac2bd9f540
Author: Paul Thomas
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89867
Andrew Pinski changed:
What|Removed |Added
CC||stevenxia990430 at gmail dot
com
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69
Bug ID: 69
Summary: ICE on auto with may_alias attribute
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
70 matches
Mail list logo
