https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115420
Xi Ruoyao changed:
What|Removed |Added
CC||xry111 at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114532
--- Comment #10 from Xi Ruoyao ---
Anyway if you really require a specific order of some data you need to either
use -fno-toplevel-reorder, or group the data with a struct or linker script
explicitly.
Relying on any implicit behavior like
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114532
--- Comment #9 from Xi Ruoyao ---
Then will -fno-toplevel-reorder help?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114532
Xi Ruoyao changed:
What|Removed |Added
CC||xry111 at gcc dot gnu.org
--- Comment #6
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104165
--- Comment #13 from Xi Ruoyao ---
For anyone attempting to claim this not fixed for 13 or later please see
PR107986 first.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104165
Xi Ruoyao changed:
What|Removed |Added
CC||xry111 at gcc dot gnu.org
--- Comment #12
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115333
--- Comment #3 from Xi Ruoyao ---
Maybe we should make it the L3 size like Intel but I'm not sure. See the
reasoning in PR87444 comments.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115169
Xi Ruoyao changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115183
Xi Ruoyao changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115176
Xi Ruoyao changed:
What|Removed |Added
CC||xry111 at gcc dot gnu.org
--- Comment #2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114978
--- Comment #21 from Xi Ruoyao ---
(In reply to chenglulu from comment #19)
> diff --git a/gcc/config/loongarch/loongarch.cc
> b/gcc/config/loongarch/loongarch.cc
> index e7835ae34ae..6a808cb0a5c 100644
> --- a/gcc/config/loongarch/loongarch.cc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115169
Xi Ruoyao changed:
What|Removed |Added
Status|NEW |ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115169
Xi Ruoyao changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |xry111 at gcc dot
gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114978
Xi Ruoyao changed:
What|Removed |Added
Keywords|needs-bisection |missed-optimization
--- Comment #17 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115037
Xi Ruoyao changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109442
Xi Ruoyao changed:
What|Removed |Added
CC||hubicka at gcc dot gnu.org
--- Comment #18
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115037
Xi Ruoyao changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115014
--- Comment #11 from Xi Ruoyao ---
(In reply to Andrew Pinski from comment #10)
> int f(int *a)
> {
> int b;
> size_t t = (size_t)
> size_t t1 = (size_t)a;
> return *(int*)(((size_t))+(t-t1));
> }
>
> Is kinda of valid c but might fail
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115014
Xi Ruoyao changed:
What|Removed |Added
CC||xry111 at gcc dot gnu.org
--- Comment #5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114980
Xi Ruoyao changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114978
--- Comment #13 from Xi Ruoyao ---
(In reply to Chen Chen from comment #12)
> No. I used system default gcc.
AOSC backports *many* changes not in upstream GCC 13.2 to their "13.2":
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115001
Xi Ruoyao changed:
What|Removed |Added
Summary|pr109062.c fails on hybrid |[14/15 Regression]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115001
Bug ID: 115001
Summary: pr109062.c fails on hybrid Intel CPU
Product: gcc
Version: 14.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114978
--- Comment #9 from Xi Ruoyao ---
(In reply to chenglulu from comment #8)
> diff --git a/gcc/config/loongarch/loongarch-def.cc
> b/gcc/config/loongarch/loongarch-def.cc
> index e8c129ce643..f27284cb20a 100644
> ---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114980
Xi Ruoyao changed:
What|Removed |Added
Keywords||patch
--- Comment #9 from Xi Ruoyao ---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114980
Xi Ruoyao changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114980
Xi Ruoyao changed:
What|Removed |Added
Last reconfirmed||2024-05-08
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114980
--- Comment #6 from Xi Ruoyao ---
Looks like when the driver invokes cc1, -fdiagnostics-urls=never seems always
after -W... options:
$ echo "" | LANG= ./gcc/xgcc -fdiagnostics-urls=never -Wtarget-lifetime -x c -
-B gcc -v -c
Reading specs from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114980
--- Comment #5 from Xi Ruoyao ---
(In reply to Andrew Pinski from comment #4)
> -fdiagnostics-plain-output does:
> /* If you have changed the default diagnostics output, and this new
> output is not appropriately "plain"
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114980
--- Comment #3 from Xi Ruoyao ---
(In reply to Andrew Pinski from comment #2)
> I have not seen this failure ...
Yes it's strange. I didn't see the failures building 14.1.0-RC1 but I saw them
building 14.1.0, though RC1 definitely outputs the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114980
--- Comment #1 from Xi Ruoyao ---
Also happens for "command-line option ... is valid for ... but not for ..."
warnings:
$ env -i PATH=$PATH TERM=xterm-256colors cc hw.c -fdiagnostics-urls=never
-Wtarget-lifetime
cc1: warning: command-line
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114980
Bug ID: 114980
Summary: [14/15 Regression] -fdiagnostics-urls=never does not
suppress URLs in `'-Werror=' argument '-Werror=...'
not valid for ...` warnings
Product: gcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114978
--- Comment #4 from Xi Ruoyao ---
s/suspicious/skeptical/
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114978
Xi Ruoyao changed:
What|Removed |Added
Target||loongarch64-*-*
Component|fortran
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114978
Xi Ruoyao changed:
What|Removed |Added
Keywords||needs-bisection
--- Comment #2 from Xi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114848
Xi Ruoyao changed:
What|Removed |Added
Resolution|--- |FIXED
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114861
Xi Ruoyao changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114861
Xi Ruoyao changed:
What|Removed |Added
Last reconfirmed||2024-04-26
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114861
Xi Ruoyao changed:
What|Removed |Added
Keywords|needs-reduction |ice-on-valid-code
--- Comment #5 from Xi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114861
--- Comment #4 from Xi Ruoyao ---
(In reply to Jakub Jelinek from comment #3)
> m for register_operand???
Hmm indeed, the m alternative should be removed. I must had been sleeping when
I typed it...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114861
Xi Ruoyao changed:
What|Removed |Added
Priority|P3 |P2
--- Comment #2 from Xi Ruoyao ---
It
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114861
--- Comment #1 from Xi Ruoyao ---
Created attachment 58044
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58044=edit
Preprocessed source
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114861
Bug ID: 114861
Summary: LoongArch: Fail to build the kernel with -Os
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114848
Xi Ruoyao changed:
What|Removed |Added
Summary|longarch: epilogue in |loongarch: epilogue in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114848
Xi Ruoyao changed:
What|Removed |Added
CC||xry111 at gcc dot gnu.org
--- Comment #1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113235
--- Comment #13 from Xi Ruoyao ---
(In reply to David Malcolm from comment #10)
> (In reply to Jan Hubicka from comment #4)
> > I keep mentioning to Larabel that he should use -fno-semantic-interposition,
> > but he doesn't.
>
> Possibly a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114830
Xi Ruoyao changed:
What|Removed |Added
CC||xry111 at gcc dot gnu.org
--- Comment #3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114808
Xi Ruoyao changed:
What|Removed |Added
CC||xry111 at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114800
Xi Ruoyao changed:
What|Removed |Added
CC||xry111 at gcc dot gnu.org
--- Comment #1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114773
Xi Ruoyao changed:
What|Removed |Added
Resolution|FIXED |INVALID
--- Comment #6 from Xi Ruoyao ---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114773
Xi Ruoyao changed:
What|Removed |Added
CC||xry111 at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113499
Xi Ruoyao changed:
What|Removed |Added
CC||xry111 at gcc dot gnu.org
--- Comment #7
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114700
--- Comment #13 from Xi Ruoyao ---
And IIRC there are various suggestion saying "if you want -fwrapv, you are
likely actually wanting -fsanitize=signed-integer-overflow" and some plan
deprecating -fwrapv. So it's more important to fix the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114700
Xi Ruoyao changed:
What|Removed |Added
Summary|Front-end optimization |Front-end optimization
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113233
Xi Ruoyao changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113233
--- Comment #13 from Xi Ruoyao ---
Will we back port the fix to 13 and 12?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114645
--- Comment #10 from Xi Ruoyao ---
> rust's `chrono`
Note that this is really a bad example because of CVE-2020-26235.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93041
Xi Ruoyao changed:
What|Removed |Added
CC||xry111 at gcc dot gnu.org
--- Comment #12
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110027
Xi Ruoyao changed:
What|Removed |Added
CC||teodor_spaeren at riseup dot
net
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114637
Xi Ruoyao changed:
What|Removed |Added
CC||xry111 at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114638
Xi Ruoyao changed:
What|Removed |Added
CC||xry111 at gcc dot gnu.org
--- Comment #1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112919
Xi Ruoyao changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113233
Xi Ruoyao changed:
What|Removed |Added
Target Milestone|12.4|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113233
Xi Ruoyao changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114574
Xi Ruoyao changed:
What|Removed |Added
CC||xry111 at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114597
Xi Ruoyao changed:
What|Removed |Added
CC||xry111 at gcc dot gnu.org
--- Comment #4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114590
Xi Ruoyao changed:
What|Removed |Added
Status|RESOLVED|WAITING
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112919
--- Comment #20 from Xi Ruoyao ---
(In reply to chenglulu from comment #19)
> (In reply to Xi Ruoyao from comment #18)
> > (In reply to chenglulu from comment #17)
> >
> > > The results of spec2006 on LA464 are:
> > > -falign-labels=4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113233
Xi Ruoyao changed:
What|Removed |Added
Target Milestone|--- |12.4
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114511
Xi Ruoyao changed:
What|Removed |Added
Ever confirmed|0 |1
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114505
Xi Ruoyao changed:
What|Removed |Added
Keywords||needs-reduction
--- Comment #5 from Xi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114505
Xi Ruoyao changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114452
Xi Ruoyao changed:
What|Removed |Added
Status|REOPENED|NEW
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112919
--- Comment #18 from Xi Ruoyao ---
(In reply to chenglulu from comment #17)
> The results of spec2006 on LA464 are:
> -falign-labels=4 -falign-functions=32 -falign-loops=16 -falign-jumps=16
Would you send a patch for them or prefer I to do
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104817
Xi Ruoyao changed:
What|Removed |Added
CC||qing.zhao at oracle dot com
--- Comment #3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114464
Xi Ruoyao changed:
What|Removed |Added
CC||xry111 at gcc dot gnu.org
--- Comment #4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114466
Xi Ruoyao changed:
What|Removed |Added
CC||xry111 at gcc dot gnu.org
--- Comment #5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114465
Xi Ruoyao changed:
What|Removed |Added
Severity|normal |enhancement
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114465
Bug ID: 114465
Summary: "x % const1 % const2" should be optimized if const1 %
const2 == 0
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114452
--- Comment #3 from Xi Ruoyao ---
(In reply to Paweł Bylica from comment #2)
> I don't think this is related to lambdas. The following is also not
> optimized:
>
>
> using F = int (*)(int) noexcept;
>
> inline int impl(int x) noexcept {
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111573
Xi Ruoyao changed:
What|Removed |Added
CC||chfast at gmail dot com
--- Comment #3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114452
Xi Ruoyao changed:
What|Removed |Added
CC||xry111 at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114449
Xi Ruoyao changed:
What|Removed |Added
Keywords||missed-optimization
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114449
Xi Ruoyao changed:
What|Removed |Added
CC||xry111 at gcc dot gnu.org
--- Comment #1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114439
Xi Ruoyao changed:
What|Removed |Added
Priority|P3 |P1
--- Comment #3 from Xi Ruoyao ---
To
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114441
Xi Ruoyao changed:
What|Removed |Added
CC||xry111 at gcc dot gnu.org
--- Comment #4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114421
Xi Ruoyao changed:
What|Removed |Added
CC||xry111 at gcc dot gnu.org
--- Comment #3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114407
Xi Ruoyao changed:
What|Removed |Added
Resolution|--- |FIXED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89163
Xi Ruoyao changed:
What|Removed |Added
CC||xry111 at gcc dot gnu.org
--- Comment #3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89163
Xi Ruoyao changed:
What|Removed |Added
CC||Explorer09 at gmail dot com
--- Comment #2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114406
Xi Ruoyao changed:
What|Removed |Added
Resolution|--- |DUPLICATE
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114175
--- Comment #40 from Xi Ruoyao ---
mips patch: https://gcc.gnu.org/pipermail/gcc-patches/2024-March/648070.html
(tested with -mabi=64)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59863
Xi Ruoyao changed:
What|Removed |Added
CC||xry111 at gcc dot gnu.org
See
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114285
Xi Ruoyao changed:
What|Removed |Added
CC||xry111 at gcc dot gnu.org
--- Comment #9
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112470
--- Comment #14 from Xi Ruoyao ---
(In reply to Jakub Jelinek from comment #13)
> So, is there anything we should do about this PR, or just close it as
> necessary outcome of trying to be more secure when user asked for it?
At least it
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114175
--- Comment #36 from Xi Ruoyao ---
Do we need a backport to releases/gcc-13?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114175
--- Comment #28 from Xi Ruoyao ---
LoongArch patch (tested):
https://gcc.gnu.org/pipermail/gcc-patches/2024-March/647928.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114175
Xi Ruoyao changed:
What|Removed |Added
Target|riscv, loongarch, x86_64|riscv, loongarch, x86_64,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114363
Xi Ruoyao changed:
What|Removed |Added
Resolution|--- |INVALID
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113430
--- Comment #12 from Xi Ruoyao ---
(In reply to Dimitrij Mijoski from comment #8)
> This bug manifested at large on Github Actions CI/CI system in the last few
> days most likely because Ubuntu's kernel also got updated to use 32 random
> bits.
1 - 100 of 698 matches
Mail list logo