https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107444
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107712
--- Comment #1 from CVS Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:2f5c071860ba3f8ef67d0b9d8291a73766ce0a44
commit r13-4109-g2f5c071860ba3f8ef67d0b9d8291a73766ce0a44
Author: Jonathan Wakely
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107720
--- Comment #2 from CVS Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:dbdce6adb748b95be219f2f5fb97f844a0f9b840
commit r13-4111-gdbdce6adb748b95be219f2f5fb97f844a0f9b840
Author: Jonathan Wakely
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107726
Bug ID: 107726
Summary: Multiple bugs related to __gnu__::__target__
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107726
--- Comment #1 from cqwrteur ---
#if __has_cpp_attribute(__gnu__::__target__) && defined(__SSE2__) &&
!defined(__AVX2__)
[[__gnu__::__target__("default")]]
#elif __has_cpp_attribute(__gnu__::__flatten__)
[[__gnu__::__flatten__]]
#endif
inline vo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107712
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107725
David Malcolm changed:
What|Removed |Added
Blocks||97110
--- Comment #2 from David Malcolm
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107725
David Malcolm changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107726
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107726
Andrew Pinski changed:
What|Removed |Added
Target|x86_64-w64-mingw32, |x86_64-linux-gnu
|x86
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107711
David Malcolm changed:
What|Removed |Added
Summary|internal compiler error:|ICE with -fanalyzer with
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107707
anlauf at gcc dot gnu.org changed:
What|Removed |Added
CC||anlauf at gcc dot gnu.org
--
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107726
--- Comment #4 from cqwrteur ---
(In reply to Andrew Pinski from comment #3)
> Also please file an different issue for the non-ifunc case since it is a new
> feature.
https://godbolt.org/z/z5cexGEMK
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107727
Bug ID: 107727
Summary: error: multiversioning needs 'ifunc' which is not
supported on this target (x86_64-w64-mingw32 target)
Product: gcc
Version: 13.0
Status: UNCONFI
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107727
--- Comment #1 from cqwrteur ---
Here is how clang deals with it on x86_64-windows-gnu (it is how clang calls
x86_64-w64-mingw32)
https://godbolt.org/z/z5cexGEMK
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107707
--- Comment #3 from Steve Kargl ---
On Wed, Nov 16, 2022 at 09:16:17PM +, anlauf at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107707
>
> anlauf at gcc dot gnu.org changed:
>
>What|Removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107727
--- Comment #2 from cqwrteur ---
BTW. how could i detect this feature being available? I think
#if __has_cpp_attribute(__gnu__::__target__)
#endif
should not be true on targets that do not support it.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107455
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
--- Comment #3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106649
--- Comment #1 from CVS Commits ---
The trunk branch has been updated by Marek Polacek :
https://gcc.gnu.org/g:c85f8dbb173f45053f6d8849d27adc98d9668769
commit r13-4112-gc85f8dbb173f45053f6d8849d27adc98d9668769
Author: Marek Polacek
Date: We
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106649
Marek Polacek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98940
Bug 98940 depends on bug 106649, which changed state.
Bug 106649 Summary: [C++23] P2448 - Relaxing some constexpr restrictions
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106649
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107728
Bug ID: 107728
Summary: with -O0, libgcc in the first stage compiler has
reference to libc functions
Product: gcc
Version: 12.2.0
Status: UNCONFIRMED
Severity:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107726
--- Comment #5 from cqwrteur ---
(In reply to Andrew Pinski from comment #2)
> We have tests for multiversioning and they are passing with BFD ld.
>
> Also multiversioning requires ifunc support which is not implemented for
> Windows (I don't k
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107725
--- Comment #3 from Chris Uzdavinis ---
Ah, sorry I didn't realize that. Its use was suggested by Jason Turner in his
most recent C++ Weekly so I started to give it a try. Perhaps there will be an
influx of such premature reports since it was
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107727
--- Comment #3 from Andrew Pinski ---
What they do is basically have the resolver always called:
callq __cpu_indicator_init
movl__cpu_model+12(%rip), %eax
andl$1024, %eax # imm = 0x400
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107727
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Build|x86_64-linux-gnu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107727
--- Comment #5 from Andrew Pinski ---
(In reply to cqwrteur from comment #2)
> BTW. how could i detect this feature being available? I think
>
> #if __has_cpp_attribute(__gnu__::__target__)
>
> #endif
>
> should not be true on targets that do
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107707
--- Comment #4 from CVS Commits ---
The master branch has been updated by Harald Anlauf :
https://gcc.gnu.org/g:bdd784fc48a283d54f5f1e3cc2a0668c14dd3bee
commit r13-4113-gbdd784fc48a283d54f5f1e3cc2a0668c14dd3bee
Author: Steve Kargl
Date: Wed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107728
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |MOVED
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107148
Joseph S. Myers changed:
What|Removed |Added
CC||jsm28 at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107707
kargl at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107728
--- Comment #2 from Andrew Pinski ---
Move over, the functions are not optimized out at -O2 but rather they don't get
pulled in glibc building because another function is referenced.
Either libgcc should be built with -fdata-sections -ffunction
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107712
--- Comment #3 from cqwrteur ---
(In reply to Jonathan Wakely from comment #2)
> Should be fixed now.
Question about toupper or any functions in ctype.h
These functions are not thread-safe and they do incur a very high cost due to
calling into
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107725
--- Comment #4 from David Malcolm ---
Aha thanks: presumably "Ep 350 - The Right Way to Write C++ Code in 2022"?
I'm watching it now.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107729
Bug ID: 107729
Summary: unhelpful handling for PMF on Itanium ABI for inline
asm
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
P
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107729
--- Comment #1 from Andrew Pinski ---
:6:1: warning: unsupported size for integer register
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107729
--- Comment #2 from Andrew Pinski ---
(In reply to Andrew Pinski from comment #1)
> :6:1: warning: unsupported size for integer register
I get that when I use:
#%0 %1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107729
--- Comment #3 from Saleem Abdulrasool ---
(In reply to Andrew Pinski from comment #2)
> (In reply to Andrew Pinski from comment #1)
> > :6:1: warning: unsupported size for integer register
>
> I get that when I use:
> #%0 %1
This totally make
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107729
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |WONTFIX
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107711
--- Comment #8 from CVS Commits ---
The master branch has been updated by David Malcolm :
https://gcc.gnu.org/g:6e4962810fe5de95b807d1ac675df45a725e31a2
commit r13-4114-g6e4962810fe5de95b807d1ac675df45a725e31a2
Author: David Malcolm
Date: W
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107728
--- Comment #3 from Thomas Petazzoni ---
Thanks for the super quick feedback. Could you clarify "Move over, the
functions are not optimized out at -O2 but rather they don't get pulled in
glibc building because another function is referenced." ?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105278
--- Comment #5 from Andrew Pinski ---
Note I think GCC's -Wfloat-equal is more reasonible than Clang's
-Wliteral-range really. The reason is because even if something can be
represented exactly in floating point (e.g. 3.0 or even 0.0), you could
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105278
Andrew Pinski changed:
What|Removed |Added
Summary|no warning for precise |-Wliteral-range vs
|l
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107711
--- Comment #9 from David Malcolm ---
It's a use-after-free of the ident_hash hash_table. Testing a fix...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104630
--- Comment #2 from John ---
This issue is still in v12.2.0.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107720
--- Comment #3 from CVS Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:f69a8299c1d95548e1539227fb7b8f5581aeb29b
commit r13-4117-gf69a8299c1d95548e1539227fb7b8f5581aeb29b
Author: Jonathan Wakely
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107720
Jonathan Wakely changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107649
Jonathan Wakely changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107704
--- Comment #2 from Jeffrey A. Law ---
ACK. And as I mentioned, the RTL form looks like it ought to be caught by the
SH specific code to optimize T reg handling. I don't care enough about the SH
to try and debug a missed optimization though.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107730
Bug ID: 107730
Summary: Trivial -Wreturn-type false positive when function
marked static
Product: gcc
Version: 12.2.1
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107730
--- Comment #1 from Sam James ---
Note that if I drop 'static', the warning goes away. Clang does not warn at
all.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107730
Sam James changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107730
Sam James changed:
What|Removed |Added
Status|RESOLVED|CLOSED
--- Comment #3 from Sam James ---
h
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90259
Kewen Lin changed:
What|Removed |Added
Target|powerpc-e300c3-linux-gnu|powerpc*-linux-gnu
Status|ASSIGN
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107711
David Malcolm changed:
What|Removed |Added
Keywords||patch
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107731
Bug ID: 107731
Summary: error: invalid 'asm': invalid use of '%c'
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107731
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107731
--- Comment #2 from Xi Ruoyao ---
(In reply to Andrew Pinski from comment #1)
> %c does not mean anything in loongarch.
>
> The codes are not documented in the documentation for loonarch though but
> they currently only documented in loongarch.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107731
--- Comment #3 from Andrew Pinski ---
MIPS nor RISCV does not define a %c either.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107731
--- Comment #4 from Andrew Pinski ---
(In reply to Xi Ruoyao from comment #2)
> Interestingly it "worked" with GCC 12.2...
I don't see how it could work though.
62ec3b5352b3 (chenglulu 2021-11-27 14:58:21 +0800 4499) default:
62ec3b5352b3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78655
--- Comment #15 from rguenther at suse dot de ---
On Wed, 16 Nov 2022, amacleod at redhat dot com wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78655
>
> Andrew Macleod changed:
>
>What|Removed |Add
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107731
--- Comment #5 from Xi Ruoyao ---
(In reply to Andrew Pinski from comment #4)
> (In reply to Xi Ruoyao from comment #2)
> > Interestingly it "worked" with GCC 12.2...
No it does not work. I guess I typed the test command in a wrong SSH
session
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107679
Richard Biener changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107731
--- Comment #6 from chenglulu ---
(In reply to Andrew Pinski from comment #1)
> %c does not mean anything in loongarch.
>
> The codes are not documented in the documentation for loonarch though but
> they currently only documented in loongarch.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107686
Richard Biener changed:
What|Removed |Added
Known to fail|13.0|
Summary|[12/13 Regression]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107731
--- Comment #7 from chenglulu ---
(In reply to Andrew Pinski from comment #3)
> MIPS nor RISCV does not define a %c either.
These two architectures can also fail under the following conditions:
void
test(void)
{
asm (".long %c0"
::"i"
101 - 166 of 166 matches
Mail list logo