[Bug c++/56687] New: [C++11] No visibility check within static_assert

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56687 Bug #: 56687 Summary: [C++11] No visibility check within static_assert Classification: Unclassified Product: gcc Version: 4.8.0 Status: UNCONFIRMED Severity: normal

[Bug c++/51304] gcc segfaults for large -ftemplate-depth values (if depth is reached)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51304 --- Comment #4 from Antoine Poliakov 2013-03-20 16:52:35 UTC --- Yes, I also submitted the bug (15551) to clang. Doesn't seem to kill intel's icc though.

[Bug c++/56669] Short code causes segfault with large -ftemplate-depth

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56669 --- Comment #1 from Antoine Poliakov 2013-03-20 14:46:27 UTC --- Created attachment 29702 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=29702 error message from 4.8.0 with stack trace

[Bug c++/56669] New: Short code causes segfault with large -ftemplate-depth

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56669 Bug #: 56669 Summary: Short code causes segfault with large -ftemplate-depth Classification: Unclassified Product: gcc Version: 4.8.0 Status: UNCONFIRMED Severity: no

[Bug c++/56611] [C++11] Template instantiation failure with variadic arguments and template aliases

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56611 --- Comment #7 from Antoine Poliakov 2013-03-13 12:15:30 UTC --- Thanks. You can remove struct result1 (lines 11-15 in alias-decl-32.C) from the test-case, it's not necessary (I would have done it but it's a very minor edit and I don't hav

[Bug c++/56611] [C++11] Template instantiation failure with variadic arguments and template aliases

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56611 --- Comment #3 from Antoine Poliakov 2013-03-13 11:12:25 UTC --- (In reply to comment #1) > The attachment is missing. Thanks! I got an error on first upload, but I thought it was ok - sorry.

[Bug c++/56611] [C++11] Template instanciation failure with variadic arguments and template aliases

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56611 --- Comment #2 from Antoine Poliakov 2013-03-13 11:09:19 UTC --- Created attachment 29662 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=29662 g++ -std=c++11 -Wall -Wextra -c gcc-test.cpp

[Bug c++/56611] New: [C++11] Template instanciation failure with variadic arguments and template aliases

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56611 Bug #: 56611 Summary: [C++11] Template instanciation failure with variadic arguments and template aliases Classification: Unclassified Product: gcc Version: 4.7.2

[Bug libstdc++/53169] Memory leak in std::vector

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53169 --- Comment #6 from Antoine Poliakov 2012-04-30 15:31:17 UTC --- (In reply to comment #4) > (In reply to comment #3) > > You should probably use sbrk and/or experiment with > > Sorry, I meant use strace, *not* sbrk! malloc_trim(0) saved the day

[Bug libstdc++/53169] Memory leak in std::vector

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53169 --- Comment #5 from Antoine Poliakov 2012-04-30 15:27:16 UTC --- (In reply to comment #2) > So it's possible to get the memory libstdc+ allocates to be returned to the > system, but it's under the control of glibc, nothing to do with std::vector

[Bug libstdc++/53169] New: Memory leak in std::vector

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53169 Bug #: 53169 Summary: Memory leak in std::vector Classification: Unclassified Product: gcc Version: 4.7.0 Status: UNCONFIRMED Severity: critical Priority: P3