c version 4.2.1 (Debian 4.2.1-6)
--
Summary: Nonexistent i386 register name `%SIL' used
Product: gcc
Version: 4.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
AssignedTo: unassigned at gcc dot gnu
86-64: Nonstandard instruction "movd %xmm0, %rax"
Product: gcc
Version: 4.4.3
Status: UNCONFIRMED
Severity: minor
Priority: P3
Component: target
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: richar
Severity: normal
Priority: P3
Component: inline-asm
Assignee: unassigned at gcc dot gnu.org
Reporter: richardpku at gmail dot com
Target Milestone: ---
I have been trying out the new "flag output constraints" feature in inline
assembly ("=@c
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: richardpku at gmail dot com
Target Milestone: ---
template concept bool A_concept = (... || (x < 0));
template constexpr bool A_constexpr = (... || (x < 0));
static_
o" does not work with LTO
Product: gcc
Version: 4.5.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: lto
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: richardpku at gmail dot com
GCC build
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: richardpku at gmail dot com
Target Milestone: ---
Minimal program to produce bug (run it on a platform where char is a
ormal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: richardpku at gmail dot com
Target Milestone: ---
Consider this program:
#include
#include
class A {
public:
A() { throw 42; }
~A() { puts("A::~A"); }
void opera
ponent: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: richardpku at gmail dot com
Target Milestone: ---
/tmp % cat a.cpp
#include
void* p;
void foo() { std::atomic_ref(p).store(nullptr); }
/tmp % g++-11.1.0 -c -std=gnu++20 a.cpp
In file included from
/usr/l
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100889
--- Comment #1 from Richard Li ---
Created attachment 50917
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50917&action=edit
Proposed patch
This patch fixes the problem.
