[Bug c++/27935] New: gcc fails to compile code with operator delete(void*,size_t)
The following code (taken from §12.5 "Free Store" of the C++ Standards, with
some simplifications) fails to compile:
struct B
{
virtual ~B() { } // line 5
void operator delete(void*, size_t);
};
test.cpp:5: error: no suitable 'operator delete' for 'B'
(The code taken directly from the C++ standard without modification fails as
well)
if you remove the size_t parameter, it succeeds
This kind of code exists in KDE's khtml.
--
Summary: gcc fails to compile code with operator
delete(void*,size_t)
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: charles at kde dot org
GCC host triplet: gcc version 4.1.2 20060601 (prerelease) (Debian 4.1.1-1)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27935
[Bug c++/27935] gcc fails to compile code with operator delete(void*,size_t)
--- Comment #7 from charles at kde dot org 2006-06-08 13:04 --- Created an attachment (id=11635) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=11635&action=view) compiles on 4.0 just #include -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27935
[Bug c/64554] New: _mm_clmulepi64_si128 doesn't compile with -O2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64554
Bug ID: 64554
Summary: _mm_clmulepi64_si128 doesn't compile with -O2
Product: gcc
Version: 4.9.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: charles at kde dot org
The following trivial program:
#include
int main()
{
__m128i a, b;
_mm_clmulepi64_si128(a, b, 1);
}
Produces the following error at compile time:
In file included from test.c:1:0:
test.c: In function ‘main’:
/usr/lib/gcc/x86_64-linux-gnu/4.9/include/wmmintrin.h:116:1: error: inlining
failed in call to always_inline ‘_mm_clmulepi64_si128’: target specific option
mismatch
_mm_clmulepi64_si128 (__m128i __X, __m128i __Y, const int __I)
^
test.c:6:2: error: called from here
_mm_clmulepi64_si128(a, b, 1);
^
When compiled with the option -O2 or -O1. Compiling succeeds with -O0.
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/4.9/lto-wrapper
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 4.9.1-19'
--with-bugurl=file:///usr/share/doc/gcc-4.9/README.Bugs
--enable-languages=c,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr
--program-suffix=-4.9 --enable-shared --enable-linker-build-id
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix
--with-gxx-include-dir=/usr/include/c++/4.9 --libdir=/usr/lib --enable-nls
--with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug
--enable-libstdcxx-time=yes --enable-gnu-unique-object --disable-vtable-verify
--enable-plugin --with-system-zlib --disable-browser-plugin
--enable-java-awt=gtk --enable-gtk-cairo
--with-java-home=/usr/lib/jvm/java-1.5.0-gcj-4.9-amd64/jre --enable-java-home
--with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-4.9-amd64
--with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-4.9-amd64
--with-arch-directory=amd64 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar
--enable-objc-gc --enable-multiarch --with-arch-32=i586 --with-abi=m64
--with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic
--enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu
--target=x86_64-linux-gnu
Thread model: posix
gcc version 4.9.1 (Debian 4.9.1-19)
(Debian testing)
[Bug target/64554] _mm_clmulepi64_si128 doesn't compile with -O2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64554 --- Comment #1 from charles at kde dot org --- It does compile with -march=westmere or later. I guess this is intended behavior.
[Bug target/64554] _mm_clmulepi64_si128 doesn't compile with -O2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64554 --- Comment #3 from charles at kde dot org --- with "gcc test.c -O2" it fails with "gcc test.c -O2 -mpclmul" it succeeds.
[Bug target/64554] _mm_clmulepi64_si128 doesn't compile with -O2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64554 --- Comment #5 from charles at kde dot org --- No you're right. I could add, though, that the compiler should have said something. Also, why did it compile just fine with -O0?
[Bug debug/22318] New: debug info wrong for doubles followed by bools
This is a problem in gcc's default debug format. It works fine with -gstabs.
struct X
{
bool x;
double d;
};
int main()
{
X x;
x.d = 42.0;
}
When debugging with gdb, x.d will contain something wrong, (often something
like 5.301466631257326e-315). If you change the bool to another type or
remove that variable completely, the results are correct. If you move the bool
to the end of the structure, the results are also correct.
This bug does not affect the execution of the program.
I guess it's something to do with how gcc writes debug info for the size of a
bool in the structure, possibly related to packing.
I'm also able to reproduce this on gcc 3.3.4.
--
Summary: debug info wrong for doubles followed by bools
Product: gcc
Version: 3.3.6
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: debug
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: charles at kde dot org
CC: gcc-bugs at gcc dot gnu dot org
GCC host triplet: gcc version 3.3.6 (Debian 1:3.3.6-7)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22318
[Bug debug/22318] debug info wrong for doubles followed by bools
--- Additional Comments From charles at kde dot org 2005-07-06 01:24 --- Oh, and to add, if you change the double to an int, it works. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22318
[Bug c++/16829] default parameter can be not one of the last in template function
--- Additional Comments From charles at kde dot org 2005-07-06 01:26 --- I should point out that fixing the actual bug in question will fix the ICE itself. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16829
