https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113962
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113962
Bug ID: 113962
Summary: [14 Regression] ICE: in exact_div, at poly-int.h:2156
with -O -mavx512f
Product: gcc
Version: 14.0
Status: WAITING
Keywords: ice-on-val
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113960
Richard Biener changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113959
Richard Biener changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113987
Jakub Jelinek changed:
What|Removed |Added
Priority|P3 |P2
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113987
--- Comment #4 from Andrew Pinski ---
(In reply to Fangrui Song from comment #1)
> BTW,
> https://github.com/llvm/llvm-project/blob/main/clang/test/SemaCXX/
> uninitialized.cpp has many member initializer list examples
And r12-5391-g0790c8aacdf
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113987
--- Comment #3 from Andrew Pinski ---
Most likely started with r12-5391-g0790c8aacdfb4f .
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113987
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |12.4
Known to fail|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113986
Andrew Pinski changed:
What|Removed |Added
CC||wilco at gcc dot gnu.org
St
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113987
--- Comment #1 from Fangrui Song ---
BTW,
https://github.com/llvm/llvm-project/blob/main/clang/test/SemaCXX/uninitialized.cpp
has many member initializer list examples
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113987
Bug ID: 113987
Summary: Binding a reference to an uninitialized data member
should not cause -Wuninitialized
Product: gcc
Version: unknown
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113986
Andrew Pinski changed:
What|Removed |Added
Keywords||build
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113986
Bug ID: 113986
Summary: [14 regression] Build failure on aarch64-linux-musl
(error: 'export_load_16' aliased to undefined symbol
'libat_load_16')
Product: gcc
Ve
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113985
Andrew Pinski changed:
What|Removed |Added
Status|RESOLVED|NEW
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113985
Xi Ruoyao changed:
What|Removed |Added
Resolution|--- |INVALID
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113985
Bug ID: 113985
Summary: redundant copy of return values at O0
Product: gcc
Version: 13.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: rtl-opti
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109358
--- Comment #16 from Jerry DeLisle ---
I think I was not being very clear when I opened pr113897. nX descriptors are
very similar to TR code and I meeantt to take care of those in the 113897. The
reason for the separate PR is that the problem i
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113984
Andrew Pinski changed:
What|Removed |Added
Summary|-Wfree-nonheap-object false |-Wfree-nonheap-object false
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113984
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113984
--- Comment #1 from Alejandro Colomar ---
With -O3, the warning also vanishes, as the function is probably inlined, and
there's no VLA parameter any more.
alx@debian:~/tmp$ gcc-14 -Wall -O3 nonheap.c
alx@debian:~/tmp$ gcc-13 -Wall -O3 nonheap.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113984
Bug ID: 113984
Summary: -Wfree-nonheap-object false positive with VLA
parameter
Product: gcc
Version: 13.2.0
Status: UNCONFIRMED
Severity: normal
Pri
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113983
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2024-02-18
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113982
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113983
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |14.0
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113983
Bug ID: 113983
Summary: [14 Regression] ICE: tree check: expected integer_cst,
have vector_cst in
maybe_undo_optimize_bit_field_compare, at
analyzer/region-model-m
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113982
--- Comment #2 from Andrew Pinski ---
Note some of this is due to return register issues.
If we instead do stores:
```
add_wide_1(unsigned long long, unsigned long long, add_result*):
mov rax, rdi
lea rcx, [rdi+rsi]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113982
Andrew Pinski changed:
What|Removed |Added
Component|target |middle-end
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113982
Bug ID: 113982
Summary: Poor codegen for 64-bit add with carry widening
functions
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Pri
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113976
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86761
Andrew Pinski changed:
What|Removed |Added
CC||Simon.Richter at hogyros dot de
--- Comm
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113981
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113980
--- Comment #1 from Andrew Pinski ---
Basically GCC does not optimize around a volatile memory load/stores which
causes artifacts like this.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113981
Bug ID: 113981
Summary: risc-v: non-void C++ function with no return statement
has no ret
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113980
Bug ID: 113980
Summary: risc-v: unnecessary sign-extend after lw, and more
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Componen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113976
--- Comment #4 from Andrew Pinski ---
(In reply to Jeffrey A. Law from comment #3)
> What does the standard say about changing const objects?
It says it is undefined. Note there is no changing const object in this code;
just the const variable
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113976
--- Comment #3 from Jeffrey A. Law ---
What does the standard say about changing const objects?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113971
Iain Sandoe changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |iains at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113912
H.J. Lu changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113912
--- Comment #2 from GCC Commits ---
The master branch has been updated by H.J. Lu :
https://gcc.gnu.org/g:853eb57759967335a7ea872e6a0721034db6fabd
commit r14-9058-g853eb57759967335a7ea872e6a0721034db6fabd
Author: H.J. Lu
Date: Tue Feb 13 13
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113979
Bug ID: 113979
Summary: Allocation of 2D array fails when Dynamic Predicate
applied to type
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113974
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113974
--- Comment #3 from Georg-Johann Lay ---
Then the documentation should make that clear that with -fno-data-sections the
object goes in COMM, but with -fdata-sections it does not and the attribute
"common" is ignored.
Better still, the compiler
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44854
peter0x44 at disroot dot org changed:
What|Removed |Added
CC||peter0x44 at disroot dot or
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113978
--- Comment #8 from Jakub Jelinek ---
(In reply to Jakub Jelinek from comment #7)
> The psABI doesn't cover that. It only talks about __m128, __m256 and __m512
> types, and
> as both compilers use the GNU vector_size attribute extension under t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112344
--- Comment #13 from GCC Commits ---
The master branch has been updated by Dimitar Dimitrov :
https://gcc.gnu.org/g:3796216bfa49b5ca288afe0760931a4c5b8ea346
commit r14-9055-g3796216bfa49b5ca288afe0760931a4c5b8ea346
Author: Dimitar Dimitrov
Da
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108640
--- Comment #10 from Anton Arnold ---
I applied the patch to a gcc 13.2 buildroot toolchain for a coldfire cpu with
ISA-A+ instruction set. Everything compiled fine and a linux 4.19 uclinux nommu
build with buildroot and several custom packages
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113915
--- Comment #12 from Sam James ---
(In reply to Andrew Pinski from comment #9)
> This should work, I think:
> [...]
I'm going to apply this tonight for our arm builds downstream as we can't do
any testing right now and there's a lot of bugs I'm
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51084
Paul Eggert changed:
What|Removed |Added
CC||eggert at cs dot ucla.edu
--- Comment #4 f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113976
--- Comment #2 from Matthias Maier ---
I have bisected the issue to:
commit 2ec399d8a6c9c26d69b73faf77c694fa3915dcec (HEAD, refs/bisect/bad)
Author: Joerg Sonnenberger
Date: Fri Sep 1 10:26:00 2017 -0600
varasm.c (bss_initializer_p): Do
49 matches
Mail list logo
