https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102989
--- Comment #108 from CVS Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:3ad9948b3e716885ce66bdf1c8e053880a843a2b
commit r14-3757-g3ad9948b3e716885ce66bdf1c8e053880a843a2b
Author: Jakub Jelinek
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102989
--- Comment #103 from CVS Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:faff31701d50fab08d75fbb13affc82cff74a72c
commit r14-3752-gfaff31701d50fab08d75fbb13affc82cff74a72c
Author: Jakub Jelinek
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102989
--- Comment #101 from CVS Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:2ce182e258d3ab11310442d5f4dd1d063018aca9
commit r14-3750-g2ce182e258d3ab11310442d5f4dd1d063018aca9
Author: Jakub Jelinek
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102989
--- Comment #102 from CVS Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:8c984a1c3693df63520558631c827bb2c2d8b5bc
commit r14-3751-g8c984a1c3693df63520558631c827bb2c2d8b5bc
Author: Jakub Jelinek
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102989
--- Comment #100 from CVS Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:7a610d44d855424518ecb4429ea5226ed2c32543
commit r14-3749-g7a610d44d855424518ecb4429ea5226ed2c32543
Author: Jakub Jelinek
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102989
--- Comment #99 from CVS Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:95521e15b6ef00c192a1bbd7c13b5f35395c7c9e
commit r14-3748-g95521e15b6ef00c192a1bbd7c13b5f35395c7c9e
Author: Jakub Jelinek
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102989
--- Comment #98 from CVS Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:b38deff6127778fed453bb647e32738ba5c78e33
commit r14-3747-gb38deff6127778fed453bb647e32738ba5c78e33
Author: Jakub Jelinek
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102989
--- Comment #96 from CVS Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:4f4fa2501186e43d115238ae938b3df322c9e02a
commit r14-3745-g4f4fa2501186e43d115238ae938b3df322c9e02a
Author: Jakub Jelinek
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102989
--- Comment #97 from CVS Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:a9d6c7fbeb374365058ffe2b9815d2b4b7193d38
commit r14-3746-ga9d6c7fbeb374365058ffe2b9815d2b4b7193d38
Author: Jakub Jelinek
Date:
Hi,
ping**2 on the revised patch, for Richard or another global reviewer. So far
all review feedback is that it’s a step forward, and it’s been widely used for
both aarch64-darwin and x86_64-darwin distributions for almost three years now.
OK to commit?
FX
> Le 5 août 2023 à 16:20, FX
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110664
--- Comment #4 from Jakub Jelinek ---
Oops, sorry, failed to find this PR when writing the patch.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110664
Joseph S. Myers changed:
What|Removed |Added
Target Milestone|--- |14.0
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111304
--- Comment #1 from Baptiste Demoulin ---
One comment: replacing `trim(prefix)` with `prefix(1:len_trim(prefix))` leads
to the same result, as does putting simply `prefix`, so the problem does not
seem to be related to using the `trim`
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111307
Bug ID: 111307
Summary: RFE: builtin to construct va_list
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107198
Jason Merrill changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111296
--- Comment #3 from CVS Commits ---
The master branch has been updated by Pan Li :
https://gcc.gnu.org/g:6b96de22d6bcadb45530c1898b264e4738afa4fd
commit r14-3744-g6b96de22d6bcadb45530c1898b264e4738afa4fd
Author: Juzhe-Zhong
Date: Wed Sep 6
This patch fix incorrect mode tieable between DI and V2SI which cause ICE
in RA.
PR target/111296
gcc/ChangeLog:
* config/riscv/riscv.cc (riscv_modes_tieable_p): Fix incorrect mode
tieable for RVV modes.
gcc/testsuite/ChangeLog:
* g++.target/riscv/rvv/base/pr111296.C:
On 9/6/23 16:12, David Malcolm wrote:
On Wed, 2023-09-06 at 15:53 +0200, Arthur Cohen wrote:
From: David Malcolm
I guess I can review this patch :)
Needs a ChangeLog entry, so here's one:
gcc/ChangeLog
* diagnostic-core.h (error_meta): New decl.
* diagnostic.cc
On 9/6/23 16:12, David Malcolm wrote:
On Wed, 2023-09-06 at 15:53 +0200, Arthur Cohen wrote:
From: David Malcolm
I guess I can review this patch :)
Needs a ChangeLog entry, so here's one:
gcc/ChangeLog
* diagnostic-core.h (error_meta): New decl.
* diagnostic.cc
On Wed, 2023-09-06 at 15:53 +0200, Arthur Cohen wrote:
> From: David Malcolm
This is probably something for the gcc-rust maintainers to review
(rather than me self-reviewing with my "diagnostics maintainer" hat
on).
Doesn't have a ChangeLog entry, FWIW.
Doesn't have a signed-off-by, so here's
On Wed, 2023-09-06 at 15:53 +0200, Arthur Cohen wrote:
> From: David Malcolm
This is probably something for the gcc-rust maintainers to review
(rather than me self-reviewing with my "diagnostics maintainer" hat
on).
Doesn't have a ChangeLog entry, FWIW.
Doesn't have a signed-off-by, so here's
On Wed, 2023-09-06 at 15:53 +0200, Arthur Cohen wrote:
> From: David Malcolm
I guess I can review this patch :)
Needs a ChangeLog entry, so here's one:
gcc/ChangeLog
* diagnostic-core.h (error_meta): New decl.
* diagnostic.cc (error_meta): New.
Also, needs a signed-off-by, so
On Wed, 2023-09-06 at 15:53 +0200, Arthur Cohen wrote:
> From: David Malcolm
I guess I can review this patch :)
Needs a ChangeLog entry, so here's one:
gcc/ChangeLog
* diagnostic-core.h (error_meta): New decl.
* diagnostic.cc (error_meta): New.
Also, needs a signed-off-by, so
On 9/5/23 23:47, Tsukasa OI wrote:
From: Tsukasa OI
'XVentanaCondOps' is a vendor extension from Ventana Micro Systems
containing two instructions for conditional move and will be supported on
their Veyron V1 CPU.
And most notably (for historical reasons), 'XVentanaCondOps' and the
Hi Richard,
> On 6 Sep 2023, at 13:43, Richard Sandiford via Gcc wrote:
>
> Iain Sandoe writes:
>> On the Darwin aarch64 port, we have a number of cleanup test fails (pretty
>> much corresponding to the [still open]
>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=39244). However, let’s
On 9/6/23 03:47, Juzhe-Zhong wrote:
This patch fix incorrect mode tieable between DI and V2SI which cause ICE
in RA.
PR target/111296
gcc/ChangeLog:
* config/riscv/riscv.cc (riscv_modes_tieable_p): Fix bug.
gcc/testsuite/ChangeLog:
*
Committed, thanks Robin.
Pan
-Original Message-
From: Gcc-patches On Behalf
Of Robin Dapp via Gcc-patches
Sent: Wednesday, September 6, 2023 9:39 PM
To: Juzhe-Zhong ; gcc-patches@gcc.gnu.org
Cc: kito.ch...@sifive.com; kito.ch...@gmail.com
Subject: Re: [PATCH] RISC-V: Remove
Committed, thanks Robin.
Pan
-Original Message-
From: Gcc-patches On Behalf
Of Robin Dapp via Gcc-patches
Sent: Wednesday, September 6, 2023 9:38 PM
To: Juzhe-Zhong ; gcc-patches@gcc.gnu.org
Cc: kito.ch...@sifive.com; kito.ch...@gmail.com
Subject: Re: [PATCH] RISC-V: Fix VSETVL PASS
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111295
--- Comment #6 from CVS Commits ---
The master branch has been updated by Pan Li :
https://gcc.gnu.org/g:1b4c70d4271a00514ae20970d483c3b78d9d66ef
commit r14-3743-g1b4c70d4271a00514ae20970d483c3b78d9d66ef
Author: Juzhe-Zhong
Date: Wed Sep 6
Hi.
I'll do another test to make sure this is enough since I tested with a
few more finalize functions.
Thanks a lot for finding this!
On Wed, 2023-09-06 at 09:40 -0400, David Malcolm via Jit wrote:
> As part of Antoyo's work on supporting LTO in rustc_codegen_gcc, he
> noticed an ICE inside
Hi David,
Thanks for the review.
On Tue, Sep 5, 2023 at 1:53 PM David Malcolm wrote:
> On Mon, 2023-09-04 at 20:00 +0200, priour...@gmail.com wrote:
>
>
[...snip...]
> All of these "new" tests (apart from the "-noexcept" ones) look like
> they're meant to be existing tests that were moved,
From: David Malcolm
---
gcc/rust/rust-diagnostics.cc | 11 +++
gcc/rust/rust-diagnostics.h | 18 ++
gcc/rust/rust-gcc-diagnostics.cc | 33 +++
gcc/rust/typecheck/rust-casts.cc | 2 +-
From: David Malcolm
---
gcc/diagnostic-core.h | 3 +++
gcc/diagnostic.cc | 15 +++
2 files changed, 18 insertions(+)
diff --git a/gcc/diagnostic-core.h b/gcc/diagnostic-core.h
index 7334c79e8e6..c9e27fd2e6e 100644
--- a/gcc/diagnostic-core.h
+++ b/gcc/diagnostic-core.h
@@
From: David Malcolm
---
gcc/rust/rust-diagnostics.cc | 11 +++
gcc/rust/rust-diagnostics.h | 18 ++
gcc/rust/rust-gcc-diagnostics.cc | 33 +++
gcc/rust/typecheck/rust-casts.cc | 2 +-
From: David Malcolm
---
gcc/diagnostic-core.h | 3 +++
gcc/diagnostic.cc | 15 +++
2 files changed, 18 insertions(+)
diff --git a/gcc/diagnostic-core.h b/gcc/diagnostic-core.h
index 7334c79e8e6..c9e27fd2e6e 100644
--- a/gcc/diagnostic-core.h
+++ b/gcc/diagnostic-core.h
@@
This short patchset from David Malcolm enables errors to contain extra
metadata - this is particularly useful for the Rust frontend, which will
rely on that implementation to emit standard Rust error codes [1].
This series of patches is necessary for much of our more recent
additions to the
This short patchset from David Malcolm enables errors to contain extra
metadata - this is particularly useful for the Rust frontend, which will
rely on that implementation to emit standard Rust error codes [1].
This series of patches is necessary for much of our more recent
additions to the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83028
--- Comment #5 from Jonathan Wakely ---
Yes, obviously, because separate statements have a sequence point between them.
Successfully bootstrapped & regrtested on x86_64-pc-linux-gnu.
Pushed to trunk as r14-3741-gf2d7a4001a3388.
gcc/analyzer/ChangeLog:
PR analyzer/105899
* kf.cc (class kf_strstr): New.
(kf_strstr::impl_call_post): New.
(register_known_functions): Register it.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52953
--- Comment #13 from Jonathan Wakely ---
Yes, Bug 74 is already closed as a duplicate of this one.
Successfully bootstrapped & regrtested on x86_64-pc-linux-gnu.
Pushed to trunk as r14-3740-gb51cde34d4e750.
gcc/analyzer/ChangeLog:
PR analyzer/105899
* kf.cc (class kf_strncpy): New.
(kf_strncpy::impl_call_post): New.
(register_known_functions): Register it.
I noticed that region_model's fill_region/zero_fill_region member
functions weren't checking that the write to the region was valid.
Fixed thusly.
Successfully bootstrapped & regrtested on x86_64-pc-linux-gnu.
Pushed to trunk as r14-3739-gb923978a6ec447.
gcc/analyzer/ChangeLog:
* kf.cc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111288
Jonathan Wakely changed:
What|Removed |Added
Last reconfirmed||2023-09-06
Ever confirmed|0
As part of Antoyo's work on supporting LTO in rustc_codegen_gcc, he
noticed an ICE inside libgccjit when compiling certain rust files.
Debugging libgccjit showed that outdated information from a previous
in-memory compile was referring to ad-hoc locations in the previous
compile's line_table.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111300
Jonathan Wakely changed:
What|Removed |Added
Last reconfirmed||2023-09-06
LGTM.
Regards
Robin
OK.
Regards
Robin
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105899
--- Comment #14 from CVS Commits ---
The master branch has been updated by David Malcolm :
https://gcc.gnu.org/g:f2d7a4001a33884bc1dfd8da58e58dee18e3cd71
commit r14-3741-gf2d7a4001a33884bc1dfd8da58e58dee18e3cd71
Author: David Malcolm
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105899
--- Comment #13 from CVS Commits ---
The master branch has been updated by David Malcolm :
https://gcc.gnu.org/g:b51cde34d4e7504e821d935152c0ece0ce0dc74d
commit r14-3740-gb51cde34d4e7504e821d935152c0ece0ce0dc74d
Author: David Malcolm
Date:
Hi Lehua,
> May I ask if the compiler options "-march=rv64gcv_zvfh -mabi=lp64d"
> should be removed? Because we don't specify -march and -mabi when we
> run testcase (so but why we need to specify the -march and -mabi in
> this target check?), we run it with the default values. Assuming that
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107198
Marek Polacek changed:
What|Removed |Added
CC||mpolacek at gcc dot gnu.org
---
Hi Juzhe,
general remark upfront: Please add function-level comments for all
functions. This makes reading and reviewing much easier. I had to sweep
back and forth quite a bit.
> +
> +static int
> +get_last_live_range (const vec _ranges, tree var)
> +{
> + unsigned int ix;
> +
Committed, thanks Juzhe and sorry for my silly mistake.
Pan
From: juzhe.zhong
Sent: Wednesday, September 6, 2023 8:53 PM
To: Li, Pan2
Cc: gcc-patches@gcc.gnu.org; Li, Pan2 ; Wang, Yanzhang
; kito.ch...@gmail.com
Subject: Re: [PATCH v1] RISC-V: Fix incorrect folder for VRGATHERI16 test case
From: Pan Li
Put the test file to the incorrect folder, this patch would like to
fix it.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/rvv/intrisinc-vrgatherei16.c: Moved to...
* gcc.target/riscv/rvv/base/intrisinc-vrgatherei16.c: ...here.
Signed-off-by: Pan Li
---
This patch covers signed and unsigned subtractions. The generated code
would be something along these lines:
signed:
sub.f r0, r1, r2
b.v @label
unsigned:
sub.f r0, r1, r2
b.c @label
gcc/ChangeLog:
* config/arc/arc.md (subsi3_v): New insn.
(subvsi4): New
This patch covers signed and unsigned additions. The generated code
would be something along these lines:
signed:
add.f r0, r1, r2
b.v @label
unsigned:
add.f r0, r1, r2
b.c @label
gcc/ChangeLog:
* config/arc/arc-modes.def: Add CC_V mode.
*
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111232
JuzheZhong changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111295
--- Comment #5 from JuzheZhong ---
I see. A candidate patch to fix this issue:
https://gcc.gnu.org/pipermail/gcc-patches/2023-September/629456.html
Fix bugzilla: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111295
PR target/111295
gcc/ChangeLog:
* config/riscv/riscv-vsetvl.cc (insert_vsetvl):
gcc/testsuite/ChangeLog:
* gcc.target/riscv/rvv/autovec/pr111295.c: New test.
---
gcc/config/riscv/riscv-vsetvl.cc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111303
--- Comment #4 from Jiu Fu Guo ---
For the pattern: "(X + C) / N", "op (plus@3 @0 INTEGER_CST@1) INTEGER_CST@2)"
where "X" has value-range, and "X + C" does not overflow:
&& get_range_query (cfun)->range_of_expr (vr0, @0))
&& get_range_query
Iain Sandoe writes:
> Hi Folks,
>
> On the Darwin aarch64 port, we have a number of cleanup test fails (pretty
> much corresponding to the [still open]
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=39244). However, let’s assume
> that bug could be a red herring..
>
> the underlying reason is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111303
--- Comment #3 from Jiu Fu Guo ---
In the pattern of match.pd, there is:
&& range_op_handler (PLUS_EXPR).overflow_free_p (vr0, vr1)
&& get_range_query (cfun)->range_of_expr (vr3, @3)
/* "X+C" and "X" are not of
Yang Yujie writes:
> gcc/ChangeLog:
>
> * config.gcc: remove non-POSIX syntax "<<<".
OK. Thanks for the quick fix.
Richard.
> ---
> gcc/config.gcc | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/gcc/config.gcc b/gcc/config.gcc
> index b2fe7c7ceef..6d4c8becd28
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111306
Bug ID: 111306
Summary: macro-fusion makes error on conjugate complex
multiplication
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Previously, I add TARGET_64BIT condtion to block VLS modes with size = 64bit
in RV32 system
E.g. V8QI
Since I realized such modes may cause inferior codegen for some situations in
RV32 system.
However, this is really quite ugly and it cause ICE for some cases in RV32:
FAIL:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111305
Bug ID: 111305
Summary: GCC Static Analyzer -Wanalyzer-out-of-bounds FP and
ICE problem
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66425
--- Comment #61 from Andrew Church ---
For the record, I'll maintain a copy of my (unaccepted) patch to add
-Wunused-result=strict at: https://achurch.org/patch-pile/#gcc
(wur-strict.diff)
This flag obviously shouldn't be relied on in released
Hi there,
We are excited to offer you a comprehensive email list of school districts that
includes key contact information such as phone numbers, email addresses,
mailing addresses, company revenue, size, and web addresses. Our databases also
cover related industries such as:
* K-12
Hi there,
We are excited to offer you a comprehensive email list of school districts that
includes key contact information such as phone numbers, email addresses,
mailing addresses, company revenue, size, and web addresses. Our databases also
cover related industries such as:
* K-12
Hello folks,
Here's v3 of the top part of the security policy. Hopefully this
addresses all concerns raised so far.
Thanks,
Sid
What is a GCC security bug?
===
A security bug is one that threatens the security of a system or
network, or might compromise the
Hi Richard,
I did some testing with the attached v2 that does not restrict to UNARY
anymore. As feared ;) there is some more fallout that I'm detailing below.
On Power there is one guality fail (pr43051-1.c) that I would take
the liberty of ignoring for now.
On x86 there are four fails:
-
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111304
Bug ID: 111304
Summary: Problem when passing implicit arrays of characters to
functions
Product: gcc
Version: 13.2.1
Status: UNCONFIRMED
Severity: normal
Committed, thanks Kito.
--
Best,
Lehua
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111303
Jiu Fu Guo changed:
What|Removed |Added
Last reconfirmed||2023-09-06
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111303
Jiu Fu Guo changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |guojiufu at gcc dot
gnu.org
---
On Wed, 2023-09-06 at 18:43 +0800, Xiaolong Chen wrote:
> gcc/testsuite/ChangeLog:
>
> * gcc.target/loongarch/strict-align.c: New test.
A question: is there really a CPU model with LSX/LASX but without
unaligned access support? If not I think we'd just reject -mstrict-
align -mlsx.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66425
--- Comment #60 from Segher Boessenkool ---
(In reply to Roman Krotov from comment #59)
> All, what I'm asking for, is to make something like -Wno-void-unused, which
> would suppress the warnings only for the (void) casted calls.
So you want to
Yang Yujie writes:
> gcc/ChangeLog:
>
> * config.gcc: remove non-POSIX syntax "<<<".
> ---
Thanks, I was just about to report this.
> gcc/config.gcc | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/gcc/config.gcc b/gcc/config.gcc
> index
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111295
--- Comment #4 from Jeremy Bennett ---
@JuzheZhong - it's a C test case, not C++. Look like you are trying to
compile it as C++.
Forgot to mention: I've bootstrapped and regtested this patch on
loongarch64-linux-gnu (with PR110939 patch applied to unbreak the
bootstrapping). Ok for trunk?
On Wed, 2023-09-06 at 18:46 +0800, Xi Ruoyao wrote:
> If mask is a constant with value ((1 << N) - 1) << M we can perform this
>
On Wed, 2023-09-06 at 18:45 +0800, Xiaolong Chen wrote:
> + *((int*)& __m128_op0[3]) = 0x004200a0;
> + *((int*)& __m128_op0[2]) = 0x;
> + *((int*)& __m128_op0[1]) = 0x004200a0;
> + *((int*)& __m128_op0[0]) = 0x0021;
These are aliasing rule violation and they will suddenly blow up
If mask is a constant with value ((1 << N) - 1) << M we can perform this
optimization.
gcc/ChangeLog:
PR target/111252
* config/loongarch/loongarch-protos.h
(loongarch_pre_reload_split): Declare new function.
(loongarch_use_bstrins_for_ior_with_mask): Likewise.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111295
--- Comment #3 from JuzheZhong ---
This code can not be compiled:
cc1plus: warning: command-line option '-Wno-implicit-function-declaration' is
valid for C/ObjC but not for C++
bug.C: In function 'int q()':
bug.C:6:9: warning: empty
gcc/testsuite/ChangeLog:
* gcc.target/loongarch/vector/lsx/lsx-builtin.c: New test.
---
.../loongarch/vector/lsx/lsx-builtin.c| 1461 +
1 file changed, 1461 insertions(+)
create mode 100644 gcc/testsuite/gcc.target/loongarch/vector/lsx/lsx-builtin.c
diff --git
gcc/testsuite/ChangeLog:
* gcc.target/loongarch/vector/loongarch-vector.exp: New test.
* gcc.target/loongarch/vector/simd_correctness_check.h: New test.
---
.../loongarch/vector/loongarch-vector.exp | 42 +++
.../loongarch/vector/simd_correctness_check.h | 39
gcc/testsuite/ChangeLog:
* gcc.target/loongarch/strict-align.c: New test.
---
gcc/testsuite/gcc.target/loongarch/strict-align.c | 13 +
1 file changed, 13 insertions(+)
create mode 100644 gcc/testsuite/gcc.target/loongarch/strict-align.c
diff --git
In order to better test the function of the vector instruction, the 128 and 256
bit test cases are further split according to the function of the instruction.
Xiaolong Chen (4):
LoongArch: Add tests of -mstrict-align option.
LoongArch: Add testsuite framework for Loongson SX/ASX.
On Wed, 2023-09-06 at 18:06 +0800, Yang Yujie wrote:
> When multilib is enabled, the c++ header directory of the default multilib
> variant needs to be linked to the toplevel since g++ does not search the
> toplevel in this case.
>
> libstdc++-v3/ChangeLog:
>
> * configure.host: Register
On Tue, Sep 5, 2023 at 2:29 AM Takayuki 'January June' Suwa
wrote:
>
> This patch optimizes the boolean evaluation for equality to 0 in SImode
> using the MINU (Minimum Value Unsigned) machine instruction available
> when TARGET_MINMAX is configured, for example, (x != 0) to MINU(x, 1)
> and (x
On Tue, Sep 5, 2023 at 9:24 PM Takayuki 'January June' Suwa
wrote:
> On 2023/09/06 8:01, Max Filippov wrote:
> > On Tue, Sep 5, 2023 at 2:29 AM Takayuki 'January June' Suwa
> > wrote:
> >> ;; after (prereq. TARGET_MINMAX)
> >> test0:
> >> movi.n a9, 1
> >> minua2,
reminder: ready for commit?
- Javier
On Wed 23. Aug 2023 at 15:02, Javier Martinez <
javier.martinez.bugzi...@gmail.com> wrote:
> On Tue, Aug 22, 2023 at 7:50 PM Jason Merrill wrote:
> > You still need an update to doc/extend.texi for this additional use of
> > the attribute. Sorry I didn't
Committed as "obvious" to master.
--Philipp.
On Wed, 6 Sept 2023 at 12:04, Christoph Muellner <
christoph.muell...@vrull.eu> wrote:
> From: Christoph Müllner
>
> The test was introduced recently and tests a RV64-only feature.
> However, when testing an RV32 compiler, the test gets executed as
When multilib is enabled, the c++ header directory of the default multilib
variant needs to be linked to the toplevel since g++ does not search the
toplevel in this case.
libstdc++-v3/ChangeLog:
* configure.host: Register t-loongarch in tmake_file.
*
From: Christoph Müllner
The test was introduced recently and tests a RV64-only feature.
However, when testing an RV32 compiler, the test gets executed as well
and fails with "cc1: error: ABI requires '-march=rv32'".
This patch fixes this by adding '-mabi=lp64' (like it is done for
other
Hi Folks,
On the Darwin aarch64 port, we have a number of cleanup test fails (pretty much
corresponding to the [still open]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=39244). However, let’s assume
that bug could be a red herring..
the underlying reason is missing CFI for the set of the FP
gcc/ChangeLog:
* config.gcc: remove non-POSIX syntax "<<<".
---
gcc/config.gcc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gcc/config.gcc b/gcc/config.gcc
index b2fe7c7ceef..6d4c8becd28 100644
--- a/gcc/config.gcc
+++ b/gcc/config.gcc
@@ -5189,7 +5189,7 @@ case
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111232
--- Comment #2 from CVS Commits ---
The trunk branch has been updated by Lehua Ding :
https://gcc.gnu.org/g:9ee40b9a7bee83394fc7ba6fef71cb76d91b49c8
commit r14-3735-g9ee40b9a7bee83394fc7ba6fef71cb76d91b49c8
Author: Lehua Ding
Date: Mon Sep
This patch enables use of 'declare mapper' for 'target update' directives,
for each of C, C++ and Fortran.
There are some implementation choices here and some
"read-between-the-lines" consequences regarding this functionality,
as follows:
* It is possible to invoke a mapper which contains
This patch fix incorrect mode tieable between DI and V2SI which cause ICE
in RA.
PR target/111296
gcc/ChangeLog:
* config/riscv/riscv.cc (riscv_modes_tieable_p): Fix bug.
gcc/testsuite/ChangeLog:
* g++.target/riscv/rvv/base/pr111296.C: New test.
---
Hi Robin,
+# Return 1 if the we can build a vector example with proper -march flags
+# and the current target can execute it, 0 otherwise. Cache the result.
+
+proc check_effective_target_riscv_vector_hw { } {
+
+return [check_runtime riscv_vector_hw32 {
+int main (void)
+{
101 - 200 of 231 matches
Mail list logo
