Like ARM SVE and GCN, add RVV.
gcc/testsuite/ChangeLog:
* gcc.dg/vect/bb-slp-pr69907.c: Add RVV.
---
gcc/testsuite/gcc.dg/vect/bb-slp-pr69907.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/gcc/testsuite/gcc.dg/vect/bb-slp-pr69907.c
Committed, thanks Juzhe.
Pan
From: juzhe.zhong
Sent: Friday, October 13, 2023 1:39 PM
To: Li, Pan2
Cc: gcc-patches@gcc.gnu.org; Li, Pan2 ; Wang, Yanzhang
; kito.ch...@gmail.com
Subject: Re: [PATCH v1] RISC-V: Add test for FP iroundf auto vectorization
lgtm
Replied Message
From
lgtm Replied Message Frompan2...@intel.comDate10/13/2023 13:33 Togcc-patches@gcc.gnu.org Ccjuzhe.zh...@rivai.ai,pan2...@intel.com,yanzhang.w...@intel.com,kito.ch...@gmail.comSubject[PATCH v1] RISC-V: Add test for FP iroundf auto vectorization
From: Pan Li
The below FP API are supported already by sharing the same standard
name, as well as the machine mode.
int iroundf (float);
This patch would like to add the test cases for ensuring the
correctness.
gcc/testsuite/ChangeLog:
*
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111001
Oleg Endo changed:
What|Removed |Added
Last reconfirmed||2023-10-13
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54089
--- Comment #103 from Oleg Endo ---
(In reply to Alexander Klepikov from comment #102)
> Created attachment 55543 [details]
> Arithmetic right shift late expanding v2
>
> Here's the patch. I hope I did not miss anything.
>
Sorry, I've been
Hi, Richi.
As you suggest, I keep MAK_LEN_GATHER_LOAD (...,-1) format and support SLP for
that in V3:
https://gcc.gnu.org/pipermail/gcc-patches/2023-October/632846.html
Thanks.
juzhe.zh...@rivai.ai
From: Richard Biener
Date: 2023-10-12 19:14
To: juzhe.zh...@rivai.ai
CC: gcc-patches;
This patch fixes this following FAILs in RISC-V regression:
FAIL: gcc.dg/vect/vect-gather-1.c -flto -ffat-lto-objects scan-tree-dump vect
"Loop contains only SLP stmts"
FAIL: gcc.dg/vect/vect-gather-1.c scan-tree-dump vect "Loop contains only SLP
stmts"
FAIL: gcc.dg/vect/vect-gather-3.c -flto
> Date: Fri, 29 Sep 2023 16:37:21 -0600
> From: Jeff Law
> So this ends up looking a lot like the bits that I had to revert several
> weeks ago :-)
>
> The core issue we have is given an INSN the generic code will cost the
> SET_SRC and SET_DEST and sum them. But that's far from ideal on a
Committed with few changelog tweak :P
On Thu, Oct 12, 2023 at 3:37 PM 钟居哲 wrote:
>
> LGTM
>
>
> juzhe.zh...@rivai.ai
>
>
> From: Kito Cheng
> Date: 2023-10-13 02:40
> To: gcc-patches; kito.cheng; palmer; jeffreyalaw; rdapp; juzhe.zhong
> CC: Kito Cheng
> Subject:
On Thu, Jul 6, 2023 at 1:53 PM Uros Bizjak via Gcc-patches
wrote:
>
> On Thu, Jul 6, 2023 at 3:14 AM liuhongt wrote:
> >
> > For testcase
> >
> > void __cond_swap(double* __x, double* __y) {
> > bool __r = (*__x < *__y);
> > auto __tmp = __r ? *__x : *__y;
> > *__y = __r ? *__y : *__x;
> >
Committed, thanks Juzhe.
Pan
From: juzhe.zh...@rivai.ai
Sent: Friday, October 13, 2023 10:26 AM
To: Li, Pan2 ; gcc-patches
Cc: Li, Pan2 ; Wang, Yanzhang ;
kito.cheng
Subject: Re: [PATCH v1] RISC-V: Leverage stdint-gcc.h for RVV test cases
LGTM。
LGTM。
juzhe.zh...@rivai.ai
From: pan2.li
Date: 2023-10-13 10:22
To: gcc-patches
CC: juzhe.zhong; pan2.li; yanzhang.wang; kito.cheng
Subject: [PATCH v1] RISC-V: Leverage stdint-gcc.h for RVV test cases
From: Pan Li
Leverage stdint-gcc.h for the int64_t types instead of typedef.
Or we may
From: Pan Li
Leverage stdint-gcc.h for the int64_t types instead of typedef.
Or we may have conflict with stdint-gcc.h in somewhere else.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/rvv/autovec/unop/math-llrint-0.c: Include
stdint-gcc.h for int types.
*
OK.
juzhe.zh...@rivai.ai
From: pan2.li
Date: 2023-10-13 09:38
To: gcc-patches
CC: juzhe.zhong; pan2.li; yanzhang.wang; kito.cheng
Subject: [PATCH v1] RISC-V: Support FP lfloor/lfloorf auto vectorization
From: Pan Li
This patch would like to support the FP lfloor/lfloorf auto vectorization.
On 10/12/23 17:04, Marek Polacek wrote:
Bootstrapped/regtested on x86_64-pc-linux-gnu, ok for trunk?
-- >8 --
My recent patch introducing cp_fold_immediate_r caused exponential
compile time with nested COND_EXPRs. The problem is that the COND_EXPR
case recursively walks the arms of a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111600
JuzheZhong changed:
What|Removed |Added
CC||juzhe.zhong at rivai dot ai
--- Comment
From: Pan Li
This patch would like to support the FP lfloor/lfloorf auto vectorization.
* long lfloor (double) for rv64
* long lfloorf (float) for rv32
Due to the limitation that only the same size of data type are allowed
in the vectorier, the standard name lfloormn2 only act on DF => DI for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108315
--- Comment #21 from Rui Ueyama ---
I fixed several issues in mold related to POWER10 compatibility, and all its
unit tests pass on gcc120! I also confirmed that mold can now bootstrap itself
with `-mcpu=power10`. So I believe it's now usable
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111424
--- Comment #3 from Chenghui Pan ---
vect.exp is enabled in master branch for now, but there's some
check_effective_target procs in gcc/testsuite/lib/target-supports.exp that
seems need modifying for enabling more vectorization tests.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107704
--- Comment #5 from Oleg Endo ---
(In reply to Jeffrey A. Law from comment #2)
> ACK. And as I mentioned, the RTL form looks like it ought to be caught by
> the SH specific code to optimize T reg handling. I don't care enough about
> the SH
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111784
Kewen Lin changed:
What|Removed |Added
Summary|[14 Regression] aarch64:|[14 Regression] aarch64:
Sure thing, thanks a lot and will follow the guidance.
Pan
From: Kito Cheng
Sent: Thursday, October 12, 2023 10:42 PM
To: Li, Pan2
Cc: 钟居哲 ; gcc-patches ; Wang,
Yanzhang
Subject: Re: [PATCH v1] RISC-V: Support FP llrint auto vectorization
I would prefer first approach since it no changes
Snapshot gcc-11-20231012 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/11-20231012/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 11 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
LGTM
juzhe.zh...@rivai.ai
From: Kito Cheng
Date: 2023-10-13 02:40
To: gcc-patches; kito.cheng; palmer; jeffreyalaw; rdapp; juzhe.zhong
CC: Kito Cheng
Subject: [PATCH v2] RISC-V: Fix the riscv_legitimize_poly_move issue on targets
where the minimal VLEN exceeds 512.
riscv_legitimize_poly_move
LGTM。
juzhe.zh...@rivai.ai
From: pan2.li
Date: 2023-10-12 22:17
To: gcc-patches
CC: juzhe.zhong; pan2.li; yanzhang.wang; kito.cheng
Subject: [PATCH v1] RISC-V: Support FP lceil/lceilf auto vectorization
From: Pan Li
This patch would like to support the FP lceil/lceilf auto vectorization.
On Thu, 12 Oct 2023, 17:11 Jeff Law, wrote:
>
>
> On 10/12/23 08:38, Christophe Lyon wrote:
> > LGTM but I'm not a maintainer ;-)
> LGTM to as well -- I usually try to stay out of libstdc++, but this
> looks simple enough. Both patches in this series are OK.
>
Thanks for stepping in, Jeff. The
On Thu, Oct 12, 2023 at 04:24:00PM -0400, Jason Merrill wrote:
> On 10/12/23 04:53, Nathaniel Shead wrote:
> > On Wed, Oct 11, 2023 at 12:48:12AM +1100, Nathaniel Shead wrote:
> > > On Mon, Oct 09, 2023 at 04:46:46PM -0400, Jason Merrill wrote:
> > > > On 10/8/23 21:03, Nathaniel Shead wrote:
> >
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111782
Andrew Pinski changed:
What|Removed |Added
Summary|[11/12/13/14 Regression]|[11/12/13/14 Regression]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83282
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Last reconfirmed|2017-12-05 00:00:00 |2023-10-12
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111782
Andrew Pinski changed:
What|Removed |Added
Keywords||ra
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111786
--- Comment #3 from Lukas Grätz ---
(In reply to Jakub Jelinek from comment #1)
> We completely intentionally don't emit tail calls to noreturn functions, so
> that e.g. in case of abort one doesn't need to virtually reconstruct
> backtrace.
>
Bootstrapped/regtested on x86_64-pc-linux-gnu, ok for trunk?
-- >8 --
My recent patch introducing cp_fold_immediate_r caused exponential
compile time with nested COND_EXPRs. The problem is that the COND_EXPR
case recursively walks the arms of a COND_EXPR, but after processing
both arms it
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111791
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2023-10-12
CC|
Hi,
on riscv insn-emit.cc has grown to over 1.2 mio lines of code and
compiling it takes considerable time.
Therefore, this patch adjust genemit to create ten files insn-emit-1.cc
to insn-emit-10.cc. In order to do so it first counts the number of
available patterns, calculates the number of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86120
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |DUPLICATE
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66969
anlauf at gcc dot gnu.org changed:
What|Removed |Added
CC||simon.kluepfel at gmail dot
On 10/12/23 04:53, Nathaniel Shead wrote:
On Wed, Oct 11, 2023 at 12:48:12AM +1100, Nathaniel Shead wrote:
On Mon, Oct 09, 2023 at 04:46:46PM -0400, Jason Merrill wrote:
On 10/8/23 21:03, Nathaniel Shead wrote:
Ping for https://gcc.gnu.org/pipermail/gcc-patches/2023-September/631203.html
+
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111778
--- Comment #3 from CVS Commits ---
The master branch has been updated by Michael Meissner :
https://gcc.gnu.org/g:611eef7609f732db65c119a7eab6d50a5fdd5985
commit r14-4600-g611eef7609f732db65c119a7eab6d50a5fdd5985
Author: Michael Meissner
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111791
Bug ID: 111791
Summary: RISC-V: Strange loop vectorizaion on popcount function
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111783
--- Comment #3 from anlauf at gcc dot gnu.org ---
(In reply to anlauf from comment #2)
> This leaves ABORT and EXIT to deal with.
Speaking to myself:
subroutine s1()
call exit(1)
stop 98
end
subroutine s2()
call abort
stop 99
end
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111783
anlauf at gcc dot gnu.org changed:
What|Removed |Added
CC||anlauf at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111660
--- Comment #12 from Marek Polacek ---
Candidate fix:
--- a/gcc/cp/cp-gimplify.cc
+++ b/gcc/cp/cp-gimplify.cc
@@ -1072,7 +1072,7 @@ cp_fold_immediate_r (tree *stmt_p, int *walk_subtrees,
void *data_)
/* We're done here. Don't clear
On Tue, 26 Sep 2023, Patrick Palka wrote:
> Bootstrapped and regtested on x86_64-pc-linux-gnu, does this look OK
> for trunk?
>
> -- >8 --
>
> This follow-up patch removes some more repetition of the type-dependent
On second thought there's no good reason to split these patches into a two
part
On Thu, Oct 12, 2023 at 06:37:00PM +0200, Tobias Burnus wrote:
> libgomp.texi: Clarify OMP_TARGET_OFFLOAD=mandatory
>
> In OpenMP 5.0/5.1, the semantic of OMP_TARGET_OFFLOAD=mandatory was
> insufficiently specified; 5.2 clarified this with extensions/clarifications
> (omp_initial_device,
riscv_legitimize_poly_move was expected to ensure the poly value is at most 32
times smaller than the minimal VLEN (32 being derived from '4096 / 128').
This assumption held when our mode modeling was not so precisely defined.
However, now that we have modeled the mode size according to the
but anyway, I don't have a strong opinion for either way, just go
ahead no matter which one you choose.
On Thu, Oct 12, 2023 at 11:28 AM Kito Cheng wrote:
>
> Sorry for the late comment after Jeff say ok, but I guess we may
> consider add "-fno-schedule-insns -fno-schedule-insns2" to avoid
>
Sorry for the late comment after Jeff say ok, but I guess we may
consider add "-fno-schedule-insns -fno-schedule-insns2" to avoid
disturbing from schedule like some of our test case in
gcc/testsuite/gcc.target/riscv/rvv?
On Thu, Oct 12, 2023 at 9:12 AM Jeff Law wrote:
>
>
>
> On 10/12/23 07:06,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=27504
Andrew Pinski changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |pinskia at gcc dot
gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=27504
Andrew Pinski changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #5 from Andrew
> The support to elide calls to allocation functions in DCE runs into
> the issue that when implementations are discovered noreturn we end
> up DCEing the calls anyway, leaving blocks without termination and
> without outgoing edges which is both invalid IL and wrong-code when
> as in the example
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88280
Andrew Pinski changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
On Wed, 11 Oct 2023, Ken Matsui wrote:
> Since RID_MAX soon reaches 255 and all traits are used approximately once in
> a C++ translation unit, this patch instead uses only RID_TRAIT_EXPR and
> RID_TRAIT_TYPE for all traits and uses gperf to look up the specific trait.
>
>
Now that abi breakage is fixed and hoping that Friday is review day :-)
Ping !
On 17/09/2023 22:41, François Dumont wrote:
libstdc++: [_Hashtable] Avoid redundant usage of rehash policy
Bypass usage of __detail::__distance_fwd and check for need to rehash
when assigning an initializer_list
On 10/9/23 08:59, Juzhe-Zhong wrote:
These cases won't check SLP for load_lanes support target.
Add vectorization check for situations.
gcc/testsuite/ChangeLog:
* gcc.dg/vect/pr97832-2.c: Add vectorization check.
* gcc.dg/vect/pr97832-3.c: Ditto.
*
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111790
--- Comment #1 from Tinko Sebastian Bartels ---
A command line that can trigger the behavior is
g++ main.cpp
One of the versions for which it occurs is
g++ -v
Es werden eingebaute Spezifikationen verwendet.
COLLECT_GCC=g++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111790
Bug ID: 111790
Summary: Unwarranted missing template keyword warning
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
I noticed that while OMP_DEFAULT_DEVICE was updated a ref to
OMP_TARGET_OFFLOAD (→ mandatory case) was missing. And
OMP_TARGET_OFFLOAD wasn't updated at all for those changes.
I hope the new version is clearer.
Current versions:
On 10/11/23 10:55, Florian Weimer wrote:
The updated test cases still reproduce the bugs with old compilers.
gcc/testsuite/
* gcc.c-torture/compile/pc44485.c (func_21): Add missing cast.
* gcc.c-torture/compile/pr106101.c: Use builtins to avoid
calls to undeclared
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108993
Andrew Pinski changed:
What|Removed |Added
CC||iamsupermouse at mail dot ru
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111771
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|NEW
On 10/11/23 10:53, Florian Weimer wrote:
These changes are assumed not to interfere with the test objective,
but it was not possible to reproduce the historic test case failures
(with or without the modification here).
gcc/testsuite/
* gcc.c-torture/compile/2105-1.c: Add missing
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111622
--- Comment #6 from Andrew Macleod ---
Interesting.
The "fix" turns out to be:
commit 9ea74d235c7e7816b996a17c61288f02ef767985
Author: Richard Biener
Date: Thu Sep 14 09:31:23 2023 +0200
tree-optimization/111294 - better DCE after
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111789
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111789
--- Comment #2 from Andrew Pinski ---
#0 0x00402521 in func_4 (p_5=, p_6=p_6@entry=0x406044
, p_7=21909, p_8=, p_9=398526839) at
/home/cuisk/gcc/tmp/a.c:134
=> 0x00402521 <+193>: mov(%r9),%r11d
r9 0x40
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111789
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |14.0
Summary|Segmentation
On 10/11/23 10:42, Florian Weimer wrote:
Add -std=gnu89 to some tests which evidently target C89-only language
features.
gcc/testsuite/
* gcc.c-torture/compile/920501-11.c: Compile with -std=gnu89.
* gcc.c-torture/compile/920501-23.c: Likewise.
*
Yeah, will send v2 today
Jeff Law 於 2023年10月12日 週四 09:15 寫道：
>
>
> On 10/11/23 17:17, Kito Cheng wrote:
> > Yeah, I'll take you suggestion and go ahead, Robin's suggestion is
> > great but it's just a little too magic :P
> So there'll be a V2 of this patch, right? Just want to make sure state
On 10/11/23 17:17, Kito Cheng wrote:
Yeah, I'll take you suggestion and go ahead, Robin's suggestion is
great but it's just a little too magic :P
So there'll be a V2 of this patch, right? Just want to make sure state
is correct in patchwork.
jeff
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111789
--- Comment #1 from CTC <19373742 at buaa dot edu.cn> ---
Created attachment 56100
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56100=edit
The compiler output
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111789
Bug ID: 111789
Summary: Segmentation fault with '-O3 -fno-inline
-fno-toplevel-reorder'
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
On 10/12/23 07:06, Christoph Muellner wrote:
From: Christoph Müllner
Fixes: c1bc7513b1d7 ("RISC-V: const: hide mvconst splitter from IRA")
A recent change broke the xtheadcondmov-indirect tests, because the order of
emitted instructions changed. Since the test is too strict when testing
On 10/11/23 19:37, Hans-Peter Nilsson wrote:
```
foo2:
sext.w a6,a1 <-- this goes away
beq a1,zero,.L4
li a5,0
li a0,0
.L3:
addwa4,a2,a5
addwa5,a3,a5
addwa0,a4,a0
bltua5,a6,.L3
On 10/12/23 08:38, Christophe Lyon wrote:
LGTM but I'm not a maintainer ;-)
LGTM to as well -- I usually try to stay out of libstdc++, but this
looks simple enough. Both patches in this series are OK.
jeff
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111788
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2023-10-12
Ever confirmed|0
On 10/12/23 03:41, Alex Coplan wrote:
Hi,
The description of the REG_NOALIAS note in reg-notes.def isn't quite
right. It describes it as being attached to call insns, but it is
instead attached to a move insn receiving the return value from a call.
This can be seen by looking at the code in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111788
Bug ID: 111788
Summary: g++ DWARF for void foo(...) missing unspecified
parameters DIE
Product: gcc
Version: 13.2.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111783
Andrew Pinski changed:
What|Removed |Added
Summary|'exit' intrinsic should be |'exit' intrinsic should be
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80917
Andrew Pinski changed:
What|Removed |Added
Known to work||14.0
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=39627
--- Comment #3 from Paul Thomas ---
Created attachment 56098
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56098=edit
Evidence for replies in last attachment
As promised in the previous entry in this PR.
Paul
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=39627
Paul Thomas changed:
What|Removed |Added
CC||pault at gcc dot gnu.org
--- Comment #2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111755
Andrew Pinski changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111784
--- Comment #1 from Alex Coplan ---
More context/details about the issue in 8/10 of the original patch series (that
the above revision comes from):
https://gcc.gnu.org/pipermail/gcc-patches/2023-September/630234.html
Hi!
While my wide_int patch bootstrapped/regtested fine when I used GCC 12
as system gcc, apparently it doesn't with GCC 11 and older or clang++.
For GCC before PR96555 C++ DR1315 implementation the compiler complains
about template argument involving template parameters, for clang++ the
same +
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111787
--- Comment #3 from CVS Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:53a94071fa9e90e268a94adbdc903bd868ddeec1
commit r14-4596-g53a94071fa9e90e268a94adbdc903bd868ddeec1
Author: Jakub Jelinek
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111787
--- Comment #2 from seurer at gcc dot gnu.org ---
This system is on RHEL 8 which has gcc 8.5 as the distro compiler.
And yes, the patch worked.
On 10/12/23 04:05, Mary Bennett wrote:
gcc/ChangeLog:
* doc/extend.texi: Change subsubsection to subsection for
CORE-V built-ins.
Thanks for jumping on it quickly. I added the PR marker to the
ChangeLog entry (bugzilla integration) and pushed this to the trunk.
jeff
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111777
Jeffrey A. Law changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111777
--- Comment #10 from CVS Commits ---
The master branch has been updated by Jeff Law :
https://gcc.gnu.org/g:e99ad401f84ca6cd2717a58a116e44274d55da70
commit r14-4595-ge99ad401f84ca6cd2717a58a116e44274d55da70
Author: Mary Bennett
Date: Thu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111787
--- Comment #1 from Jakub Jelinek ---
Does
2023-10-12 Jakub Jelinek
PR bootstrap/111787
* tree.h (wi::int_traits ::needs_write_val_arg): New
static data member.
(int_traits >::needs_write_val_arg): Likewise.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111787
Bug ID: 111787
Summary: [14 regression] xxx breaks build
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: bootstrap
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111777
--- Comment #9 from seurer at gcc dot gnu.org ---
That patch works fine on a system where the build was failing.
I would prefer first approach since it no changes other than adding
testcase, that might confusing other people.
Li, Pan2 於 2023年10月11日 週三 23:12 寫道：
> Sorry for misleading here.
>
> When implement the llrint after lrint, I realize llrint (DF => SF) are
> supported by the lrint already in the
LGTM but I'm not a maintainer ;-)
On Thu, 12 Oct 2023 at 04:22, Hans-Peter Nilsson wrote:
>
> Ping.
>
> > From: Hans-Peter Nilsson
> > Date: Wed, 4 Oct 2023 19:08:16 +0200
> >
> > s/atomic-exchange/atomic-cmpxchg-word/g.
> > Tested as v1.
> >
> > Ok to commit?
> > -- >8 --
> > These tests
LGTM but I'm not a maintainer ;-)
On Thu, 12 Oct 2023 at 04:21, Hans-Peter Nilsson wrote:
>
> Ping.
>
> > From: Hans-Peter Nilsson
> > Date: Wed, 4 Oct 2023 19:04:55 +0200
> >
> > > From: Hans-Peter Nilsson
> > > Date: Wed, 4 Oct 2023 17:15:28 +0200
> >
> > > New version coming up.
> >
> >
Tamar Christina writes:
> Hi All,
>
> At the moment, trying to use -march=armv9-a with any ACLE header such as
> arm_neon.h results in rows and rows of warnings saying:
>
> : warning: "__ARM_ARCH" redefined
> : note: this is the location of the previous definition
>
> This is obviously not useful
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52994
Paul Thomas changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=39627
Bug 39627 depends on bug 52994, which changed state.
Bug 52994 Summary: [OOP] [F08] internal compiler error: in
gfc_trans_assignment_1, at fortran/trans-expr.c:6881
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52994
What|Removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111786
Xi Ruoyao changed:
What|Removed |Added
Resolution|INVALID |DUPLICATE
--- Comment #2 from Xi Ruoyao
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=10837
Xi Ruoyao changed:
What|Removed |Added
CC||lukas.graetz@tu-darmstadt.d
1 - 100 of 201 matches
Mail list logo
