https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113288
--- Comment #6 from Haochen Jiang ---
Fixed on trunk.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113288
--- Comment #5 from GCC Commits ---
The master branch has been updated by Haochen Jiang :
https://gcc.gnu.org/g:4ab847b354ee9e13e6052f78f49f575eae3abf3f
commit r14-7168-g4ab847b354ee9e13e6052f78f49f575eae3abf3f
Author: Haochen Jiang
Date:
This test should pass no matter how we adjust cost model.
Remove -fno-vect-cost-model.
Committed.
gcc/testsuite/ChangeLog:
* gcc.target/riscv/rvv/autovec/fold-min-poly.c: Remove
-fno-vect-cost-model
---
gcc/testsuite/gcc.target/riscv/rvv/autovec/fold-min-poly.c | 2 +-
1 file
Bootstrapped and tested on x86_64-linux with no regressions.
I'm still getting used to things so let me know if the change log
entries are excessive, thanks.From 9dc168e7bcbbd7d515fa28cb9cae28ec113fae0f Mon Sep 17 00:00:00 2001
From: Waffl3x
Date: Thu, 11 Jan 2024 14:32:46 -0700
Subject: [PATCH]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55004
Bug 55004 depends on bug 110997, which changed state.
Bug 110997 Summary: [13 Regression] internal compiler error: in
cxx_eval_constant_expression, at cp/constexpr.cc:8005
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110997
What
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107687
Bug 107687 depends on bug 110997, which changed state.
Bug 110997 Summary: [13 Regression] internal compiler error: in
cxx_eval_constant_expression, at cp/constexpr.cc:8005
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110997
What
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110997
Richard Biener changed:
What|Removed |Added
Resolution|FIXED |---
Summary|[13/14
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113344
Richard Biener changed:
What|Removed |Added
Status|NEW |ASSIGNED
ok.
juzhe.zh...@rivai.ai
From: Jun Sha (Joshua)
Date: 2024-01-12 11:24
To: gcc-patches
CC: jim.wilson.gcc; palmer; andrew; philipp.tomsich; jeffreyalaw;
christoph.muellner; juzhe.zhong; Jun Sha (Joshua); Jin Ma; Xianmiao Qu
Subject: [PATCH v5] RISC-V: Rewrite some instructions using ASM
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110997
--- Comment #5 from Andrew Pinski ---
Hmm, the target milestone is set to 13.3.0 but only references patches which
have gone in for gcc 14 only
ok.
juzhe.zh...@rivai.ai
From: Jun Sha (Joshua)
Date: 2024-01-12 11:23
To: gcc-patches
CC: jim.wilson.gcc; palmer; andrew; philipp.tomsich; jeffreyalaw;
christoph.muellner; juzhe.zhong; Jun Sha (Joshua); Jin Ma; Xianmiao Qu
Subject: [PATCH v6] RISC-V: Fix register overlap issue for some
ok
juzhe.zh...@rivai.ai
From: Jun Sha (Joshua)
Date: 2024-01-12 11:22
To: gcc-patches
CC: jim.wilson.gcc; palmer; andrew; philipp.tomsich; jeffreyalaw;
christoph.muellner; juzhe.zhong; Jun Sha (Joshua); Jin Ma; Xianmiao Qu
Subject: [PATCH v6] RISC-V: Handle differences between XTheadvector
OK.
juzhe.zh...@rivai.ai
From: Jun Sha (Joshua)
Date: 2024-01-12 11:21
To: gcc-patches
CC: jim.wilson.gcc; palmer; andrew; philipp.tomsich; jeffreyalaw;
christoph.muellner; juzhe.zhong; Jun Sha (Joshua); Jin Ma; Xianmiao Qu
Subject: [PATCH v5] RISC-V: Adds the prefix "th." for the
This patch needs kito review. I can't approve that.
juzhe.zh...@rivai.ai
From: Jun Sha (Joshua)
Date: 2024-01-12 11:20
To: gcc-patches
CC: jim.wilson.gcc; palmer; andrew; philipp.tomsich; jeffreyalaw;
christoph.muellner; juzhe.zhong; kito.cheng; Jun Sha (Joshua); Jin Ma; Xianmiao
Qu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113126
Hongtao Liu changed:
What|Removed |Added
CC||liuhongt at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113347
Richard Biener changed:
What|Removed |Added
Summary|ICE during gimplification |[13 Regression] ICE during
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113347
Richard Biener changed:
What|Removed |Added
Keywords||ice-on-valid-code,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113347
--- Comment #1 from Richard Biener ---
Created attachment 57047
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57047=edit
preprocessed source
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113347
Bug ID: 113347
Summary: ICE during gimplification building TVM
Product: gcc
Version: 13.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112280
Richard Biener changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112280
--- Comment #10 from GCC Commits ---
The master branch has been updated by Richard Biener :
https://gcc.gnu.org/g:655b6cb1ea3a0e23124d77dccd5d174ac59c429c
commit r14-7166-g655b6cb1ea3a0e23124d77dccd5d174ac59c429c
Author: Richard Biener
Date:
Am Do., 11. Jan. 2024 um 21:23 Uhr schrieb Jonathan Wakely :
>
> Tested x86_64-linux. Does this look better now?
Yes, thank you.
- Daniel
Hi,
On P9 "setb" is used to set the result of block compare. So it works
with m32 and mpowerpc64. On P8, carry bit is used. So it can't work
with m32 and mpowerpc64. This patch enables block compare expand for
m32 and mpowerpc64 on P9.
Bootstrapped and tested on x86 and powerpc64-linux BE and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113346
--- Comment #1 from Richard Biener ---
This was with r14-7159-g1a80e9558dd7fe
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113346
Richard Biener changed:
What|Removed |Added
Keywords||ice-on-valid-code, ra
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113346
Bug ID: 113346
Summary: [14 Regression] epiphany-elf build failure
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
Add a depth parameter to limit recursion of vec_slp_has_scalar_use.
Feng
---
.../gcc.target/aarch64/bb-slp-pr113091.c | 22 ++
gcc/tree-vect-slp.cc | 207 ++
2 files changed, 190 insertions(+), 39 deletions(-)
create mode 100644
On Wed, 10 Jan 2024, liuhongt wrote:
> To override -fcf-protection, -fcf-protection=none needs to be added
> and then with -fcf-protection=xxx.
I'm afraid I am struggling with the English of this, but need more time to
untangle and suggest an alternative.
For the time being I pushed the
On Linux/x86_64,
b5476e4c881b0d2bfbbfb84ee38d791123acf8e1 is the first bad commit
commit b5476e4c881b0d2bfbbfb84ee38d791123acf8e1
Author: Julian Brown
Date: Mon Nov 15 02:23:49 2021 -0800
OpenMP: lvalue parsing for map/to/from clauses (C)
caused
FAIL: gcc.dg/gomp/bad-array-section-c-3.c
Exception handling on nios2-linux-gnu with -fpic has been broken since
revision 790854ea7670f11c14d431c102a49181d2915965, "Use _dl_find_object
in _Unwind_Find_FDE". For whatever reason, this doesn't work on nios2.
Nios2 uses the GOT address as the base for DW_EH_PE_datarel
relocations in PIC;
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113312
--- Comment #16 from H.J. Lu ---
I updated users/hjl/pr113312/master branch to handle function pointers.
On Thu, 2024-01-04 17:28:02 +0100, Georg-Johann Lay wrote:
> This fixes the avr-specific attributes io, io_low and address,
> that are all basically the same except that io and io_low imply
> assertions on allowed addressing modes.
> --- a/gcc/config/avr/avr.cc
> +++ b/gcc/config/avr/avr.cc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113345
Hongtao Liu changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
There are some xtheadvector instructions that differ from RVV1.0
apart from simply adding "th." prefix. For example, RVV1.0
load/store instructions will have SEW while xtheadvector not;
RVV1.0 will have "o" for indexed-ordered store instructions while
xtheadvecotr not; xtheadvector and RVV1.0 have
For th.vmadc/th.vmsbc as well as narrowing arithmetic instructions
and floating-point compare instructions, an illegal instruction
exception will be raised if the destination vector register overlaps
a source vector register group.
To handle this issue, we add an attribute "spec_restriction" to
This patch only involves the generation of xtheadvector
special load/store instructions and vext instructions.
gcc/ChangeLog:
* config/riscv/riscv-vector-builtins-bases.cc
(class th_loadstore_width): Define new builtin bases.
(class th_extract): Define new builtin bases.
This patch is to handle the differences in instruction generation
between Vector and XTheadVector. In this version, we only support
partial xtheadvector instructions that leverage directly from current
RVV1.0 with simple adding "th." prefix. For different name xtheadvector
instructions but share
This patch adds th. prefix to all XTheadVector instructions by
implementing new assembly output functions. We only check the
prefix is 'v', so that no extra attribute is needed.
gcc/ChangeLog:
* config/riscv/riscv-protos.h (riscv_asm_output_opcode):
Add new function to add
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113039
Hongtao Liu changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
This patch is to introduce basic XTheadVector support
(march string parsing and a test for __riscv_xtheadvector)
according to https://github.com/T-head-Semi/thead-extension-spec/
gcc/ChangeLog:
* common/config/riscv/riscv-common.cc
(riscv_subset_list::parse): Add new vendor
On Thu, Jan 11, 2024 at 12:06 AM H.J. Lu wrote:
>
> On Tue, Jan 9, 2024 at 6:02 PM liuhongt wrote:
> >
> > After r14-2692-g1c6231c05bdcca, the option is defined as EnumSet and
> > -fcf-protection=branch won't unset any others bits since they're in
> > different groups. So to override
On Fri, Jan 12, 2024 at 10:55 AM Jiang, Haochen wrote:
>
> > -Original Message-
> > From: Richard Biener
> > Sent: Thursday, January 11, 2024 4:19 PM
> > To: Liu, Hongtao
> > Cc: Jiang, Haochen ; gcc-patches@gcc.gnu.org;
> > ubiz...@gmail.com; bur...@net-b.de; san...@codesourcery.com
>
This patch series presents gcc implementation of the XTheadVector
extension [1].
[1] https://github.com/T-head-Semi/thead-extension-spec/
For some vector patterns that cannot be avoided, we use
"!TARGET_XTHEADVECTOR" to disable them in order not to
generate instructions that xtheadvector does
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113039
--- Comment #4 from GCC Commits ---
The master branch has been updated by hongtao Liu :
https://gcc.gnu.org/g:75ed46558a2e085ba12641a47112e37f114faee0
commit r14-7164-g75ed46558a2e085ba12641a47112e37f114faee0
Author: liuhongt
Date: Mon Jan
Hi Alexandre,
on 2024/1/11 17:05, Alexandre Oliva wrote:
> On Jan 7, 2024, "Kewen.Lin" wrote:
>
>> As PR113100 shows, the unbiasing introduced by r14-6737 can
>> cause the scrubbing to overrun and screw some critical data
>> on stack like saved toc base consequently cause segfault on
>> Power.
Committed, thanks Juzhe.
Pan
From: juzhe.zh...@rivai.ai
Sent: Friday, January 12, 2024 10:54 AM
To: Li, Pan2 ; gcc-patches
Cc: Li, Pan2 ; Wang, Yanzhang ;
kito.cheng
Subject: Re: [PATCH v1] RISC-V: Update the comments of riscv_v_ext_mode_p [NFC]
OK
> -Original Message-
> From: Richard Biener
> Sent: Thursday, January 11, 2024 4:19 PM
> To: Liu, Hongtao
> Cc: Jiang, Haochen ; gcc-patches@gcc.gnu.org;
> ubiz...@gmail.com; bur...@net-b.de; san...@codesourcery.com
> Subject: Re: [PATCH] i386: Add AVX10.1 related macros
>
> On Thu, Jan
OK
juzhe.zh...@rivai.ai
From: pan2.li
Date: 2024-01-12 10:52
To: gcc-patches
CC: juzhe.zhong; pan2.li; yanzhang.wang; kito.cheng
Subject: [PATCH v1] RISC-V: Update the comments of riscv_v_ext_mode_p [NFC]
From: Pan Li
gcc/ChangeLog:
* config/riscv/riscv.cc (riscv_v_ext_mode_p): Update
From: Pan Li
gcc/ChangeLog:
* config/riscv/riscv.cc (riscv_v_ext_mode_p): Update the
comments of predicate func riscv_v_ext_mode_p.
Signed-off-by: Pan Li
---
gcc/config/riscv/riscv.cc | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git
> -Original Message-
> From: Jiang, Haochen
> Sent: Friday, January 12, 2024 10:26 AM
> To: gcc-patches@gcc.gnu.org
> Cc: Liu, Hongtao ; ubiz...@gmail.com
> Subject: [PATCH] i386: Remove redundant move in vnni pattern
>
> Hi all,
>
> This patch removes all redundant set in vnni
Committed, thanks.
From: juzhe.zh...@rivai.ai
Date: 2024-01-12 09:38
To: wangfeng; gcc-patches
CC: kito.cheng; jeffreyalaw; wangfeng
Subject: Re: [PATCH] RISC-V: Modify ABI-name length of vfloat16m8_t
Good catch. LGTM.
juzhe.zh...@rivai.ai
From: Feng Wang
Date: 2024-01-12 09:35
To:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113345
--- Comment #1 from Hongtao Liu ---
>
> maybe we can just refactor the pattern as blow, then combine can generate
> the pattern for us.
>
> 22115(define_insn "_psign3"
> 22116 [(set (match_operand:VI124_AVX2 0 "register_operand" "=x,x")
>
Hi all,
This patch removes all redundant set in vnni patterns.
Ok for trunk?
Thx,
Haochen
gcc/ChangeLog:
* config/i386/sse.md (sdot_prod): Remove redundant SET.
(usdot_prod): Ditto.
(sdot_prod): Ditto.
(udot_prod): Ditto.
---
gcc/config/i386/sse.md | 4
1
Hi Richard,
Thanks so much for your comments.
>> patch.diff
>> diff --git a/gcc/config/rs6000/rs6000-string.cc
>> b/gcc/config/rs6000/rs6000-string.cc
>> index 7f777666ba9..4c9b2cbeefc 100644
>> --- a/gcc/config/rs6000/rs6000-string.cc
>> +++ b/gcc/config/rs6000/rs6000-string.cc
>> @@ -140,7
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113345
Bug ID: 113345
Summary: miss optimization for psign{b,w,d}.
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
1.Delete "dg-do run".
When binutils do not support vectorization, an error occurs during
the assembly phase that does not recognize vector instructions.
2.Added "-mlsx" option for vectorization on LoongArch.
gcc/testsuite/ChangeLog:
* gcc.dg/tree-ssa/gen-vect-2.c: Remove the program's
gcc/testsuite/ChangeLog:
* gcc.dg/pr104992.c: Added additional "-mlsx" compilation options.
* gcc.dg/signbit-2.c: Dito.
* gcc.dg/tree-ssa/scev-16.c: Dito.
* gfortran.dg/graphite/vect-pr40979.f90: Dito.
* gfortran.dg/vect/fast-math-mgrid-resid.f: Dito.
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113338
--- Comment #2 from Brad Richardson ---
The addition of CFI_cdesc_t in 2018 means it is possible to pass
non-interoperable types to C so long as it doesn't need to know anything about
its type (i.e. doesn't try to modify or copy it). And yes,
Pushed to r14-7160 and r14-7161.
在 2024/1/11 下午7:36, Li Wei 写道:
We found that the current combine optimization pass in gcc cannot handle
the following redundant sign extension situations:
(insn 77 76 78 5 (set (reg:SI 143)
(plus:SI (subreg/s/u:SI (reg/v:DI 104 [ len ]) 0)
I found an issue bootstrapping GCC with -mcmodel=extreme in BOOT_CFLAGS:
we need a target hook to tell the generic code
UNSPEC_LA_PCREL_64_PART{1,2} are just a wrapper around symbols, or we'll
see millions lines of messages like
../../gcc/gcc/tree.h:4171:1: note: non-delegitimized UNSPEC
Good catch. LGTM.
juzhe.zh...@rivai.ai
From: Feng Wang
Date: 2024-01-12 09:35
To: gcc-patches
CC: kito.cheng; jeffreyalaw; juzhe.zhong; Feng Wang
Subject: [PATCH] RISC-V: Modify ABI-name length of vfloat16m8_t
The length of vfloat16m8_t ABI-name should be 17.
gcc/ChangeLog:
*
The length of vfloat16m8_t ABI-name should be 17.
gcc/ChangeLog:
* config/riscv/riscv-vector-builtins.def (vfloat16m8_t):Modify ABI-name
length of vfloat16m8_t
---
gcc/config/riscv/riscv-vector-builtins.def | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113312
--- Comment #15 from H. Peter Anvin ---
That should be fine for this use case, obviously.
I should add the following: the reason the assembly stub isn't a problem for
FRED whereas it is a bit of a nuisance for IDT-style delivery is that with
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113312
--- Comment #14 from H.J. Lu ---
Here is a branch for __attribute__((no_callee_saved_registers)):
https://gitlab.com/x86-gcc/gcc/-/commits/users/hjl/pr113312/master
Calling a function with __attribute__((no_callee_saved_registers))
doesn't
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113344
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2024-01-12
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113344
--- Comment #3 from Andrew Pinski ---
https://gcc.gnu.org/pipermail/gcc-regression/2024-January/078983.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113344
--- Comment #1 from Andrew Pinski ---
Confirmed, it fails everywhere too.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102609
--- Comment #29 from waffl3x ---
https://cplusplus.github.io/CWG/issues/2789.html
My alteration to CWG2789 came up on reddit and I realized I should
probably post about it here.
Instead of:
"if both are non-static member functions, they have
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113258
--- Comment #25 from Jonathan Wakely ---
Fixed on trunk only so far.
On Thu, 11 Jan 2024, Jason Merrill wrote:
> Now in patch form!
It appears quite clear to me.
(At first I thought we need to escape the '&' in "[&] (tree arg)" as
"", but checking with validator.w3.org apparently not so in this
specific context.)
Gerald
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113344
Bug ID: 113344
Summary: [14 regression] gcc.dg/pr15784-1.c fails after
r14-7139-g897b95a12b7fe5
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity:
Hi!
On 2024-01-11T15:22:07+0100, Arthur Cohen wrote:
> Sorry about this - two simple changes to Makefile.def we had missed
> during our first libgrust/ patchset
I don't think those were "missed" but rather "intentionally omitted"?
I'll have to have a more detailed look.
(..., and almost no
Hi!
On 2024-01-11T15:22:07+0100, Arthur Cohen wrote:
> Sorry about this - two simple changes to Makefile.def we had missed
> during our first libgrust/ patchset
I don't think those were "missed" but rather "intentionally omitted"?
I'll have to have a more detailed look.
(..., and almost no
Hi.
This patch fixes the bug 113343.
I'm wondering if there's a better solution than using mpfr.
The only other solution I found is real_from_string, but that seems
overkill to convert the number to a string.
I could not find a better way to create a real value from a host
double.
If there's no
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113343
Bug ID: 113343
Summary: Float values are not correct when cross-compiling
Product: gcc
Version: 13.1.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Verify that if-conversion succeeded through noce_try_store_flag_mask, as
per PR rtl-optimization/105314, tightening the test case and making it
explicit.
gcc/testsuite/
* gcc.target/riscv/pr105314.c: Scan the RTL "ce1" pass too.
---
gcc/testsuite/gcc.target/riscv/pr105314.c |
The optimization levels pr105314.c is iterated over are needlessly
overridden with "-O2", limiting the coverage of the test case to that
level, perhaps with additional options the original optimization level
has been supplied with. We could prevent the extra iterations other
than "-O2" from
Hi,
Here's a pair of further pr105314.c changes I came up with in the course
of recent RISC-V if-conversion work. It's not entirely clear to me what
our policy is for Stages 3 and 4 when it comes to testsuite cleanups or
improvements, but I think it's worth sharing these updates anyway.
OK
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110065
Marek Polacek changed:
What|Removed |Added
CC||mpolacek at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113200
Jonathan Wakely changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55004
Bug 55004 depends on bug 113200, which changed state.
Bug 113200 Summary: std::char_traits::move is not constexpr when the
argument is a string literal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113200
What|Removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113200
--- Comment #12 from GCC Commits ---
The releases/gcc-12 branch has been updated by Jonathan Wakely
:
https://gcc.gnu.org/g:26a9e8cee4d20e5b08c0336439c8f69a2f06af1c
commit r12-10090-g26a9e8cee4d20e5b08c0336439c8f69a2f06af1c
Author: Jonathan
This fixes a regression introduced by the LWG 3809 change, so is needed
on trunk and gcc-13 and gcc-12.
Tested x86_64-linux and aarch64-linux.
-- >8 --
I implemented the resolution of LWG 3809 in r13-4364-ga64775a0edd469 but
more recently it was noted that the change causes possible truncation
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113342
--- Comment #2 from Andrew Pinski ---
Note there was a change between `clang 10` and `clang 11` which changed clang
into accepting the code. So I am 99% sure it is that paper which caused the
change ...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113342
--- Comment #1 from Andrew Pinski ---
Note MSVC has the same behavior as GCC here:
```
(13): error C2244: 'Job::create': unable to match function definition
to an existing declaration
(13): note: see declaration of 'Job::create'
(13): note:
On Thu, 11 Jan 2024 at 16:12, Patrick Palka wrote:
>
> On Thu, 11 Jan 2024, Jonathan Wakely wrote:
>
> > On Wed, 10 Jan 2024 at 21:40, Patrick Palka wrote:
> > >
> > > Tested on x86_64-pc-linux-gnu, does this look OK for trunk?
> > >
> > > -- >8 --
> > >
> > > This avoids redundant moves when
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113342
Bug ID: 113342
Summary: Template parameter does not shadow member enum value.
Product: gcc
Version: 13.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105505
Jonathan Wakely changed:
What|Removed |Added
Target Milestone|--- |14.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113320
--- Comment #2 from Jonathan Wakely ---
Patch posted:
https://gcc.gnu.org/pipermail/gcc-patches/2024-January/642741.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110512
--- Comment #9 from Jonathan Wakely ---
Patch posted for review:
https://gcc.gnu.org/pipermail/gcc-patches/2024-January/642732.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113341
--- Comment #8 from Jessica Clarke ---
The clang/ subdirectory should be building itself with -fno-strict-aliasing on
GCC already
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113313
--- Comment #6 from john.harper at vuw dot ac.nz ---
I know nothing about either applying gfortran patches or MatterMost but
I'm willing to try.
On Thu, 11 Jan 2024, jvdelisle at gcc dot gnu.org wrote:
> Date: Thu, 11 Jan 2024 20:18:36 +
Snapshot gcc-11-20240111 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/11-20240111/
and on various mirrors, see https://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
On Thu, 2024-01-11 at 22:40 +0100, Guillaume Gomez wrote:
> Hi David,
>
> > The above looks correct, but the patch adds the entrypoint
> > descriptions
> > to topics/types.rst, which seems like the wrong place. The
> > function-
> > related ones should be in topics/functions.rst in the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113341
--- Comment #7 from Andrew Pinski ---
`-fno-lifetime-dse` is already used but I get the feeling there might be strict
aliasing issues in the code though. What happens if you add
-fno-strict-aliasing ?
This code gives me strict aliasing
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113341
--- Comment #6 from Andrew Pinski ---
The backtrace in the llvm bug report is not very useful either.
Maybe look into that first to see if it is obvious which function might be
compiling "incorrectly". Maybe there is a bug in the new clang
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113341
--- Comment #5 from Segher Boessenkool ---
(In reply to John Paul Adrian Glaubitz from comment #3)
> (In reply to Segher Boessenkool from comment #2)
> > We need a reduced testcase.
>
> Any suggestion on how to proceed here?
Nothing in
On Fri, 12 Jan 2024 at 00:16, Jonathan Wakely wrote:
>
> I'd like to commit this to trunk for GCC 14. Please take a look.
Without looking at it in excruciating detail, it's pretty much along
the lines of what I have always envisioned
to be a powerful combination of concepts and if-constexpr. My
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113124
Jason Merrill changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113341
--- Comment #4 from Andrew Pinski ---
I should mention that LLVM has/had known issues with -flifetime-dse so it might
be useful also to show how stage1 of LLVM/clang was being built.
1 - 100 of 372 matches
Mail list logo
