Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: rohan at rohanlean dot de
“char s[_Alignas (int) 7];” is accepted without warnings in strict C11 mode. I
cannot construct that declaration using the grammar in appendix A.2 of the
standard.
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: rohan at rohanlean dot de
Target Milestone: ---
Target: x86_64
The following code causes G++ to emit an "xorl %eax, %eax" on x86_64. I believe
the Itanium AB
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55546
Bug #: 55546
Summary: Static functions that are fully inlined can end up in
the object file
Classification: Unclassified
Product: gcc
Version: 4.7.2
Status:
: minor
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: rohan at rohanlean dot de
Created attachment 33384
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=33384&action=edit
small testcase
Suppose that three clas
++
Assignee: unassigned at gcc dot gnu.org
Reporter: rohan at rohanlean dot de
Target Milestone: ---
I am unsure if the optimisations I desire are allowed by the standard, so in
that sense this report is half a question. I believe it comes down mostly to
the interpretation of [expr.new
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=121177
--- Comment #2 from Rohan Lean ---
I have crossposted to the LLVM bugtracker at
https://github.com/llvm/llvm-project/issues/149661, because clang also does no
elisions here.
++
Assignee: unassigned at gcc dot gnu.org
Reporter: rohan at rohanlean dot de
Target Milestone: ---
I have hit the following error with `-g -std=c++23 -flto=auto
-fno-fat-lto-objects`, but not with `-O3 -DNDEBUG -std=c++23 -flto=auto
-fno-fat-lto-objects`:
```
internal compiler
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=121226
--- Comment #2 from Rohan Lean ---
Created attachment 61952
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=61952&action=edit
Preprocessed source
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: rohan at rohanlean dot de
Target Milestone: ---
The `stop_token` overload of `condition_variable_any` can sometimes return a
wrong result. The implementation in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=121237
--- Comment #1 from Rohan Lean ---
I copy pasted the wrong listing from the standard by mistake. The correct one
is:
```
while (!stoken.stop_requested()) {
if (pred())
return true;
if (wait_until(lock, abs_time) == cv_status::timeo
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=121237
--- Comment #2 from Rohan Lean ---
(The libstdc++ implementation corresponding to that overload also appears to
have the problem, however.)
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: rohan at rohanlean dot de
Target Milestone: ---
The following two files, compiled with `-std=c++23 -fmodules` give a runtime
exception, `format error: invalid width or precision in
12 matches
Mail list logo
