ty: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: myriachan at gmail dot com
Target Milestone: ---
The following with -std=c++17 -Waddress:
int meow() { return 1; }
void kitty(int);
template
void test() {
if co
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94554
--- Comment #2 from Melissa ---
Templates that take an optional function pointer as a template parameter. It
lets you have templates that change behavior if a null function pointer is
passed.
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: myriachan at gmail dot com
Target Milestone: ---
Attempting to use one of the intrinsic x86 vector types like __m128 causes a
warning:
:9:30: warning: ignoring attributes on template argument '__m128 {aka
__vec
ty: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: myriachan at gmail dot com
Target Milestone: ---
GCC expects the "override" keyword in an incorrect position in the C++ grammar:
#define MEOW 256
struct Base {
: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: myriachan at gmail dot com
Target Milestone: ---
Consider the following C/C++ code with -O3 -fstrict-aliasing:
struct s1 {unsigned short x;};
struct s2 {unsigned short x
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82224
--- Comment #3 from Melissa ---
(In reply to Andrew Pinski from comment #1)
> See PR 14319 which I think this is a dup of.
PR 14319 refers to a case in which you are allowed to read the common prefix of
a structure when the structure is not the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82224
--- Comment #5 from Melissa ---
This originated from a Stack Overflow post "supercat" made (I'm the "Myria"
there).
https://stackoverflow.com/questions/46205744/is-this-use-of-unions-strictly-conforming/
: unassigned at gcc dot gnu.org
Reporter: myriachan at gmail dot com
Target Milestone: ---
x86's gcc/config/i386/cpuid.h contains the following comment:
/* Return highest supported input value for cpuid instruction. ext can
be either 0x0 or 0x800 to return highest supp
IRMED
Severity: normal
Priority: P3
Component: sanitizer
Assignee: unassigned at gcc dot gnu.org
Reporter: myriachan at gmail dot com
CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org,
jakub at gcc dot gnu.org, kcc at gc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67333
Melissa changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55004
Bug 55004 depends on bug 67333, which changed state.
Bug 67333 Summary: [C++11][constexpr] constexpr functions incorrectly prohibit
taking references to volatile types
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67333
What|Remove
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65892
Melissa changed:
What|Removed |Added
CC||myriachan at gmail dot com
--- Comment #12
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65892
--- Comment #13 from Melissa ---
As for a reason why this should be allowed, all I need is to do is mention
struct sockaddr.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49604
Melissa changed:
What|Removed |Added
CC||myriachan at gmail dot com
--- Comment #3
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: myriachan at gmail dot com
Host: x86_64-unknown-linux-gnu
Target: x86_64-unknown-linux-gnu
Build: x86_64-unknown-linux-gnu
There
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61015
Melissa changed:
What|Removed |Added
CC||myriachan at gmail dot com
--- Comment #1
Priority: P3
Component: inline-asm
Assignee: unassigned at gcc dot gnu.org
Reporter: myriachan at gmail dot com
Target Milestone: ---
x86 intrinsics _addcarry_u32 and _addcarry_u64 generate silly code. For
example, the following function to get the result of a 64-bit
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49171
Melissa changed:
What|Removed |Added
CC||myriachan at gmail dot com
--- Comment #12
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: myriachan at gmail dot com
Target Milestone: ---
GCC 4.7.3 (at least) through GCC 6.0 reject the following due to "meow has
side-effects":
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: myriachan at gmail dot com
Target Milestone: ---
The following compiles on GCC 13.1.0 when it should not:
struct X { };
struct Y {
X x;
};
struct Z : X {
Y y
20 matches
Mail list logo