https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113340
--- Comment #4 from GCC Commits ---
The trunk branch has been updated by Marek Polacek :
https://gcc.gnu.org/g:ac219d524ace47eea5bf5404b267e22950f44030
commit r14-8165-gac219d524ace47eea5bf5404b267e22950f44030
Author: Marek Polacek
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113340
Marek Polacek changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53938
Andrew Pinski changed:
What|Removed |Added
CC||rsaxvc at gmail dot com
--- Comment #5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113432
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113431
--- Comment #3 from Patrick O'Neill ---
This has the same behavior with --param=vsetvl-strategy=simple so this is
probably not a vsetvl issue.
> /scratch/tc-testing/tc-jan-16-vsetvl-toggle/build-rv64gcv/bin/riscv64-unknown-linux-gnu-gcc
> -O3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113221
--- Comment #5 from Andrew Pinski ---
(In reply to Andrew Pinski from comment #4)
> Actually `(match_operand 0 "register_operand")` should be used instead of
> the current `(match_code "reg,subreg")`.
Except that does not work since
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113377
--- Comment #3 from anlauf at gcc dot gnu.org ---
Created attachment 57108
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57108=edit
Patch to play with
This is a first attempt to outline code for handling scalar dummies with the
VALUE
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113430
Bug ID: 113430
Summary: Trivial program segfaults intermittently with ASAN
since Linux 6.7
Product: gcc
Version: 13.2.1
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113432
Bug ID: 113432
Summary: missing optimization: GCC UXTB zero-extends result of
LDRB from volatile variables
Product: gcc
Version: 13.2.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113377
--- Comment #4 from anlauf at gcc dot gnu.org ---
(In reply to anlauf from comment #3)
> However,
>
> integer, allocatable,optional :: j
>
> still does not work: the code *in* the generated loop looks fine to me, but
> the scalarizer
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113429
--- Comment #4 from JuzheZhong ---
Thanks. Will take a look
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113221
--- Comment #4 from Andrew Pinski ---
Actually `(match_operand 0 "register_operand")` should be used instead of the
current `(match_code "reg,subreg")`.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113307
Jason Merrill changed:
What|Removed |Added
Target Milestone|--- |14.0
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113431
Bug ID: 113431
Summary: [14] RISC-V rv64gcv vector: Runtime mismatch at -O3
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113431
Patrick O'Neill changed:
What|Removed |Added
Keywords||wrong-code
Target|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113431
--- Comment #2 from JuzheZhong ---
Will take a look today.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113156
Andrew Pinski changed:
What|Removed |Added
Target Milestone|14.0|12.4
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113221
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=113429
--- Comment #3 from Vineet Gupta ---
The toggles used to build are
riscv64-unknown-linux-gnu-gfortran -c -o cam4red.o -I. -Iinclude
-Inetcdf/include -Ofast -fno-lto -static -march=rv64gcv_zba_zbb_zbs_zicond
-ftree-vectorize
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113307
--- Comment #2 from GCC Commits ---
The trunk branch has been updated by Jason Merrill :
https://gcc.gnu.org/g:6aae831a3fe6619794afa79410e6fc1b4817f0b1
commit r14-8163-g6aae831a3fe6619794afa79410e6fc1b4817f0b1
Author: waffl3x
Date: Fri Jan
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88935
--- Comment #11 from Jonathan Wakely ---
Yes, but in practice that's not the problem with mingw. The problem is the low
RAND_MAX. The distribution within the range of numbers produced is acceptable.
Good enough for std::random_shuffle anyway.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113292
--- Comment #1 from GCC Commits ---
The master branch has been updated by Nathaniel Shead :
https://gcc.gnu.org/g:14338386970bc6c2d46b81181f48622fdf25d705
commit r14-8168-g14338386970bc6c2d46b81181f48622fdf25d705
Author: Nathaniel Shead
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96388
--- Comment #17 from GCC Commits ---
The master branch has been updated by Maxim Kuvyrkov :
https://gcc.gnu.org/g:0c42d1782e48d8ad578ace2065cce9b3615f97c0
commit r14-8174-g0c42d1782e48d8ad578ace2065cce9b3615f97c0
Author: Maxim Kuvyrkov
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111554
--- Comment #13 from GCC Commits ---
The master branch has been updated by Maxim Kuvyrkov :
https://gcc.gnu.org/g:0c42d1782e48d8ad578ace2065cce9b3615f97c0
commit r14-8174-g0c42d1782e48d8ad578ace2065cce9b3615f97c0
Author: Maxim Kuvyrkov
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96388
Maxim Kuvyrkov changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88935
--- Comment #10 from Xi Ruoyao ---
(In reply to Jonathan Wakely from comment #9)
> (In reply to Xi Ruoyao from comment #7)
> > The C++11 standard explicitly allows to use rand() as the random source for
> > random_shuffle, thus this is not a bug
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112684
David Malcolm changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113360
--- Comment #2 from Marek Polacek ---
Idea: use cp_function_chain->invalid_constexpr to not to attempt to
explain_invalid_constexpr_fn.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110205
Andrew Macleod changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113428
Bug ID: 113428
Summary: [14 regression] gcc.dg/gomp/bad-array-section-c-3.c
fails after r14-7158-gb5476e4c881b0d
Product: gcc
Version: 14.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113424
Andrew Pinski changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91624
--- Comment #1 from GCC Commits ---
The master branch has been updated by John David Anglin :
https://gcc.gnu.org/g:3867dfc3062c7216d05a4691c79edbc0bb455713
commit r14-8157-g3867dfc3062c7216d05a4691c79edbc0bb455713
Author: John David Anglin
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113431
--- Comment #7 from Patrick O'Neill ---
(In reply to JuzheZhong from comment #6)
> (In reply to Patrick O'Neill from comment #5)
> > (In reply to JuzheZhong from comment #4)
> > > a[0][1] seems to be undefined value.
> >
> > a is a global
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113429
--- Comment #5 from JuzheZhong ---
Hi, Vineet.
I failed to compile it.
bug.f90:2:7:
2 | use shr_kind_mod,b => shr_kind_r8
| 1
Fatal Error: Cannot open module file 'shr_kind_mod.mod' for reading at (1): No
such file or
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113429
--- Comment #6 from Vineet Gupta ---
Created attachment 57111
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57111=edit
additional modules
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113416
Andrew Pinski changed:
What|Removed |Added
Host|x86_64-pc-linux-gnu |
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113433
Andrew Pinski changed:
What|Removed |Added
Keywords||missed-optimization
Ever
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113431
Andrew Pinski changed:
What|Removed |Added
Target|riscv |riscv aarch64-linux-gnu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113430
--- Comment #1 from Sam James ---
If you could find the time to bisect the kernel (perhaps in a VM), that may
well be helpful.
Would also be interesting to know if Clang suffers from the same thing (given
we import libsanitizer from them).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113221
Andrew Pinski changed:
What|Removed |Added
URL||https://gcc.gnu.org/piperma
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111693
--- Comment #10 from GCC Commits ---
The master branch has been updated by Sandra Loosemore :
https://gcc.gnu.org/g:25bb8a40abd91fccf9a59dd6518a7a283433dea3
commit r14-8173-g25bb8a40abd91fccf9a59dd6518a7a283433dea3
Author: Sandra Loosemore
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111693
sandra at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113418
--- Comment #3 from Xi Ruoyao ---
In gcc.dg:
align-2.c
analyzer/torture/pr93350.c
analyzer/torture/uninit-bit-field-ref.c
bic-bitmask-13.c
bic-bitmask-14.c
bic-bitmask-15.c
bic-bitmask-16.c
bic-bitmask-17.c
bic-bitmask-18.c
bic-bitmask-19.c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113435
Bug ID: 113435
Summary: Missed optimization of loop invariant elimination
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113412
--- Comment #3 from kargl at gcc dot gnu.org ---
Created attachment 57109
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57109=edit
patch
The attached patch has been regtested. There were no regression.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111956
--- Comment #18 from Gaius Mulley ---
Created attachment 57110
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57110=edit
Work in progress fix
Many thanks for the config.gcc hints! It now builds on gcc120 and gcc135 with
the work in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110251
--- Comment #15 from Anonymous ---
(In reply to Andrew Pinski from comment #10)
> (In reply to Anonymous from comment #9)
> > (In reply to Andrew Pinski from comment #1)
> > > dom3 :
> > > ```
> >
> > Could you please explain on how you to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113419
Andrew Pinski changed:
What|Removed |Added
Keywords||missed-optimization
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113431
--- Comment #6 from JuzheZhong ---
(In reply to Patrick O'Neill from comment #5)
> (In reply to JuzheZhong from comment #4)
> > a[0][1] seems to be undefined value.
>
> a is a global variable so the elements are initialized to 0. a[0][1] is
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113431
--- Comment #8 from JuzheZhong ---
(In reply to Patrick O'Neill from comment #7)
> (In reply to JuzheZhong from comment #6)
> > (In reply to Patrick O'Neill from comment #5)
> > > (In reply to JuzheZhong from comment #4)
> > > > a[0][1] seems
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112973
--- Comment #1 from GCC Commits ---
The master branch has been updated by Sandra Loosemore :
https://gcc.gnu.org/g:fce3f51f9c252c2650b2bf90401c72cda0eae088
commit r14-8171-gfce3f51f9c252c2650b2bf90401c72cda0eae088
Author: Sandra Loosemore
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113433
Bug ID: 113433
Summary: [12/13/14 Regression] Missed optimization for
redundancy computation elimination
Product: gcc
Version: 14.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113416
--- Comment #1 from Andrew Pinski ---
I thought I saw something similar before for aarch64 and SVE. Maybe OpenMP .
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113434
Bug ID: 113434
Summary: [13/14 Regression] Missed optimization for Loop
Unswitch
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113418
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113419
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113431
--- Comment #4 from JuzheZhong ---
a[0][1] seems to be undefined value.
And the test seems to trigger undefined behavior.
I just checked ARM SVE and RVV.
The vectorized IR is totally the same and I don't see anything obviously wrong
in
RVV
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113431
--- Comment #5 from Patrick O'Neill ---
(In reply to JuzheZhong from comment #4)
> a[0][1] seems to be undefined value.
a is a global variable so the elements are initialized to 0. a[0][1] is within
the bounds a[2][9].
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112973
sandra at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113434
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113430
--- Comment #2 from Sam James ---
Ah, I see you mentioned the recent ASLR kerfuffle in
https://github.com/llvm/llvm-project/issues/78354#issuecomment-1894606165.
That config in some distros' kernel configs change was made for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113418
Kewen Lin changed:
What|Removed |Added
CC||linkw at gcc dot gnu.org
--- Comment #4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113430
Xi Ruoyao changed:
What|Removed |Added
Summary|Trivial program segfaults |Trivial program segfaults
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113430
--- Comment #4 from Sam James ---
(In reply to Xi Ruoyao from comment #3)
I didn't update it because I wasn't certain if it was the same thing, although
it seems very likely. But fair enough.
101 - 164 of 164 matches
Mail list logo