Hello Kewen:
On 12/12/23 11:58 am, Kewen.Lin wrote:
> Hi Ajit,
>
> on 2023/12/8 16:01, Ajit Agarwal wrote:
>> Hello Kewen:
>>
>
> [snip...]
>
>> With UNSPEC_MMA_EXTRACT I could generate the register pair but functionally
>> here is the
>> below code which is incorrect.
>>
>> l lxvp
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112962
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |14.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112961
Richard Biener changed:
What|Removed |Added
Status|NEW |ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96340
--- Comment #1 from Andrew Pinski ---
was this also fixed by r14-6416-gf5fc001a84a7db ?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112939
Richard Biener changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112444
Bug 112444 depends on bug 112939, which changed state.
Bug 112939 Summary: [14 Regression] ICE: verify_ssa failed with -O
-ftrivial-auto-var-init=zero
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112939
What|Removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112939
--- Comment #3 from GCC Commits ---
The master branch has been updated by Richard Biener :
https://gcc.gnu.org/g:f5f33b44b5dd4c41ae335445ae3f06b1ca3cfbcb
commit r14-6448-gf5f33b44b5dd4c41ae335445ae3f06b1ca3cfbcb
Author: Richard Biener
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96341
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |14.0
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112693
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |14.0
Status|UNCONFIRMED
The following builds upon the last fix, making sure we only value-number
to visited (un-)defs, otherwise prefer .VN_TOP.
Bootstrapped and tested on x86_64-unknown-linux-gnu, pushed.
PR tree-optimization/112939
* tree-ssa-sccvn.cc (visit_phi): When all args are undefined
On Mon, Dec 11, 2023 at 11:46 AM Richard Sandiford
wrote:
>
> Jeff Law writes:
> > On 11/27/23 05:12, Richard Sandiford wrote:
> >> check_asm_operands was inconsistent about how it handled "p" after
> >> RA compared to before RA. Before RA it tested the address with a
> >> void (unknown) memory
Hi,
on 2023/11/22 17:30, Kewen.Lin wrote:
> on 2023/11/17 20:55, Alexander Monakov wrote:
>>
>> On Fri, 17 Nov 2023, Kewen.Lin wrote:
I don't think you can run cleanup_cfg after sched_init. I would suggest
to put it early in schedule_insns.
>>>
>>> Thanks for the suggestion, I placed it
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112970
--- Comment #2 from Xi Ruoyao ---
(In reply to Xi Ruoyao from comment #1)
> With -mexplicit-relocs=auto the generated code is sub-optimal as well:
I mean "always", not "auto".
> pcalau12i $r12,%pc_hi20(.LANCHOR0)
> addi.d
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112970
--- Comment #1 from Xi Ruoyao ---
With -mexplicit-relocs=auto the generated code is sub-optimal as well:
pcalau12i $r12,%pc_hi20(.LANCHOR0)
addi.d $r12,$r12,%pc_lo12(.LANCHOR0)
ld.wu $r5,$r12,4
addi.d
The problem with peephole2 is it uses a naive sliding-window algorithm
and misses many cases. For example:
float a[1];
float t() { return a[0] + a[8000]; }
is compiled to:
la.local$r13,a
la.local$r12,a+32768
fld.s $f1,$r13,0
fld.s $f0,$r12,-768
Hi Ajit,
on 2023/12/8 16:01, Ajit Agarwal wrote:
> Hello Kewen:
>
[snip...]
> With UNSPEC_MMA_EXTRACT I could generate the register pair but functionally
> here is the
> below code which is incorrect.
>
> llxvp %vs0,0(%r4)
> xxlor %vs32,%vs0,%vs0
> xvf32ger 0,%vs34,%vs32
Hi,
Gentle ping this:
https://gcc.gnu.org/pipermail/gcc-patches/2023-November/636597.html
BR,
Kewen
on 2023/11/15 17:01, Kewen.Lin wrote:
> Hi,
>
> on 2023/11/10 01:40, Alexander Monakov wrote:
>
>> I agree with the concern. I hoped that solving the problem by skipping the BB
>> like the
Hi,
Gentle ping:
https://gcc.gnu.org/pipermail/gcc-patches/2023-November/636599.html
BR,
Kewen
on 2023/11/15 17:16, Kewen.Lin wrote:
> Hi,
>
> As Power ISA defines, when loading a scalar single precision (SP)
> floating point from memory, we have the double precision (DP) format
> in target
x86 doesn't support horizontal reduction instructions, reduc_op_scal_m
is emulated with vec_extract_half + op(half vector length)
Take that into account when calculating cost for vectorization.
Bootstrapped and regtested on x86_64-pc-linux-gnu{-m32,}.
No big performance impact on SPEC2017 as
Hi,
Gentle ping this:
https://gcc.gnu.org/pipermail/gcc-patches/2023-January/609993.html
BR,
Kewen
> on 2023/1/16 17:08, Kewen.Lin via Gcc-patches wrote:
>> Hi,
>>
>> As Honza pointed out in [1], the current uses of function
>> optimize_function_for_speed_p in
Hi,
Gentle ping this series:
https://gcc.gnu.org/pipermail/gcc-patches/2022-November/607146.html
BR,
Kewen
>>> on 2022/11/24 17:15, Kewen Lin wrote:
Hi,
Following Segher's suggestion, this patch series is to rework
function rs6000_emit_vector_compare for
Hi,
Gentle ping this:
https://gcc.gnu.org/pipermail/gcc-patches/2023-December/639140.html
BR,
Kewen
on 2023/12/4 17:49, Kewen.Lin wrote:
> Hi,
>
> As PR112788 shows, on rs6000 with -mabi=ieeelongdouble type _Float128
> has the different type precision (128) from that (127) of type long
>
On Tue, Dec 12, 2023 at 1:47 PM Jiang, Haochen via Gcc-regression
wrote:
>
> > -Original Message-
> > From: Jiang, Haochen
> > Sent: Tuesday, December 12, 2023 9:11 AM
> > To: Andrew Pinski (QUIC) ; haochen.jiang
> > ; gcc-regress...@gcc.gnu.org; gcc-
> > patc...@gcc.gnu.org
> > Subject:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112929
--- Comment #18 from Li Pan ---
I see, thanks all, will have a try with variadic function call.
Hi,
on 2023/12/11 10:54, HAO CHEN GUI wrote:
> Hi,
> This patch cleans up pre-checking of expand_block_compare. It does
> 1. Assert only P7 above can enter this function as it's already guard
> by the expand.
> 2. Return false when optimizing for size.
> 3. Remove P7 CPU test as only P7 above
On Mon, Dec 11, 2023, 21:48 Jiang, Haochen wrote:
> > -Original Message-
> > From: Jiang, Haochen
> > Sent: Tuesday, December 12, 2023 9:11 AM
> > To: Andrew Pinski (QUIC) ; haochen.jiang
> > ; gcc-regress...@gcc.gnu.org; gcc-
> > patc...@gcc.gnu.org
> > Subject: RE: [r14-6420
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112978
--- Comment #2 from Raymond Chang ---
(In reply to Andrew Pinski from comment #1)
> I doubt this is fixable really because the number of expansions is huge.
Thanks, I think this is a pretty uncommon situtation anyways. I figured I'd
report it
> -Original Message-
> From: Jiang, Haochen
> Sent: Tuesday, December 12, 2023 9:11 AM
> To: Andrew Pinski (QUIC) ; haochen.jiang
> ; gcc-regress...@gcc.gnu.org; gcc-
> patc...@gcc.gnu.org
> Subject: RE: [r14-6420 Regression] FAIL: gcc.target/i386/pr110790-2.c scan-
> assembler-times shrq
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112978
Andrew Pinski changed:
What|Removed |Added
Keywords||compile-time-hog
--- Comment #1 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112978
Bug ID: 112978
Summary: Five minute long error message when OpenMP pragma is
erroneously placed in macro
Product: gcc
Version: 14.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112891
--- Comment #5 from GCC Commits ---
The master branch has been updated by hongtao Liu :
https://gcc.gnu.org/g:fc62716fe8d1d60a9f1c6906e5a4845b3331b828
commit r14-6447-gfc62716fe8d1d60a9f1c6906e5a4845b3331b828
Author: liuhongt
Date: Thu Dec
On Fri, Dec 8, 2023 at 10:17 AM liuhongt wrote:
>
> If the function desn't clobber any sse registers or only clobber
> 128-bit part, then vzeroupper isn't issued before the function exit.
> the status not CLEAN but ANY after the function.
>
> Also for sibling_call, it's safe to issue an
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112334
Alexandre Oliva changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
On Dec 11, 2023, Jeff Law wrote:
>>
>> for gcc/ChangeLog
>> PR target/112334
>> * builtins.h (target_builtins): Add fields for apply_args_size
>> and apply_result_size.
>> * builtins.cc (apply_args_size, apply_result_size): Cache
>> results in fields rather than in static variables.
>>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112334
--- Comment #4 from GCC Commits ---
The master branch has been updated by Alexandre Oliva :
https://gcc.gnu.org/g:d96533559e26dd0c86f0708fa46eef65c35f7b90
commit r14-6446-gd96533559e26dd0c86f0708fa46eef65c35f7b90
Author: Alexandre Oliva
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112783
Andrew Pinski changed:
What|Removed |Added
Resolution|INVALID |MOVED
--- Comment #6 from Andrew
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112783
Andrew Pinski changed:
What|Removed |Added
Resolution|FIXED |INVALID
--- Comment #5 from Andrew
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112783
yancheng.li at foxmail dot com changed:
What|Removed |Added
Resolution|INVALID |FIXED
--- Comment #4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100942
--- Comment #2 from Andrew Pinski ---
Created attachment 56860
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56860=edit
Patch which I am testing
Patch which I am testing. Will be doing some benchmarking too.
在 2023/12/12 上午9:58, chenglulu 写道:
在 2023/12/10 上午12:38, Xi Ruoyao 写道:
We are excluding loongarch-opts.h from target libraries, but now struct
loongarch_target and gcc_options are not declared in the target
libraries, causing:
In file included from ../.././gcc/options.h:8,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112943
Hongyu Wang changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
Hi,
on 2023/12/11 09:49, HAO CHEN GUI wrote:
> Hi,
> The patch corrects the definition of
> TARGET_EFFICIENT_OVERLAPPING_UNALIGNED and change its name to a
> comprehensible name.
>
> Bootstrapped and tested on x86 and powerpc64-linux BE and LE with no
> regressions. Is this OK for trunk?
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112943
--- Comment #4 from GCC Commits ---
The master branch has been updated by Hongyu Wang :
https://gcc.gnu.org/g:07dcb39e08aa52f166e8d74420364757002ad756
commit r14-6445-g07dcb39e08aa52f166e8d74420364757002ad756
Author: Hongyu Wang
Date: Mon
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99407
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |13.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107247
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |13.0
OK for trunk?
-- 8< --
I thought it could be easier to use check_GNU_style.py. With this alias,
'git gcc-style' will take a git revision as argument instead of a file, or
check HEAD if no argument is given.
contrib/ChangeLog:
* gcc-git-customization.sh: Add git gcc-style alias.
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111972
--- Comment #20 from Hongtao Liu ---
(In reply to Andrew Pinski from comment #19)
> Fixed.
Thanks.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112943
Hongtao Liu changed:
What|Removed |Added
CC||liuhongt at gcc dot gnu.org
--- Comment
On Mon, Dec 11, 2023 at 8:39 PM Hongyu Wang wrote:
>
> > > +__int128 u128_2 = (9223372036854775808 << 4) * foo0_u8_0; /* {
> > > dg-warning "integer constant is so large that it is unsigned" "so large"
> > > } */
> >
> > Just you can use (9223372036854775807LL + (__int128) 1) instead of
>
On Dec 11, 2023, Alexandre Oliva wrote:
> (there's a #2/2 followup coming up that addresses the ??? comment added
> herein)
Here it is. Also regstrapped on x86_64-linux-gnu, along with the
previous patch (that had also been regstrapped by itself). I think this
would be a desirable thing to do
Hi,
on 2023/12/11 11:26, Jiufu Guo wrote:
> Hi,
>
> For constant building e.g. r120=0x, which does not fit 'li or lis',
> 'pli' is used to build this constant via 'emit_move_insn'.
>
> While for a complicated constant, e.g. 0xULL, when using
>
Add more test coverage for r14-6349-g0bef72539e585d.
Pushed to trunk as r14-6444-g2900a77fe4e7d2.
gcc/testsuite/ChangeLog:
* gcc.dg/plugin/plugin.exp: Add taint-modulus.c to
analyzer_kernel_plugin.c tests.
* gcc.dg/plugin/taint-modulus.c: New test.
---
Hi Jeff,
on 2023/12/11 11:26, Jiufu Guo wrote:
> Hi,
>
> Trunk gcc supports more constants to be built via two instructions:
> e.g. "li/lis; xori/xoris/rldicl/rldicr/rldic".
> And then num_insns_constant should also be updated.
>
> Function "rs6000_emit_set_long_const" is used to build
ChangeLog:
* MAINTAINERS: Update my email address
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index f3683ff03ec..bc47e30325b 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -705,7 +705,7 @@ Marcel Vollweiler
Patch v3: Fix typo and remove the modification of rvv.exp.
Patch v2: Using variadic macro and add the dependency into t-riscv.
In order to add other extension about vector,this patch add
unsigned int (*avail) (void) into function_group_info to determine
whether to register the intrinsic based on
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112938
--- Comment #4 from Alexandre Oliva ---
Patch at https://gcc.gnu.org/pipermail/gcc-patches/2023-December/640252.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112977
--- Comment #1 from David Malcolm ---
Created attachment 56859
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56859=edit
Reduced reproducer (needs adding to plugin.exp)
This patch moves RVV POLY VALUE estimation from riscv.cc to riscv-v.cc for
future better maintain like other target hook implementation.
Committed as it is obviously a code refinement.
gcc/ChangeLog:
* config/riscv/riscv-protos.h (estimated_poly_value): New function.
*
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112977
Bug ID: 112977
Summary: -Wanalyzer-tainted-offset false positive seen on Linux
kernel's drivers/scsi/aacraid/aachba.c
Product: gcc
Version: unknown
Status: UNCONFIRMED
On 2023/12/12 1:45, H.J. Lu wrote:
> On Sat, Dec 9, 2023 at 7:25 PM Zhu, Lipeng wrote:
> >
> > On 2023/12/9 23:23, Jakub Jelinek wrote:
> > > On Sat, Dec 09, 2023 at 10:39:45AM -0500, Lipeng Zhu wrote:
> > > > This patch try to introduce the rwlock and split the read/write to
> > > > unit_root
ChangeLog:
* MAINTAINERS: Add myself to write after approval
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 0dbcbadcfd7..f3683ff03ec 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -705,6 +705,7 @@ Marcel Vollweiler
Pushed to r14-6440.
在 2023/12/8 下午6:01, Yang Yujie 写道:
On LoongArch, the regitsters $r4 - $r7 (EH_RETURN_DATA_REGNO) will be saved
and restored in the function prologue and epilogue if the given function calls
__builtin_eh_return. This causes the return value to be overwritten on normal
return
When generating code for an internal strub wrapper, don't clear the
DECL_NOT_GIMPLE_REG_P flag of volatile args, and gimplify them both
before and after any conversion.
While at that, move variable TMP into narrower scopes so that it's
more trivial to track where ARG lives.
Regstrapped on
在 2023/12/10 上午12:38, Xi Ruoyao 写道:
We are excluding loongarch-opts.h from target libraries, but now struct
loongarch_target and gcc_options are not declared in the target
libraries, causing:
In file included from ../.././gcc/options.h:8,
from ../.././gcc/tm.h:49,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112919
--- Comment #5 from chenglulu ---
(In reply to Xi Ruoyao from comment #4)
> Lulu: can you help to run some other benchmarks like SPEC (I don't have an
> access to it) and update these values for LA464 and LA664?
No problem, this is what I
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112737
--- Comment #3 from Patrick Palka ---
Created attachment 56858
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56858=edit
untested fix
Changing CLASS_PLACEHOLDER_TEMPLATE of a CTAD placeholder that names a ttp to
point to the ttp's
On Dec 11, 2023, Sam James wrote:
> Alexandre Oliva via Gcc-patches writes:
>> On Jun 2, 2023, Alexandre Oliva wrote:
>>
>>> Introduce -finline-stringops
>>
>> Ping? https://gcc.gnu.org/pipermail/gcc-patches/2023-June/620472.html
> Should the docs for the x86-specific
On Dec 11, 2023, Joseph Myers wrote:
> On Fri, 8 Dec 2023, Alexandre Oliva wrote:
>> @@ -20589,7 +20589,7 @@ allocation before or after interprocedural
>> optimization.
>> This option enables multilib-aware @code{TFLAGS} to be used to build
>> target libraries with options different from those
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100942
Andrew Pinski changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |pinskia at gcc dot
gnu.org
> -Original Message-
> From: Andrew Pinski (QUIC)
> Sent: Tuesday, December 12, 2023 9:01 AM
> To: haochen.jiang ; Andrew Pinski (QUIC)
> ; gcc-regress...@gcc.gnu.org; gcc-
> patc...@gcc.gnu.org; Jiang, Haochen
> Subject: RE: [r14-6420 Regression] FAIL: gcc.target/i386/pr110790-2.c scan-
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112976
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=112976
Bug ID: 112976
Summary: expand_gimple_stmt_1 vs
gimple_assign_nontemporal_move_p vs SSA_NAME on lhs
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Keywords:
> -Original Message-
> From: haochen.jiang
> Sent: Monday, December 11, 2023 4:54 PM
> To: Andrew Pinski (QUIC) ; gcc-
> regress...@gcc.gnu.org; gcc-patches@gcc.gnu.org; haochen.ji...@intel.com
> Subject: [r14-6420 Regression] FAIL: gcc.target/i386/pr110790-2.c scan-
> assembler-times
On Linux/x86_64,
85c5efcffed19ca6160eeecc2d4faebd9fee63aa is the first bad commit
commit 85c5efcffed19ca6160eeecc2d4faebd9fee63aa
Author: Andrew Pinski
Date: Sat Nov 11 15:54:10 2023 -0800
MATCH: (convert)(zero_one !=/== 0/1) for outer type and zero_one type are
the same
caused
FAIL:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109876
Marek Polacek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110106
Marek Polacek changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112410
Marek Polacek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112410
--- Comment #6 from GCC Commits ---
The releases/gcc-13 branch has been updated by Marek Polacek
:
https://gcc.gnu.org/g:60979215517629400902938b1c5666f97d0653cf
commit r13-8147-g60979215517629400902938b1c5666f97d0653cf
Author: Marek Polacek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110106
--- Comment #6 from GCC Commits ---
The releases/gcc-13 branch has been updated by Marek Polacek
:
https://gcc.gnu.org/g:d44830a1364cf8cb726d59e91298a5b3077a86d9
commit r13-8148-gd44830a1364cf8cb726d59e91298a5b3077a86d9
Author: Marek Polacek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109876
--- Comment #16 from GCC Commits ---
The releases/gcc-13 branch has been updated by Marek Polacek
:
https://gcc.gnu.org/g:08f4496aa619f9b0e8dbb459452dd96edb870236
commit r13-8146-g08f4496aa619f9b0e8dbb459452dd96edb870236
Author: Marek Polacek
I'm not sure how to do this. I tried the following commands, but this
fails even on master:
../../gcc/configure --enable-host-shared --enable-
languages=c,jit,c++,fortran,objc,lto --enable-checking=release --
disable-werror --prefix=/opt/gcc
make bootstrap -j24
make -k check -j24
>From what I
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112975
--- Comment #1 from David Malcolm ---
Created attachment 56857
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56857=edit
Reduced reproducer (needs adding to plugin.exp)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112975
Bug ID: 112975
Summary: -Wanalyzer-tainted-allocation-size false positive seen
in Linux kernel's drivers/xen/privcmd.c
Product: gcc
Version: unknown
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112599
Patrick O'Neill changed:
What|Removed |Added
Attachment #56795|0 |1
is obsolete|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112598
Patrick O'Neill changed:
What|Removed |Added
Attachment #56794|0 |1
is obsolete|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112974
--- Comment #1 from David Malcolm ---
Created attachment 56854
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56854=edit
Patch adding reduced reproducer
On 12/11/23 17:12, Thomas Schwinge wrote:
Hi!
This issue would've been prevented if we'd actually use a distinct C++
data type for GCC types, checkable at compile time -- I'm thus CCing
Andrew MacLeod for amusement or crying, "one more for the list!". ;-\
Perhaps the time has come It
On 12/11/23 16:19, Andrew Pinski via Gcc wrote:
nds32 support in Linux was removed last year:
https://www.phoronix.com/news/Andes-Tech-NDS32-Removal
The support for glibc never made it upstream as far as I can tell either.
What are others thoughts on this?
I believe the architecture is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112974
Bug ID: 112974
Summary: -Wanalyzer-tainted-array-index false positive seen on
Linux kernel
drivers/platform/x86/intel/speed_select_if/isst_tpmi_c
ore.c
On Mon, Dec 11, 2023 at 5:20 PM Andrew Pinski via Gcc
wrote:
> nds32 support in Linux was removed last year:
> https://www.phoronix.com/news/Andes-Tech-NDS32-Removal
>
> The support for glibc never made it upstream as far as I can tell either.
>
> What are others thoughts on this?
>
Looks like
nds32 support in Linux was removed last year:
https://www.phoronix.com/news/Andes-Tech-NDS32-Removal
The support for glibc never made it upstream as far as I can tell either.
What are others thoughts on this?
Thanks,
Andrew Pinski
> > + vectype = truth_type_for (comp_type);
>
> so this leaves the producer of the mask in the GIMPLE_COND and we
> vectorize the GIMPLE_COND as
>
> mask_1 = ...;
> if (mask_1 != {-1,-1...})
> ..
>
> ? In principle only the mask producer needs a vector type and that
> adjusted by
On Mon, Dec 11, 2023 at 05:00:50PM -0500, Jason Merrill wrote:
> In discussion of PR71093 it came up that more clobber_kind options would be
> useful within the C++ front-end.
>
> gcc/ChangeLog:
>
> * tree-core.h (enum clobber_kind): Rename CLOBBER_EOL to
> CLOBBER_STORAGE_END. Add
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78352
--- Comment #22 from Andrew Pinski ---
(In reply to Sergey Fedorov from comment #21)
> Any chance of having it fixed in gcc14?
It is too late to be included in GCC 14, GCC is in stage 3 already, that is no
new features can be included that was
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78352
--- Comment #21 from Sergey Fedorov ---
(In reply to Iain Sandoe from comment #20)
>
> I recently brought my patches forward from GCC-5 => GCC-10 (easier to avoid
> the .c => .cc file renaming). Since we now face some problems with
> sanitiser
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112963
--- Comment #13 from Jakub Jelinek ---
I've already started testing the:
2023-12-11 Jakub Jelinek
PR libquadmath/112963
* configure.ac (LIBM): Readd AC_CHECK_LIBM-like check without doing
AC_CHECK_LIB in it.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112963
--- Comment #12 from Iain Sandoe ---
(In reply to Jakub Jelinek from comment #10)
> BTW, yet another option would be to just
> LIBM=
> case $host in
> *-*-beos* | *-*-cegcc* | *-*-cygwin* | *-*-haiku* | *-*-pw32* | *-*-darwin*)
> # These
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112972
Stephan Stiller changed:
What|Removed |Added
Status|RESOLVED|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112972
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |INVALID
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112973
Bug ID: 112973
Summary: Documentation for __builtin_preserve_access_index is
not wrapped in extend.texi
Product: gcc
Version: 14.0
Status: UNCONFIRMED
1 - 100 of 366 matches
Mail list logo
