https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119020
Bug ID: 119020
Summary: Problem of constexpr static lambda and maybe GCC
accepts invalid
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119016
Tamar Christina changed:
What|Removed |Added
Priority|P3 |P1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116855
--- Comment #9 from GCC Commits ---
The master branch has been updated by Tamar Christina :
https://gcc.gnu.org/g:ebe7cd9f2833a79877fbc56829c4f37a518a9b1d
commit r15-7711-gebe7cd9f2833a79877fbc56829c4f37a518a9b1d
Author: Tamar Christina
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118464
--- Comment #15 from GCC Commits ---
The master branch has been updated by Tamar Christina :
https://gcc.gnu.org/g:ebe7cd9f2833a79877fbc56829c4f37a518a9b1d
commit r15-7711-gebe7cd9f2833a79877fbc56829c4f37a518a9b1d
Author: Tamar Christina
Date
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118835
--- Comment #4 from GCC Commits ---
The releases/gcc-13 branch has been updated by Stefan Schulze Frielinghaus
:
https://gcc.gnu.org/g:b7466cff8cd4984cea6a2a134c54ca18e20f3fb3
commit r13-9399-gb7466cff8cd4984cea6a2a134c54ca18e20f3fb3
Author: S
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119019
Bug ID: 119019
Summary: -Wshadow false negative for function parameter (used
as array length expression) shadowing a global
variable
Product: gcc
Version: 14.2.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118994
--- Comment #7 from Hongtao Liu ---
diff --git a/gcc/match.pd b/gcc/match.pd
index 5c679848bdf..d6a465c963c 100644
--- a/gcc/match.pd
+++ b/gcc/match.pd
@@ -11348,3 +11348,28 @@ and,
}
(if (full_perm_p)
(vec_perm (op@3 @0 @
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108369
--- Comment #22 from kargls at comcast dot net ---
On 2/25/25 20:28, jvdelisle at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108369
>
> --- Comment #21 from Jerry DeLisle ---
> (In reply to kargls from comment #20)
>>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108369
--- Comment #21 from Jerry DeLisle ---
(In reply to kargls from comment #20)
> (In reply to Jerry DeLisle from comment #19)
> >
> > What this is doing is invoking -std=legacy for files with suffixes that
> > imply legacy files such as .f
> >
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114298
Andrew Pinski changed:
What|Removed |Added
CC||luigighiron at gmail dot com
--- Commen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119018
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|UNCONFIRME
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119018
--- Comment #1 from Andrew Pinski ---
https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2022/p2711r1.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108369
--- Comment #20 from kargls at comcast dot net ---
(In reply to Jerry DeLisle from comment #19)
>
> What this is doing is invoking -std=legacy for files with suffixes that
> imply legacy files such as .f
>
> This is my first dive on the lang-spe
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119018
Bug ID: 119018
Summary: Some iota_view constructors are missing explicit
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108369
--- Comment #19 from Jerry DeLisle ---
Created attachment 60593
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=60593&action=edit
Possible patch to change compile behavior
This patch changes the fortran/lang-spec.h as a possible better app
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108680
--- Comment #12 from Jerry DeLisle ---
"The keyword INTEGER with no kind-selector specifies type integer with default
kind; the kind type parameter value is equal to KIND (0). The decimal exponent
range of default integer shall be at least 5." -
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119014
--- Comment #8 from Vincent Lefèvre ---
(In reply to Jakub Jelinek from comment #6)
> I don't think that is true.
Indeed, it seems that I did some mistake when searching the standard, which is
a bit contradictory about the case FLT_EVAL_METHOD
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117069
--- Comment #6 from Hongtao Liu ---
It looks like the testcase is fragile, it's supposed to check the compiler
ability of generating code_6_gottpoff_reloc instruction, but failed since
there's a seg_prefixed memory usage(r14-6242-gd564198f960a2f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117069
Hongtao Liu changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118753
Bug 118753 depends on bug 117069, which changed state.
Bug 117069 Summary: [15 Regression] gcc.target/i386/apx-ndd-tls-1b.c since
r15-268-g9dbff9c05520a7
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117069
What|Removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117069
Hongtao Liu changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117069
--- Comment #4 from Andrew Pinski ---
(In reply to Hongtao Liu from comment #3)
> Fixed.
Do we know what fixed it? As this requires a new binutils i have not tested it
yet.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118992
--- Comment #12 from Hongtao Liu ---
(In reply to H.J. Lu from comment #11)
> Created attachment 60590 [details]
> A patch
>
> Can you try this on SPEC CPU?
Sure.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118753
Bug 118753 depends on bug 117069, which changed state.
Bug 117069 Summary: [15 Regression] gcc.target/i386/apx-ndd-tls-1b.c since
r15-268-g9dbff9c05520a7
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117069
What|Removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108680
--- Comment #11 from kargls at comcast dot net ---
On 2/25/25 12:43, anlauf at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108680
>
> --- Comment #10 from anlauf at gcc dot gnu.org ---
> (In reply to Jerry DeLisle from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119017
--- Comment #1 from Andrew Pinski ---
Created attachment 60591
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=60591&action=edit
C++11 testcase
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119017
Andrew Pinski changed:
What|Removed |Added
Attachment #60591|0 |1
is obsolete|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119017
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119017
Bug ID: 119017
Summary: error on valid user defined literal
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119016
Sam James changed:
What|Removed |Added
CC||tnfchris at gcc dot gnu.org
Summ
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117342
--- Comment #18 from Khem Raj ---
(In reply to Andrew Pinski from comment #16)
> (In reply to Khem Raj from comment #15)
> > My problem was that I made the version to be 15.1.0
>
> How?
in yocto, we copy the tools/symlinks into locations manua
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117342
--- Comment #17 from Sam James ---
(In reply to Khem Raj from comment #15)
I don't think this is really the same problem. It can easily happen if you e.g.
build gcc 15 with newer binutils then downgrade (with any sort of gymnastics
in-between).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117342
--- Comment #16 from Andrew Pinski ---
(In reply to Khem Raj from comment #15)
> My problem was that I made the version to be 15.1.0
How?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118992
--- Comment #11 from H.J. Lu ---
Created attachment 60590
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=60590&action=edit
A patch
Can you try this on SPEC CPU?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93059
--- Comment #54 from GCC Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:2256e30874af2ef804bb19d2eba40f9c92953beb
commit r15-7706-g2256e30874af2ef804bb19d2eba40f9c92953beb
Author: Jonathan Wakely
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117342
Khem Raj changed:
What|Removed |Added
CC||raj.khem at gmail dot com
--- Comment #15 fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119009
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119012
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119016
Sam James changed:
What|Removed |Added
Attachment #60588|0 |1
is obsolete|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119016
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |15.0
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119016
--- Comment #1 from Sam James ---
Created attachment 60588
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=60588&action=edit
eol.c
-cet --disable-systemtap --enable-valgrind-annotations
--disable-vtable-verify --disable-libvtv --with-zstd --with-isl
--disable-isl-version-check --enable-default-pie --enable-host-pie
--enable-host-bind-now --enable-default-ssp --disable-fixincludes
--with-build-config='
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118753
Bug 118753 depends on bug 115028, which changed state.
Bug 115028 Summary: [15 regression] gcc.target/i386/pr101950-2.c FAILs since
r15-268-g9dbff9c05520a7
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115028
What|Removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115028
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115028
--- Comment #11 from GCC Commits ---
The trunk branch has been updated by Andrew Pinski :
https://gcc.gnu.org/g:892ee5ffba0760794a932e36771863a86ef2b271
commit r15-7705-g892ee5ffba0760794a932e36771863a86ef2b271
Author: Andrew Pinski
Date: T
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108680
--- Comment #10 from anlauf at gcc dot gnu.org ---
(In reply to Jerry DeLisle from comment #9)
> We can have only one default integer otherwise its not a default. Our
> default integer is KIND=4
Forgive me for being stupid, but leaving aside the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119001
qinzhao at gcc dot gnu.org changed:
What|Removed |Added
Assignee|qinzhao at gcc dot gnu.org |unassigned at gcc dot
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115458
--- Comment #19 from GCC Commits ---
The master branch has been updated by Vladimir Makarov :
https://gcc.gnu.org/g:2341f675edadd6370147d2bc55ca7761a7ecfaa1
commit r15-7700-g2341f675edadd6370147d2bc55ca7761a7ecfaa1
Author: Vladimir N. Makarov
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118991
--- Comment #8 from GCC Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:0bb431d0a77cf8dc790b9c61539b3eb6ab1710f0
commit r15-7699-g0bb431d0a77cf8dc790b9c61539b3eb6ab1710f0
Author: Jakub Jelinek
Date: T
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118991
--- Comment #7 from Roland Illig ---
On the other hand, since you already limit the temporary buffer to 16 hex
digits, you could as well use %#llx directly, as ULLONG_MAX is guaranteed to be
at least 2^64-1 since C99. Or can GCC itself be built
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118991
--- Comment #6 from Roland Illig ---
(In reply to Jakub Jelinek from comment #5)
> Fix for avr:
Looks good to me, apart from the typo "thre" in the comment.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117430
Jerry DeLisle changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118083
Patrick Palka changed:
What|Removed |Added
Target Milestone|--- |14.3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118083
--- Comment #2 from GCC Commits ---
The master branch has been updated by Patrick Palka :
https://gcc.gnu.org/g:1b9e4fe2ff5f4711406cdcf0e6e183b247d9f42b
commit r15-7698-g1b9e4fe2ff5f4711406cdcf0e6e183b247d9f42b
Author: Patrick Palka
Date: T
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119014
--- Comment #7 from Jakub Jelinek ---
Though, I think we should predefine __FLT_EVAL_METHOD__ to 16 rather than 0 for
-fexcess-precision=16.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119014
--- Comment #6 from Jakub Jelinek ---
(In reply to Vincent Lefèvre from comment #5)
> (In reply to Jakub Jelinek from comment #2)
> > That is the normal behavior of extended precision.
>
> If you think of FLT_EVAL_METHOD, then this applies *onl
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108233
Andre Vehreschild changed:
What|Removed |Added
Status|NEW |WAITING
--- Comment #1 from Andre V
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119014
Vincent Lefèvre changed:
What|Removed |Added
CC||vincent-gcc at vinc17 dot net
--- Com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119011
Paul Eggert changed:
What|Removed |Added
CC||eggert at gnu dot org
--- Comment #8 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118654
Iain Buclaw changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118654
--- Comment #1 from GCC Commits ---
The master branch has been updated by Iain Buclaw :
https://gcc.gnu.org/g:c17044e509824e5ed3de94c85a7a0dd71cfd9cc1
commit r15-7696-gc17044e509824e5ed3de94c85a7a0dd71cfd9cc1
Author: Iain Buclaw
Date: Tue F
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119011
--- Comment #7 from Alejandro Colomar ---
(In reply to Jonathan Wakely from comment #6)
> Not warning at all for a literal -1 seems reasonable to me. It's such a
> common idiom to compare to -1 for error checks.
>
> So suppress the warning only
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117047
--- Comment #24 from Sam James ---
Created attachment 60587
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=60587&action=edit
libgccjit.log.xz crashing
This log is from `'../src/bootstrap-emacs' -batch --no-site-file --no-site-lisp
-l com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117047
--- Comment #23 from Sam James ---
Created attachment 60586
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=60586&action=edit
Contents of /proc/cpuinfo on a machine which crashes
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119014
--- Comment #4 from Stefan Schulze Frielinghaus
---
Thanks for pointing this out. I was fearing that this is valid but wasn't
sure. Especially the difference between (_Float16) 42.42f16 and just the
constant without the cast, I didn't have on
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119015
Bug ID: 119015
Summary: [14 Regression] g++ -O2 uses huge amounts of time and
memory
Product: gcc
Version: 14.2.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117047
--- Comment #22 from David Malcolm ---
Created attachment 60584
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=60584&action=edit
Contents of /proc/cpuinfo on a machine that this crash *doesn't* happen on
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119011
--- Comment #6 from Jonathan Wakely ---
Not warning at all for a literal -1 seems reasonable to me. It's such a common
idiom to compare to -1 for error checks.
So suppress the warning only for the literal -1 (and no other spellings, such
as -1L
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117047
David Malcolm changed:
What|Removed |Added
CC||andrea.corallo at arm dot com,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119014
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |INVALID
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118785
--- Comment #12 from Martin Jambor ---
I have proposed a fix on the mailing list:
https://inbox.sourceware.org/gcc-patches/ri6tt8i58kq@virgil.suse.cz/T/#u
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117047
--- Comment #19 from David Malcolm ---
(In reply to David Malcolm from comment #12)
> Sam: what architectures/configurations do you see this on? Comment #0 was
> presumably aarch64, but I don't think comment #3 specified anything beyond
> it be
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119014
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118874
--- Comment #4 from ro at CeBiTec dot Uni-Bielefeld.DE ---
> --- Comment #3 from Jakub Jelinek ---
> Even just
[...]
> ICEs the same way, so this doesn't seem to be related to range for.
> Does this ICE even with older gcc versions which do sup
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119014
Richard Biener changed:
What|Removed |Added
Target||x86_64-*-*
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118874
Jakub Jelinek changed:
What|Removed |Added
CC||iains at gcc dot gnu.org,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119014
Bug ID: 119014
Summary: Extending _Float16 constant at compile and run time
differs
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117047
--- Comment #20 from David Malcolm ---
This looks like it might be x86_64-specific. If so, perhaps it's specific to a
particular microarchitecture?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119010
--- Comment #7 from Richard Biener ---
(In reply to Jan Hubicka from comment #5)
> I had patch to reduce max issue back to 4 (exactly because of the compile
> time slowdown and because the way we model decoder we own't issue more than
> 4 instru
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119010
--- Comment #6 from Richard Biener ---
(In reply to Jan Hubicka from comment #5)
> I had patch to reduce max issue back to 4 (exactly because of the compile
> time slowdown and because the way we model decoder we own't issue more than
> 4 instru
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119010
Jan Hubicka changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119010
Richard Biener changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119010
Richard Biener changed:
What|Removed |Added
Component|rtl-optimization|target
--- Comment #3 from Richard Bie
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119011
--- Comment #5 from Alejandro Colomar ---
(In reply to Jakub Jelinek from comment #4)
> (In reply to Alejandro Colomar from comment #3)
> > unsigned long == -1 does The Right Thing(tm). The -1 is first
> > sign-extended, and afterwards converte
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119010
--- Comment #2 from Richard Biener ---
Hmm, the automaton is the same as the znver4 one it seems. Here's it's
statistics, znver4_fpu is by far the largest:
Automaton `znver4'
5 NDFA states, 15 NDFA arcs
5 DFA state
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119011
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117047
--- Comment #18 from David Malcolm ---
I spent a large chunk of yesterday attempting to reproduce this, but
unfortunately I'm still not seeing it.
Is anyone seeing this on a machine in the compiler farm, and if so which?
Which specific version
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119011
--- Comment #3 from Alejandro Colomar ---
(In reply to Richard Biener from comment #2)
> Your point that unsigned long == -1 vs. unsigned long == -1u is not the same
> is a very good point to continue diagnosing this.
But the bug is actually in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119011
--- Comment #2 from Richard Biener ---
Your point that unsigned long == -1 vs. unsigned long == -1u is not the same
is a very good point to continue diagnosing this.
Now, for equality compares of operands of different sign but same precision
we
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118991
--- Comment #5 from Jakub Jelinek ---
Fix for avr:
2025-02-25 Jakub Jelinek
PR translation/118991
* config/avr/avr.cc (avr_print_operand): Print ival into
a temporary buffer and use %s in output_operand_lossage to mak
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118874
--- Comment #2 from Rainer Orth ---
Created attachment 60583
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=60583&action=edit
64-bit sparc-sun-solaris2.11 range-for2.ii
It still did yesterday night as of commit
5806279610783805286ebcd0af3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119013
Bug ID: 119013
Summary: LoongArch and RISC-V: Redundant sign-extension after
moving 32-bit values from FPR into 64-bit GPR
Product: gcc
Version: 15.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118991
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117955
Robin Dapp changed:
What|Removed |Added
CC||rdapp at gcc dot gnu.org
--- Comment #7 fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118991
--- Comment #3 from Joseph S. Myers ---
This sort of concatenation is not expected to work with gettext; except I think
for limited cases for standard PRI* etc. macros, translations are always for
literal strings, not ones concatenated with host
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118819
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #6
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118874
--- Comment #1 from Jakub Jelinek ---
Does this still FAIL even after the various recent range for fixes?
If yes, it would be helpful to have a preprocessed source, so that it can be
debugged with a cross-compiler.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118940
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119001
--- Comment #5 from Jakub Jelinek ---
Created attachment 60582
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=60582&action=edit
gcc15-pr119001.patch
Full untested patch.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119011
--- Comment #1 from Alejandro Colomar ---
Or maybe we can just make -Wsign-compare not warn on that, without adding
levels at all.
1 - 100 of 138 matches
Mail list logo