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
Keywords|needs-reduction |ice-on-valid-code
--- Comment #5 from Xi Ru
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
Status|ASSIGNED|RESOLVED
Resolution|---
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=114978
Xi Ruoyao changed:
What|Removed |Added
Keywords||needs-bisection
--- Comment #2 from Xi Ruoy
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
--- Comment #4 from Xi Ruoyao ---
s/suspicious/skeptical/
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=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 optio
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 #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 #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
Xi Ruoyao changed:
What|Removed |Added
Last reconfirmed||2024-05-08
Assignee|unassigned at
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
Keywords||patch
--- Comment #9 from Xi Ruoyao ---
ht
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
> --- a/gcc/config/loongarch/loonga
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: testsuite
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]
|Intel
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://github.com/AOSC-Dev/aosc-os-abbs/tree/stable/core-deve
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=115014
Xi Ruoyao changed:
What|Removed |Added
CC||xry111 at gcc dot gnu.org
--- Comment #5 fr
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)&b;
> size_t t1 = (size_t)a;
> return *(int*)(((size_t)&b)+(t-t1));
> }
>
> Is kinda of valid c but might
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=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
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114978
Xi Ruoyao changed:
What|Removed |Added
Keywords|needs-bisection |missed-optimization
--- Comment #17 from Xi
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
--- Comme
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=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=115176
Xi Ruoyao changed:
What|Removed |Added
CC||xry111 at gcc dot gnu.org
--- Comment #2 fr
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=115169
Xi Ruoyao changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
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=104165
Xi Ruoyao changed:
What|Removed |Added
CC||xry111 at gcc dot gnu.org
--- Comment #12 f
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=114532
Xi Ruoyao changed:
What|Removed |Added
CC||xry111 at gcc dot gnu.org
--- Comment #6 fr
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
--- 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 -fcom
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=10837
Xi Ruoyao changed:
What|Removed |Added
CC||lukas.graetz@tu-darmstadt.d
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111786
Xi Ruoyao changed:
What|Removed |Added
Resolution|INVALID |DUPLICATE
--- Comment #2 from Xi Ruoyao --
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111887
Xi Ruoyao changed:
What|Removed |Added
CC||xry111 at gcc dot gnu.org
--- Comment #3 fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111930
Xi Ruoyao changed:
What|Removed |Added
CC||xry111 at gcc dot gnu.org
Severit
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106627
Xi Ruoyao changed:
What|Removed |Added
CC||xry111 at gcc dot gnu.org
--- Comment #7 fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112286
Xi Ruoyao changed:
What|Removed |Added
Last reconfirmed||2023-10-30
Severity|normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112286
--- Comment #2 from Xi Ruoyao ---
(In reply to chenglulu from comment #1)
> (In reply to Robin Lee from comment #0)
> > Follow-up from https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108682#c2
> >
> > libgo runtime needs an update.
> > gccgo build
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112286
--- Comment #3 from Xi Ruoyao ---
FWIW one nice aspect of gccgo is we don't need a pre-installed Go binary to
build it.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112286
--- Comment #5 from Xi Ruoyao ---
(In reply to chenglulu from comment #4)
> (In reply to Xi Ruoyao from comment #2)
> > (In reply to chenglulu from comment #1)
> > > (In reply to Robin Lee from comment #0)
> > > > Follow-up from https://gcc.gnu.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112299
Xi Ruoyao changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned at g
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112299
Xi Ruoyao changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112330
Bug ID: 112330
Summary: [14 Regression] LoongArch: LTO bootstrap failure with
GAS 2.41
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112330
--- Comment #1 from Xi Ruoyao ---
(In reply to Xi Ruoyao from comment #0)
> I guess the easiest solution is raising the minimal GAS requirement of
> bootstrapping GCC 14 on LoongArch to 2.42.
Another solution might be default to -mno-relax if
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112330
--- Comment #2 from Xi Ruoyao ---
Created attachment 56483
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56483&action=edit
The generated assembly triggering the GAS internal error
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112330
--- Comment #4 from Xi Ruoyao ---
(In reply to chenglulu from comment #3)
> (In reply to Xi Ruoyao from comment #1)
> > (In reply to Xi Ruoyao from comment #0)
> >
> > > I guess the easiest solution is raising the minimal GAS requirement of
> >
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112330
--- Comment #6 from Xi Ruoyao ---
(In reply to chenglulu from comment #5)
> (In reply to Xi Ruoyao from comment #4)
> > (In reply to chenglulu from comment #3)
> > > (In reply to Xi Ruoyao from comment #1)
> > > > (In reply to Xi Ruoyao from com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112330
--- Comment #8 from Xi Ruoyao ---
(In reply to chenglulu from comment #7)
> Uh, I also thought about this gcc and binutils matching issue when I
> submitted r14-4674, but I didn't think about whether this should be solved?
> How to fix it?
I'm
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112330
Xi Ruoyao changed:
What|Removed |Added
Summary|[14 Regression] LoongArch: |[14 Regression] LoongArch:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69549
Xi Ruoyao changed:
What|Removed |Added
CC||xry111 at gcc dot gnu.org
Keywords
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112330
--- Comment #11 from Xi Ruoyao ---
I cherry-picked f87cf663af71e5d78c8d647fa48562102f3b0615 for Binutils 2.41 and
get some better error message:
t.s:98064: Error: Reloc overflow
t.s:101127: Error: Reloc overflow
t.s:101453: Error: Reloc overflo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112330
--- Comment #13 from Xi Ruoyao ---
(In reply to chenglulu from comment #12)
> (In reply to Xi Ruoyao from comment #11)
> > I cherry-picked f87cf663af71e5d78c8d647fa48562102f3b0615 for Binutils 2.41
> > and get some better error message:
> >
> >
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112330
Xi Ruoyao changed:
What|Removed |Added
Keywords|build |
Summary|[14 Regression] LoongAr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112329
Xi Ruoyao changed:
What|Removed |Added
CC||xry111 at gcc dot gnu.org
Summar
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109035
Xi Ruoyao changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109035
Xi Ruoyao changed:
What|Removed |Added
Target Milestone|--- |14.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112364
Xi Ruoyao changed:
What|Removed |Added
CC||xry111 at gcc dot gnu.org
Statu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112364
--- Comment #3 from Xi Ruoyao ---
(In reply to Martin Uecker from comment #2)
> I don't think this is correct. The requirement is "The pointer returned if
> the allocation succeeds is suitably aligned so that it may be assigned to a
> pointer t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111315
Xi Ruoyao changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112364
--- Comment #5 from Xi Ruoyao ---
(In reply to Martin Uecker from comment #4)
> Interesting. But independently of alignment, the description of calloc makes
> it clear that it allocates an array of nmemb objects of size x. So in any
> case I th
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111930
--- Comment #3 from Xi Ruoyao ---
(In reply to Richard Sandiford from comment #1)
> We're aiming to add SME and SME2 support in GCC 14, hopefully by the end of
> the year.
Note that now we have only 2 weeks before GCC 14 stage 1 ends.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112442
Xi Ruoyao changed:
What|Removed |Added
Resolution|--- |INVALID
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112442
--- Comment #7 from Xi Ruoyao ---
Note that in the "new bug" page, there is a red banner saying:
Before reporting that GCC compiles your code incorrectly, compile it with gcc
-Wall -Wextra and see whether this shows anything wrong with your cod
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112442
--- Comment #10 from Xi Ruoyao ---
(In reply to Adam Andersson from comment #9)
> I was sure I had tried -fno-strict-aliasing without any difference, but I
> guessed I messed up somehow. Sorry about that.
>
> Still, is it not strange that -Wall
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112476
Xi Ruoyao changed:
What|Removed |Added
CC||xry111 at gcc dot gnu.org
Keyword
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110815
Xi Ruoyao changed:
What|Removed |Added
CC||xry111 at gcc dot gnu.org
--- Comment #3 fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112476
Xi Ruoyao changed:
What|Removed |Added
Last reconfirmed||2023-11-11
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112476
Xi Ruoyao changed:
What|Removed |Added
CC||chenglulu at loongson dot cn
--- Comment #3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112476
Xi Ruoyao changed:
What|Removed |Added
Component|rtl-optimization|target
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112483
Bug ID: 112483
Summary: [14 Regression] gfortran.dg/ieee/ieee_2.f90 fails on
loongarch64-linux-gnu at -O1 or above
Product: gcc
Version: 14.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112484
Bug ID: 112484
Summary: [14 Regression]
26_numerics/random/{poisson_distribution,negative_bino
mial_distribution}/operators/values.cc fails on
loongarch64-linux-gn
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112476
Xi Ruoyao changed:
What|Removed |Added
URL||https://gcc.gnu.org/piperma
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112486
Xi Ruoyao changed:
What|Removed |Added
CC||xry111 at gcc dot gnu.org
--- Comment #3 fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112487
Xi Ruoyao changed:
What|Removed |Added
Target Milestone|--- |14.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112483
Xi Ruoyao changed:
What|Removed |Added
CC||tamar.christina at arm dot com
Last recon
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112483
--- Comment #2 from Xi Ruoyao ---
(In reply to Xi Ruoyao from comment #1)
> gcc/ChangeLog:
>
> PR tree-optimization/109154
> * match.pd: Add new neg+abs rule, remove inverse copysign rule.
I guess the inverse c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112483
--- Comment #3 from Xi Ruoyao ---
Minimized test case:
! { dg-do run }
use, intrinsic :: ieee_arithmetic
implicit none
real :: sx1, sx2, sx3
double precision :: dx1, dx2, dx3
type(ieee_round_type) :: mode
! Test IEEE_COPY_SIGN
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112483
--- Comment #4 from Xi Ruoyao ---
In 268r.cse1:
(insn 26 25 27 2 (set (reg:SF 93)
(mem/u/c:SF (reg/f:DI 94) [0 S4 A32])) "ieee_2.f90":13:6 discrim 4 146
{*movsf_hardfloat}
(expr_list:REG_EQUAL (const_double:SF -1.0e+0 [-0x0.8p+1])
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112483
Xi Ruoyao changed:
What|Removed |Added
Component|target |rtl-optimization
--- Comment #5 from Xi Ruo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112497
Bug ID: 112497
Summary: Bootstrap comparison failure:
gcc/analyzer/constraint-manager.o differs on
loongarch64-linux-gnu
Product: gcc
Version: 14.0
S
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112497
Xi Ruoyao changed:
What|Removed |Added
Last reconfirmed||2023-11-12
Summary|Bootstrap com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112497
--- Comment #2 from Xi Ruoyao ---
FWIW, GCC configured with:
--with-system-zlib --disable-fixincludes --enable-default-ssp
--enable-default-pie --disable-werror --disable-multilib
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112497
--- Comment #4 from Xi Ruoyao ---
(In reply to Jeffrey A. Law from comment #3)
> If at all possible, cc Jin Ma in this since it's his change, I just reviewed
> and committed the bits on Jin's behalf.
I've replied the gcc-patch thread. It seems
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112497
Xi Ruoyao changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112497
Xi Ruoyao changed:
What|Removed |Added
Target Milestone|--- |14.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112483
--- Comment #8 from Xi Ruoyao ---
(In reply to Tamar Christina from comment #7)
> Yeah, that fold-rtx code is bogus. It's a latent bug.
>
> Optimizing copysign(x, -y) to neg(x) is just wrong.
>
> Will you be sending a patch Xi or do you want m
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112483
--- Comment #9 from Xi Ruoyao ---
*** Bug 112484 has been marked as a duplicate of this bug. ***
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112484
Xi Ruoyao changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Component|target
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112483
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=112476
Xi Ruoyao changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112483
Xi Ruoyao changed:
What|Removed |Added
Keywords||missed-optimization
--- Comment #11 from Xi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112483
Xi Ruoyao changed:
What|Removed |Added
Status|ASSIGNED|NEW
Assignee|xry111 at gcc dot gn
401 - 500 of 1049 matches
Mail list logo