https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110341
--- Comment #4 from CVS Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:194825f20619a1c4b51eaea84f20432fefc0db03
commit r14-5454-g194825f20619a1c4b51eaea84f20432fefc0db03
Author: Jakub Jelinek
Date: T
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110338
Bug 110338 depends on bug 110341, which changed state.
Bug 110341 Summary: [C++26] P1854R4 - Making non-encodable string literals
ill-formed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110341
What|Removed |Ad
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110341
Jakub Jelinek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78904
--- Comment #19 from CVS Commits ---
The master branch has been updated by Uros Bizjak :
https://gcc.gnu.org/g:b42a09b258c3ed8d1368e0ef0948034dcf0f8ac9
commit r14-5456-gb42a09b258c3ed8d1368e0ef0948034dcf0f8ac9
Author: Uros Bizjak
Date: Tue N
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112524
Eric Botcazou changed:
What|Removed |Added
Ever confirmed|0 |1
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112529
Eric Botcazou changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112524
--- Comment #2 from Jack Perry ---
Either way, the correct behavior would be to report an error, right? the `for`
expression should be surrounded by parentheses, at least when Ada 2022 is
selected. But it seems instead to call that an error even
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112524
--- Comment #3 from Eric Botcazou ---
Yes, this looks like illegal indeed.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112530
Bug ID: 112530
Summary: [14 Regression] New ICE in gimple->rtl expansion after
recent change
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112530
--- Comment #1 from Andrew Pinski ---
Does r14-5453-g948b8b6e0e50958ecf56d4d9fb7ac16f245d9cc3 fix this too?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112530
--- Comment #2 from Andrew Pinski ---
(In reply to Andrew Pinski from comment #1)
> Does r14-5453-g948b8b6e0e50958ecf56d4d9fb7ac16f245d9cc3 fix this too?
The RISCV backtrace and the alpha backtrace is the same for the same testcase
too which is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112530
Jeffrey A. Law changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112481
--- Comment #14 from Jeffrey A. Law ---
*** Bug 112530 has been marked as a duplicate of this bug. ***
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112531
Bug ID: 112531
Summary: [14] RISC-V: gcc.dg/unroll-8.c rtl-dump scan errors
with --param=riscv-autovec-preference=scalable
Product: gcc
Version: 14.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106849
--- Comment #4 from CVS Commits ---
The master branch has been updated by Nathan Sidwell :
https://gcc.gnu.org/g:5b9ecce87e8f315e2681743d75401991cdfefa71
commit r14-5460-g5b9ecce87e8f315e2681743d75401991cdfefa71
Author: Nathaniel Shead
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103499
--- Comment #7 from CVS Commits ---
The master branch has been updated by Nathan Sidwell :
https://gcc.gnu.org/g:14979dd31c887ba5ba573f2cdb0647b37e09641a
commit r14-5461-g14979dd31c887ba5ba573f2cdb0647b37e09641a
Author: Nathaniel Shead
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112447
--- Comment #11 from Vineet Gupta ---
As a hack I commented out set_delete() to see what the extraneous vsetvli
would have been.
```
.L36:
# bb 3: start of outer loop: off 0
vsetvli zero,zero,e8,mf2,ta,ma # insn 2915
-gnu --with-ld=/usr/bin/x86_64-pc-linux-gnu-ld
--with-as=/usr/bin/x86_64-pc-linux-gnu-as --disable-libstdcxx-pch
--prefix=/repo/gcc-trunk//binary-trunk-r14-5443-20231114122339-gb9fd8399ec0-checking-yes-rtl-df-extra-nobootstrap-amd64
Thread model: posix
Supported LTO compression algorithms: zlib
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112533
Bug ID: 112533
Summary: missed optimization (~A & C) == (~B & C) => (A & C) ==
(B & C)
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112533
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103533
--- Comment #8 from CVS Commits ---
The master branch has been updated by David Malcolm :
https://gcc.gnu.org/g:cfaaa8b11b8429eed5ec44426fc6a20ad5d53d30
commit r14-5464-gcfaaa8b11b8429eed5ec44426fc6a20ad5d53d30
Author: David Malcolm
Date: T
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111311
Edwin Lu changed:
What|Removed |Added
CC||ewlu at rivosinc dot com
--- Comment #17 fro
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103533
David Malcolm changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104819
--- Comment #6 from anlauf at gcc dot gnu.org ---
(In reply to anlauf from comment #5)
> We need to detect and diagnose violations of the above.
Example:
program main
implicit none
type t
integer :: i
end type t
type(t), allocatab
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111627
Gaius Mulley changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111871
Gaius Mulley changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112348
Jonathan Wakely changed:
What|Removed |Added
Target Milestone|--- |12.4
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112531
JuzheZhong changed:
What|Removed |Added
CC||juzhe.zhong at rivai dot ai
--- Comment #1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112447
--- Comment #12 from JuzheZhong ---
The merge is correct here.
vmv.x.s demand SEW = 32 wheras vle/vse demand RATIO = 16 (e8mf2)
So, to make vsetvl valid for both of them, the vtype should be sew = 32 and
lmul = M2 (32 / 16 = 2).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112348
--- Comment #3 from CVS Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:6f2fc42d9e52e8322e718e0154cd235d00906f99
commit r14-5465-g6f2fc42d9e52e8322e718e0154cd235d00906f99
Author: Jonathan Wakely
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112491
--- Comment #3 from CVS Commits ---
The releases/gcc-13 branch has been updated by Jonathan Wakely
:
https://gcc.gnu.org/g:5cb055e99d2026c734602ffdc28cb8b357a7b28e
commit r13-8066-g5cb055e99d2026c734602ffdc28cb8b357a7b28e
Author: Jonathan Wake
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112348
--- Comment #4 from CVS Commits ---
The releases/gcc-13 branch has been updated by Jonathan Wakely
:
https://gcc.gnu.org/g:16635b89f36c07b9e06c48a93d1bfafa93178328
commit r13-8067-g16635b89f36c07b9e06c48a93d1bfafa93178328
Author: Jonathan Wake
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112491
--- Comment #4 from CVS Commits ---
The releases/gcc-12 branch has been updated by Jonathan Wakely
:
https://gcc.gnu.org/g:99f992a275c30bc8db2e6352e98ab81c89b5b7ed
commit r12-9977-g99f992a275c30bc8db2e6352e98ab81c89b5b7ed
Author: Jonathan Wake
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112348
--- Comment #5 from CVS Commits ---
The releases/gcc-12 branch has been updated by Jonathan Wakely
:
https://gcc.gnu.org/g:a97c08ea530dadf366022b5c3e5aab21d34a61bd
commit r12-9978-ga97c08ea530dadf366022b5c3e5aab21d34a61bd
Author: Jonathan Wake
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112348
Jonathan Wakely changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47857
--- Comment #10 from CVS Commits ---
The master branch has been updated by Lewis Hyatt :
https://gcc.gnu.org/g:9938645fcf914ec2a3fa8137cf1456ad4af5f77c
commit r14-5471-g9938645fcf914ec2a3fa8137cf1456ad4af5f77c
Author: Lewis Hyatt
Date: Fri N
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=9471
--- Comment #5 from CVS Commits ---
The master branch has been updated by Lewis Hyatt :
https://gcc.gnu.org/g:9938645fcf914ec2a3fa8137cf1456ad4af5f77c
commit r14-5471-g9938645fcf914ec2a3fa8137cf1456ad4af5f77c
Author: Lewis Hyatt
Date: Fri Nov
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=9471
Lewis Hyatt changed:
What|Removed |Added
CC||lhyatt at gcc dot gnu.org
Resolutio
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47857
Lewis Hyatt changed:
What|Removed |Added
CC||lhyatt at gcc dot gnu.org
Resoluti
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112491
--- Comment #5 from CVS Commits ---
The releases/gcc-11 branch has been updated by Jonathan Wakely
:
https://gcc.gnu.org/g:57727d36e0a3d69dbd6b2221cde0624dbb9dfc95
commit r11-11098-g57727d36e0a3d69dbd6b2221cde0624dbb9dfc95
Author: Jonathan Wak
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112491
Jonathan Wakely changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112534
Bug ID: 112534
Summary: [14 regression] build failure after
r14-5424-gdb50aea6259545 using gcc 4.8.5
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: n
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112447
--- Comment #13 from Vineet Gupta ---
Then I don't know where the problem actually is ?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112534
--- Comment #1 from Andrew Pinski ---
Hmm. similar issue happen with gdb 5 years ago:
https://lists.gnu.org/archive/html/bug-gnulib/2018-08/msg00151.html
Looks like this is huge gnulib mess at that.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112447
--- Comment #14 from JuzheZhong ---
Let me give you some guide which helps you to dig into the problem.
First, reduce the case as follows:
#include
void abort (void);
void exit (int);
#ifndef MAX_OFFSET
#define MAX_OFFSET (sizeof (long long
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112447
--- Comment #15 from Vineet Gupta ---
(In reply to JuzheZhong from comment #14)
> Let me give you some guide which helps you to dig into the problem.
>
> First, reduce the case as follows:
Did your msg get truncated or pressed send too soon ?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112518
--- Comment #3 from Andrew Pinski ---
I cannot reproduce it with r14-5450-g4db820928065ec or r14-5427-gd22b87864e5d47
.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111439
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112496
--- Comment #5 from CVS Commits ---
The releases/gcc-13 branch has been updated by hongtao Liu
:
https://gcc.gnu.org/g:ed73ad337739a4244e8040d19b6e567c4101b58a
commit r13-8068-ged73ad337739a4244e8040d19b6e567c4101b58a
Author: liuhongt
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112104
--- Comment #5 from Hongtao.liu ---
(In reply to Andrew Pinski from comment #4)
> Fixed via r14-5428-gfd1596f9962569afff6c9298a7c79686c6950bef .
Note, my patch only handles constant tripcount for XOR, but not do the
transformation when tripcoun
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112104
Andrew Pinski changed:
What|Removed |Added
Status|RESOLVED|NEW
Resolution|FIXED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112104
Andrew Pinski changed:
What|Removed |Added
Target Milestone|14.0|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108865
peter0x44 at disroot dot org changed:
What|Removed |Added
CC||peter0x44 at disroot dot o
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108865
--- Comment #35 from Andrew Pinski ---
(In reply to peter0x44 from comment #34)
> Unfortunately, this option breaks GCC running under Windows XP.
XP has not been supported by mingw for a long time so I have no idea how you
have been building th
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108865
--- Comment #36 from Andrew Pinski ---
(In reply to Andrew Pinski from comment #35)
> (In reply to peter0x44 from comment #34)
> > Unfortunately, this option breaks GCC running under Windows XP.
>
> XP has not been supported by mingw for a long
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108865
--- Comment #37 from peter0x44 at disroot dot org ---
Sorry, comment got sent by accident, before I was done typing.
And you replied before I finished, too.
Thanks for pointing me in the correct direction.
===
IRRELEVANT
Executables with this
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112534
Bruno Haible changed:
What|Removed |Added
CC||bruno at clisp dot org
--- Comment #2 fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112534
--- Comment #3 from Bruno Haible ---
(In reply to Andrew Pinski from comment #1)
> Hmm. similar issue happen with gdb 5 years ago:
> https://lists.gnu.org/archive/html/bug-gnulib/2018-08/msg00151.html
Thanks; this is helpful. In this thread we
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112447
--- Comment #16 from JuzheZhong ---
The victim should be these 2 pieces of codes:
.L20:
lbu a1,0(a3)
li t1,97
bne a1,t1,.L21
lbu t1,1(a3)
bne t1,a1,.L21
lbu a1,2(a3)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112447
--- Comment #17 from JuzheZhong ---
The incorrect elimination happens on pre_global_vsetvl_info
You can try simple hack like this:
diff --git a/gcc/config/riscv/riscv-vsetvl.cc
b/gcc/config/riscv/riscv-vsetvl.cc
index 8466b5d019e..65dcf931808
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108865
--- Comment #38 from LIU Hao ---
(In reply to Andrew Pinski from comment #35)
> (In reply to peter0x44 from comment #34)
> > Unfortunately, this option breaks GCC running under Windows XP.
>
> XP has not been supported by mingw for a long time
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112525
--- Comment #6 from Jiu Fu Guo ---
(In reply to Jiu Fu Guo from comment #3)
> One possible method is fixing DSE to let is able to remove those 'store's.
> (but need to take care of the case that is using 'arg_pointer' to pass
> parameters.)
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112535
Bug ID: 112535
Summary: [14] RISC-V ICE: error: unable to find a register to
spill during RTL pass: reload
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Sever
algrind-annotations
--disable-vtable-verify --disable-libvtv --with-zstd --without-isl
--enable-default-pie --enable-host-pie --enable-host-bind-now
--enable-default-ssp --with-build-config='bootstrap-O3 bootstrap-lto'
Thread model: posix
Supported LTO compression algorithms: zlib
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112536
--- Comment #1 from Sam James ---
Created attachment 56588
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56588&action=edit
xf86Helper.c.i
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112536
--- Comment #2 from Sam James ---
I'm going to kick off cvise for this. I've also had probably a dupe with zstd
but I may reduce that too given both projects are C so it should be quick.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112447
--- Comment #18 from JuzheZhong ---
I know how to fix it.
Testing a candidate patch.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112536
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |14.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112447
--- Comment #19 from JuzheZhong ---
Created attachment 56589
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56589&action=edit
bug fix patch
Hi,Vineet.
The attachment is the bug fix patch.
I have tested on both RV32 and RV64 C/C++.
No reg
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112536
--- Comment #3 from Andrew Pinski ---
Worked at r14-5115-g6e9ee44d96e5bda8808dd9d8ccf58d2525383f6b .
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112447
--- Comment #20 from JuzheZhong ---
This is the reason of this patch:
The whole analysis is correct.But we made a mistake on inserting vsetvls.
This is the story.
We have 2 types of global vsetvls insertion.
One is earliest fusion of each end
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112537
Bug ID: 112537
Summary: Is there a way to disable cpymem pass for rvv
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112537
--- Comment #1 from Andrew Pinski ---
>since if vector load and store for smaller structure assign is costable and
>harmfull to cpu pipeline.
This depends on the Pipeline. Seems like there is a missing cost model for your
cpu somewhere.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112536
--- Comment #4 from Sam James ---
Reduced:
```
typedef struct {
int green, blue;
} rgb;
struct {
rgb offset;
} xf86SetWeight_scrp;
rgb xf86SetWeight_mask;
int ffs(int color);
void xf86SetWeight() {
xf86SetWeight_scrp.offset.green = ffs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112536
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2023-11-15
Status|UNCONFIRM
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112536
Andrew Pinski changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112518
--- Comment #4 from Zdenek Sojka ---
(In reply to Andrew Pinski from comment #3)
> I cannot reproduce it with r14-5450-g4db820928065ec or
> r14-5427-gd22b87864e5d47 .
Thank you for the investigation!
Either the flags have changed, or I did som
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112519
--- Comment #4 from Zdenek Sojka ---
I can no longer reproduce the failure on neither the original or reduced
testcase, on neither r14-5443 , r14-5456 nor r14-5476
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112536
--- Comment #7 from Sam James ---
Here's the zstd testcase with clz instead too:
```
unsigned a, b, minTableLog_srcSize;
unsigned FSE_minTableLog_srcSize(unsigned maxSymbolValue) {
minTableLog_srcSize = __builtin_clz(a);
b = -minTableLog_sr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112538
Bug ID: 112538
Summary: [RISC-V] Failed to disable V-ext autovectorization
using the '--param riscv-autovec-preference=none'
Product: gcc
Version: 14.0
Status: UNCONFIRM
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112537
--- Comment #2 from JuzheZhong ---
Currently, we don't have a compile option to disable cpymem by RVV.
I can tell how to disable it:
in riscv.md:
(define_expand "cpymem"
[(parallel [(set (match_operand:BLK 0 "general_operand")
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112537
--- Comment #3 from Huaqi ---
Hi Juzhe, thanks for the help, could it be controlled by
--param=riscv-autovec-preference= option, so if I want to enable cpymem
optimization, I can enable it by auto vectorzation.
Thanks
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112537
--- Comment #4 from JuzheZhong ---
You mean you want to disable it when disabling auto-vectorization ?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112537
--- Comment #5 from Huaqi ---
(In reply to JuzheZhong from comment #4)
> You mean you want to disable it when disabling auto-vectorization ?
Yes, I think this could be better, so we can control whether vector instruction
should be generated, an
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112537
--- Comment #6 from JuzheZhong ---
We can add
if (!flag_tree_vectorize)
return false;
in riscv_vector::expand_block_move
But I am not sure whether other RISC-V folks is happy with that.
CCing other folks to see whether they allow it.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54696
Sam James changed:
What|Removed |Added
CC||sjames at gcc dot gnu.org
--- Comment #4 fro
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112538
JuzheZhong changed:
What|Removed |Added
CC||juzhe.zhong at rivai dot ai
--- Comment #1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112538
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|UNCONFIRME
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112537
Andrew Pinski changed:
What|Removed |Added
CC||mumuxi_ll at outlook dot com
--- Commen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112374
Sam James changed:
What|Removed |Added
Summary|[14 Regression] |[14 Regression] Failed
|`
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110390
Sam James changed:
What|Removed |Added
Keywords||needs-reduction
Summary|ICE on v
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106849
Sam James changed:
What|Removed |Added
Keywords||ice-checking
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112496
Sam James changed:
What|Removed |Added
Resolution|--- |FIXED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112532
Sam James changed:
What|Removed |Added
CC||sjames at gcc dot gnu.org
--- Comment #1 fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112537
--- Comment #8 from Kito Cheng ---
That remind me we may need one option like something -mgeneral-regs-only in
aarch64 and also for target attribute.
BTW, clang has an generic option called -mno-implicit-float can did similar
thing
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112537
--- Comment #9 from JuzheZhong ---
I think we can use -fno-tree-vectorize or --param=riscv-autovec-preference=none
to
disable it.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70
--- Comment #3 from LIU Hao ---
Costas, would you like to provide a configure option to exclude that manifest?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112539
Bug ID: 112539
Summary: a struct with an array of unknown size at the end
allows writing past end of the struct
Product: gcc
Version: 11.4.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112539
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |INVALID
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112539
--- Comment #2 from Sam James ---
https://people.kernel.org/kees/bounded-flexible-arrays-in-c and
https://developers.redhat.com/articles/2022/09/29/benefits-limitations-flexible-array-members
are good reads too
101 - 200 of 208 matches
Mail list logo
