https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102194
Michael Kenzel changed:
What|Removed |Added
CC||michael.kenzel at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116872
--- Comment #7 from Michael Kenzel ---
Oh. Looks like I was looking at the wrong table… Sorry about that 😅
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116872
--- Comment #4 from Michael Kenzel ---
Quoting [lex.name]/1 (https://eel.is/c++draft/lex.name#1.sentence-2):
The program is ill-formed if an identifier does not conform to Normalization
Form C as specified in the Unicode Standard.
According to
++
Assignee: unassigned at gcc dot gnu.org
Reporter: michael.kenzel at gmail dot com
Target Milestone: ---
According to [lex.name]/1, a program that contains an identifier that's not in
Unicode Normalization Form C is ill-formed.
gcc does not seem to correctly diagnose this
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: michael.kenzel at gmail dot com
Target Milestone: ---
Initializing an unsigned integer like
unsigned int mask = -1;
or
unsigned int mask = ~0;
is common practice, guaranteed
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: michael.kenzel at gmail dot com
Target Milestone: ---
When passing structs of certain shape by value on x86-64 (seems to be specific
to this target), gcc 14 emits (fails to optimize
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114298
--- Comment #1 from Michael Kenzel ---
I just learned that this was apparently only added in C++23 (P2711 [1]), so I
was likely a bit too quick to open this issue…
[1]: https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2022/p2711r1.html
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: michael.kenzel at gmail dot com
Target Milestone: ---
[range.lazy.split.view][1] specifies the following constructor
constexpr explicit lazy_split_view(V base, Pattern pattern
: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: michael.kenzel at gmail dot com
Target Milestone: ---
The following example will reproduce the issue:
// A.ixx
module;
#include
export
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: michael.kenzel at gmail dot com
Target Milestone: ---
The following example will reproduce the issue:
// A.ixx
export module A;
export void fun
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: michael.kenzel at gmail dot com
Target Milestone: ---
When using a keyword as the name of an enum, gcc will issue a diagnostic about
the enum being "unnamed". This can be very
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: michael.kenzel at gmail dot com
Target Milestone: ---
The following example will reproduce the issue:
// A.ixx
export module A;
export struct
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: michael.kenzel at gmail dot com
Target Milestone: ---
When compiling a class with virtual member functions declared in a module
interface unit and defined in a module implementation
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: michael.kenzel at gmail dot com
Target Milestone: ---
repro: https://godbolt.org/z/h5f798eEY
Product: gcc
Version: 11.1.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: michael.kenzel at gmail dot com
Target Milestone: ---
The following code
: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: michael.kenzel at gmail dot com
Target Milestone: ---
The following code will reproduce the issue (seems to affect all versions of
gcc that support
16 matches
Mail list logo
