Product: gcc
Version: 4.3.2
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: bmerry at gmail dot com
GCC build triplet: x86_64-pc-linux-gnu
GCC host triplet: x86
Product: gcc
Version: 4.3.2
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: bmerry at gmail dot com
GCC build triplet: x86_64-pc-linux-gnu
GCC host triplet: x86
--- Comment #1 from bmerry at gmail dot com 2009-07-27 19:46 ---
Created an attachment (id=18258)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=18258&action=view)
Source file illustrating the problem
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40880
--- Comment #2 from bmerry at gmail dot com 2009-07-27 19:47 ---
Created an attachment (id=18259)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=18259&action=view)
Preprocessed file
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40880
--- Comment #1 from bmerry at gmail dot com 2009-07-27 19:48 ---
System threw an HTTP error 500 but managed to create a bug, so now there are
two copies. Rejecting this one, bug 40880 is the real one.
--
bmerry at gmail dot com changed:
What|Removed
--- Comment #5 from bmerry at gmail dot com 2009-07-28 07:28 ---
Thanks, I wasn't aware of that. It's slightly annoying that the behaviour is
different from glibc (I use -std=c89 so that the compiler keeps me honest,
since I'm working on code that has to compile on compi
: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: bmerry at gmail dot com
Created attachment 30378
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=30378&action=edit
Minimal test case
I don't claim to fully un
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57728
--- Comment #2 from Bruce Merry ---
(In reply to Jonathan Wakely from comment #1)
> The explicit instantiation declaration suppresses the definition of
> A::A() in defaulted.o, but the explicit instantiation definition
> doesn't cause that symbol
: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: bmerry at gmail dot com
Created attachment 30730
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=30730&action=edit
Minimal broken test case
It seems that in some cases explicit instantiation of a function t
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52764
Bug #: 52764
Summary: Including after fails to define
limit macros
Classification: Unclassified
Product: gcc
Version: 4.6.1
Status: UNCONFIRMED
Severity:
: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: bmerry at gmail dot com
Created attachment 31135
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=31135&action=edit
Patch to update raise statements to modern Python syntax
The pretty printers shipped with GCC 4.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58962
--- Comment #1 from Bruce Merry ---
I've now realised that this is actually just the tip of the iceberg - I suspect
that libstdc++'s pretty printers aren't Python 3 ready, while Ubuntu is
shipping a gdb linked to libython 3.3. Feel free to close i
: unassigned at gcc dot gnu.org
Reporter: bmerry at gmail dot com
Created attachment 31159
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=31159&action=edit
Preprocessed source
This minimal example causes GCC to ICE:
template class A {};
template
class B {
public:
stati
cement
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: bmerry at gmail dot com
I have code for which I am explicitly selecting debug containers from the
__gnu_debug namespace (I'm not using -D_GLIBCXX_DEBUG since it breaks the ABI
: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: bmerry at gmail dot com
Created attachment 31258
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=31258&action=edit
Sample case
GCC is accepting the attached code,
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59213
Bruce Merry changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: bmerry at gmail dot com
Target Milestone: ---
When using a pointer-to-member-function which is a template parameter on an
instance of a derived class, I get a warning about type
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58962
--- Comment #4 from Bruce Merry ---
Incidentally, the workaround I have been using is to just run the script
through 2to3. Since Python only tells you things have gone wrong when you
execute the code I can't guarantee that this fixes everything,
18 matches
Mail list logo
