[Bug c++/87665] [8/9 Regression] gcc HEAD (svn: 265340) breaks elements on resize

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87665 Ville Voutilainen changed: What|Removed |Added CC||ville.voutilainen at gmail dot com

[Bug libstdc++/87619] sizeof(std::variant) can be reduced if its variant_size is UCHAR_MAX

||ville.voutilainen at gmail dot com Resolution|--- |FIXED --- Comment #2 from Ville Voutilainen --- Fixed.

[Bug c++/87051] is_trivially_move_constructible wrongly gives `false` for class with user-provided non-const copy constructor

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87051 --- Comment #2 from Ville Voutilainen --- Patch available: https://gcc.gnu.org/ml/gcc-patches/2018-09/msg00670.html

[Bug c++/87093] is_constructible (__is_constructible() instrinsic) explicitly instantiates conversion member function of source

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87093 Ville Voutilainen changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug c++/87093] is_constructible (__is_constructible() instrinsic) explicitly instantiates conversion member function of source

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87093 --- Comment #4 from Ville Voutilainen --- Patch available: https://gcc.gnu.org/ml/gcc-patches/2018-09/msg00484.html

[Bug c++/87093] is_constructible (__is_constructible() instrinsic) explicitly instantiates conversion member function of source

||ville.voutilainen at gmail dot com Assignee|unassigned at gcc dot gnu.org |ville.voutilainen at gmail dot com --- Comment #3 from Ville Voutilainen --- Mine.

[Bug c++/87051] is_trivially_move_constructible wrongly gives `false` for class with user-provided non-const copy constructor

||ville.voutilainen at gmail dot com Assignee|unassigned at gcc dot gnu.org |ville.voutilainen at gmail dot com --- Comment #1 from Ville Voutilainen --- I'll take a look.

[Bug c++/54367] [meta-bug] lambda expressions

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54367 Bug 54367 depends on bug 79133, which changed state. Bug 79133 Summary: lambda capture shadowing parameter & decltype confusion https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79133 What|Removed |Added

[Bug c++/79133] lambda capture shadowing parameter & decltype confusion

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79133 Ville Voutilainen changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug c++/86361] Compilation failed while other compiler(clang) able to compile code in question

||ville.voutilainen at gmail dot com Resolution|--- |DUPLICATE --- Comment #2 from Ville Voutilainen --- The lambda capturing k with a parameter named k is ill-formed as per Core DR 2211. Fix coming. *** This bug has been marked as a duplicate

[Bug c++/79133] lambda capture shadowing parameter & decltype confusion

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79133 Ville Voutilainen changed: What|Removed |Added CC||husain.255 at gmail dot com ---

[Bug c++/86398] is_trivially_constructible always returns true even when is_constructible returns false

||ville.voutilainen at gmail dot com Resolution|--- |FIXED --- Comment #8 from Ville Voutilainen --- Fixed.

[Bug c++/82882] [8 regression] ICE Segmentation fault

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82882 --- Comment #11 from Ville Voutilainen --- Also happens with a member function of a class template, thus: template struct X { void f(const char* a = ([]() noexcept -> const char* { enum { Size = 42 - 1 }; return "";

[Bug c++/82882] [8 regression] ICE Segmentation fault

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82882 --- Comment #10 from Ville Voutilainen --- Reproducer: template void f(const char* a = ([]() noexcept -> const char* { enum { Size = 42 - 1 }; return ""; }())); void g() { f(); } Looks like we don't

[Bug c++/82882] [8 regression] ICE Segmentation fault

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82882 --- Comment #9 from Ville Voutilainen --- The Qt problems are not fixed, this comes with the gcc-8 branch: qtbase/include/QtCore/../../../../qtbase/src/corelib/tools/qstringliteral.h:82:30: internal compiler error: Segmentation fault ([]()

[Bug c++/77513] -Wzero-as-null-pointer-constant vs 0, nullptr, NULL and __null

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77513 --- Comment #8 from Ville Voutilainen --- See r260973

[Bug c++/77513] -Wzero-as-null-pointer-constant vs 0, nullptr, NULL and __null

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77513 Ville Voutilainen changed: What|Removed |Added CC||ville.voutilainen at gmail dot com

[Bug c++/85889] lambda expression can capture structured bindings

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85889 Ville Voutilainen changed: What|Removed |Added CC||ville.voutilainen at gmail dot com

[Bug c++/35878] [LWG 2302] Useless NULL pointer check when constructing object

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=35878 Ville Voutilainen changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug libstdc++/85517] std::variant exception safety problems

||2018-04-25 CC||ville.voutilainen at gmail dot com Assignee|unassigned at gcc dot gnu.org |ville.voutilainen at gmail dot com Ever confirmed|0 |1 --- Comment #1 from Ville Voutilainen

[Bug c++/65923] False positive for warning about literal operator suffix and using

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65923 Ville Voutilainen changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug c++/65923] False positive for warning about literal operator suffix and using

||ville.voutilainen at gmail dot com Assignee|unassigned at gcc dot gnu.org |ville.voutilainen at gmail dot com --- Comment #6 from Ville Voutilainen --- Mine.

[Bug libstdc++/80654] is_trivially_copy_constructible fails with compiler error with vector of uncopyable objects

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80654 --- Comment #7 from Ville Voutilainen --- That's not a bug. You need to make the copy constructor of s conditionally deleted depending on whether T is copyconstructible. Otherwise the trait will result in true but the code will not compile due

[Bug libstdc++/84601] [8 Regression] std::optional<std::pair<int, int>> is not assignment copyable

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84601 Ville Voutilainen changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug c++/70431] [C++11] Out of line defaulted copy constructor of a union does not compile.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70431 Ville Voutilainen changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug libstdc++/84601] [8 Regression] std::optional<std::pair<int, int>> is not assignment copyable

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84601 Ville Voutilainen changed: What|Removed |Added CC||ville.voutilainen at gmail dot com

[Bug c++/83895] [8 Regression] -Wparentheses warns about pointer-to-member typedefs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83895 Ville Voutilainen changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug c++/83895] New: -Wparentheses warns about pointer-to-member typedefs

Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: ville.voutilainen at gmail dot com Target Milestone: --- Test: struct X; typedef int (X::*foo); gcc diagnoses this with warning: unnecessary parentheses in declaration of 'foo' [-Wparentheses] There's no danger

[Bug c++/81327] [8 Regression] cast to void* does not suppress -Wclass-memaccess

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81327 --- Comment #15 from Ville Voutilainen --- I would like to have the change be a DR. Anyway, I looked at the cast-less cases, they are in qtransform.h, which is included by at least QImage and QtGui, so there will be a fair amount of code that

[Bug c++/81327] [8 Regression] cast to void* does not suppress -Wclass-memaccess

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81327 --- Comment #13 from Ville Voutilainen --- I understand that, but considering that I plan to convince the committee that the bit-blasts like Qt does should be well-defined, the warning is a bit eager, cast or no cast. And since it does break

[Bug c++/81327] [8 Regression] cast to void* does not suppress -Wclass-memaccess

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81327 --- Comment #11 from Ville Voutilainen --- The issue is again that users of existing Qt versions will see the warnings, and they also turn to errors. I can fix the non-casting uses, but I would recommend removing this warning from -Wall as well.

[Bug c++/81327] [8 Regression] cast to void* does not suppress -Wclass-memaccess

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81327 --- Comment #8 from Ville Voutilainen --- I can confirm that this fixes the woes in building and using Qt as far as QVector is concerned. Now that we have this fix, I see that there are other bit-blasts that don't use casts. Would it be possible

[Bug c++/81327] [8 Regression] cast to void* does not suppress -Wclass-memaccess

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81327 --- Comment #6 from Ville Voutilainen --- As stated in the other comments, this breaks *users* of existing Qt versions. Any fix would apply to newer versions only. QVector bit-blasts an object of a type with a virtual table over an object of

[Bug libstdc++/68430] std::is_constructible::value == true for unconstructible type T

||ville.voutilainen at gmail dot com Resolution|--- |FIXED --- Comment #3 from Ville Voutilainen --- Our new compiler-powered is_constructible in gcc 8 no longer gives the completely wrong answer; it gives the semi-expected answer even though

[Bug libstdc++/56257] std::vector allows access to the elements of _Vector_base

||ville.voutilainen at gmail dot com Resolution|--- |WONTFIX --- Comment #4 from Ville Voutilainen --- We are not going to jump through hoops to prevent users from getting into portability trouble by writing code that the standard explicitly

[Bug libstdc++/57139] std::tuple conversion constructor does the wrong checks

||ville.voutilainen at gmail dot com Resolution|--- |FIXED --- Comment #4 from Ville Voutilainen --- This has been fixed by the implementation of Daniel's paper, http://open-std.org/JTC1/SC22/WG21/docs/papers/2015/n4387.html. The constructor

[Bug libstdc++/54043] [LWG 2221] cout << nullptr does not work

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54043 --- Comment #17 from Ville Voutilainen --- Initial patch is at https://gcc.gnu.org/ml/gcc-patches/2017-12/msg00112.html, will need to wait until next stage1 to continue on it.

[Bug libstdc++/54043] [LWG 2221] cout << nullptr does not work

||ville.voutilainen at gmail dot com Assignee|unassigned at gcc dot gnu.org |ville.voutilainen at gmail dot com --- Comment #16 from Ville Voutilainen --- Mine.

[Bug c++/81327] cast to void* does not suppress -Wclass-memaccess

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81327 --- Comment #3 from Ville Voutilainen --- By the way, this doesn't just block building Qt, but also using it for development, because all uses of QVector that end up default-constructing an element will run into this.

[Bug libstdc++/83066] [8 regression] 26_numerics/gcd/gcd_neg.cc fails since r254736

||ville.voutilainen at gmail dot com Resolution|--- |FIXED --- Comment #1 from Ville Voutilainen --- Fixed in r254785.

[Bug c++/80682] __is_trivially_constructible(void, int) returns true.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80682 Ville Voutilainen changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug libstdc++/82470] Structured bindings don't work with std::tuple if a type has a get member function

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82470 --- Comment #4 from Ville Voutilainen --- Ah yes, the compiler is indeed correct, the standard suggests looking up a member function. Time to fix the spec, then. :)

[Bug libstdc++/82470] Structured bindings don't work with std::tuple if a type has a get member function

, ||ville.voutilainen at gmail dot com --- Comment #1 from Ville Voutilainen --- The compiler is not supposed to look for member functions with structured bindings; this looks like a compiler bug. Jason?

[Bug c++/58107] missing destructor call after thrown exception in lambda capture

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58107 --- Comment #3 from Ville Voutilainen --- All versions on wandbox seem to give the desired/expected result, so we can close this.

[Bug c++/50169] "new struct X {{}};" incorrectly treated as an invalid struct-definition

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50169 Ville Voutilainen changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug c++/81327] cast to void* does not suppress -Wclass-memaccess

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81327 --- Comment #1 from Ville Voutilainen --- Note that this currently blocks building Qt with gcc 8. We could work around it by turning our void* casts to char* casts, but we have a preference for fixing this problem in the compiler.

[Bug c++/50169] "new struct X {{}};" incorrectly treated as an invalid struct-definition

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50169 --- Comment #4 from Ville Voutilainen --- I have sent this to Core for consideration.

[Bug libstdc++/80940] [7/8 Regression] Private inheritance from std::ostream - compilation error for custom operator <

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80940 Ville Voutilainen changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug libstdc++/80675] Incorrect implementation of LWG 2534

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80675 Ville Voutilainen changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug libstdc++/80675] Incorrect implementation of LWG 2534

||2017-06-09 CC||ville.voutilainen at gmail dot com Assignee|unassigned at gcc dot gnu.org |ville.voutilainen at gmail dot com Ever confirmed|0 |1 --- Comment #1 from Ville Voutilainen

[Bug libstdc++/80940] Private inheritance from std::ostream - compilation error for custom operator <

||2017-06-09 CC||ville.voutilainen at gmail dot com Assignee|unassigned at gcc dot gnu.org |ville.voutilainen at gmail dot com Ever confirmed|0 |1 --- Comment #1 from Ville Voutilainen

[Bug c++/80812] [8 Regression] ICE: in build_value_init_noctor, at cp/init.c:483

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80812 Ville Voutilainen changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug c++/80812] [8 Regression] ICE: in build_value_init_noctor, at cp/init.c:483

||ville.voutilainen at gmail dot com Assignee|unassigned at gcc dot gnu.org |ville.voutilainen at gmail dot com --- Comment #3 from Ville Voutilainen --- Mine.

[Bug libstdc++/80654] is_trivially_copy_constructible fails with compiler error with vector of uncopyable objects

||2017-05-17 CC||ville.voutilainen at gmail dot com Assignee|unassigned at gcc dot gnu.org |ville.voutilainen at gmail dot com Ever confirmed|0 |1 --- Comment #3 from Ville Voutilainen

[Bug c++/80682] __is_trivially_constructible(void, int) returns true.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80682 --- Comment #5 from Ville Voutilainen --- This patch doesn't fully provide the means for a library implementation to just call the intrinsic from the library trait. I have a patch that does, which I'm testing.

[Bug c++/80682] __is_trivially_constructible(void, int) returns true.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80682 --- Comment #4 from Ville Voutilainen --- Fixed on trunk thus far. Backporting in a couple of days.

[Bug c++/80682] __is_trivially_constructible(void, int) returns true.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80682 --- Comment #2 from Ville Voutilainen --- Initial patch: https://gcc.gnu.org/ml/gcc-patches/2017-05/msg00632.html

[Bug c++/80682] __is_trivially_constructible(void, int) returns true.

||2017-05-09 Assignee|unassigned at gcc dot gnu.org |ville.voutilainen at gmail dot com Ever confirmed|0 |1 --- Comment #1 from Ville Voutilainen --- I'll see what I can do. is_trivially_xible seems to return true here, dunno why yet

[Bug libstdc++/80579] std::vector::reserve should not require T to be moveable.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80579 --- Comment #4 from Ville Voutilainen --- (In reply to Marc Glisse from comment #2) > If I remember correctly (very doubtful), a paper was presented about option > 2, and option 1 was rejected (although we could still provide it as an >

[Bug libstdc++/80579] std::vector::reserve should not require T to be moveable.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80579 Ville Voutilainen changed: What|Removed |Added CC||ville.voutilainen at gmail dot com

[Bug c++/70167] Some const array prvalues are incorrectly treated as lvalues

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70167 --- Comment #2 from Ville Voutilainen --- This has been suggested as a value category checker: https://wandbox.org/permlink/rXQewIGjI2096UbA There are two cases in it that print "Bug!" with gcc.

[Bug c++/70167] Some const array prvalues are incorrectly treated as lvalues

|UNCONFIRMED |NEW Last reconfirmed||2017-04-11 CC||ville.voutilainen at gmail dot com Ever confirmed|0 |1 Known to fail||5.3.0, 6.3.0, 7.0

[Bug libstdc++/79141] [6/7 Regression] std::pair<int,int> p = {}; fails to compile due to ambiguous overload

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79141 Ville Voutilainen changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug libstdc++/79141] [6/7 Regression] std::pair<int,int> p = {}; fails to compile due to ambiguous overload

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79141 --- Comment #4 from Ville Voutilainen --- Fixed on trunk so far, backporting...

[Bug libstdc++/79141] [6/7 Regression] std::pair<int,int> p = {}; fails to compile due to ambiguous overload

||ville.voutilainen at gmail dot com Assignee|unassigned at gcc dot gnu.org |ville.voutilainen at gmail dot com --- Comment #2 from Ville Voutilainen --- Mine, patch available: https://gcc.gnu.org/ml/gcc-patches/2017-04/msg00034.html

[Bug c++/35878] [LWG 2302] Useless NULL pointer check when constructing object

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=35878 Ville Voutilainen changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |ville.voutilainen at gmail

[Bug libstdc++/69853] An inheriting constructor of the class that inherited std::tuple isn't called correctly

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69853 Ville Voutilainen changed: What|Removed |Added Status|SUSPENDED |RESOLVED Resolution|---

[Bug libstdc++/80165] Constexpr tuple of variant doesn't work

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80165 Ville Voutilainen changed: What|Removed |Added CC||ville.voutilainen at gmail dot com

[Bug c++/35878] [LWG 2302] Useless NULL pointer check when constructing object

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=35878 --- Comment #11 from Ville Voutilainen --- Fixed on trunk for C++17 mode, leaving open to enable in other standard modes later.

[Bug c++/35878] [LWG 2302] Useless NULL pointer check when constructing object

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=35878 Ville Voutilainen changed: What|Removed |Added Component|libstdc++ |c++ --- Comment #9 from Ville

[Bug libstdc++/35878] [LWG 2302] Useless NULL pointer check when constructing object

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=35878 Ville Voutilainen changed: What|Removed |Added CC||ville.voutilainen at gmail dot com

[Bug c++/57443] Captured variable hide the parameter if they have the same name in Lambdas

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57443 --- Comment #3 from Ville Voutilainen --- The resolution of Core Issue 2211 makes such code ill-formed.

[Bug libstdc++/80034] [5/6 Regression] unqualified calls to std::distance in std::list::sort

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80034 Ville Voutilainen changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug libstdc++/80034] [5/6 Regression] unqualified calls to std::distance in std::list::sort

||2017-03-13 CC||ville.voutilainen at gmail dot com Assignee|unassigned at gcc dot gnu.org |ville.voutilainen at gmail dot com Ever confirmed|0 |1 --- Comment #1 from Ville Voutilainen

[Bug libstdc++/78420] [5/6/7 Regression] std::less<T*> is not a total order with -O2 enabled

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78420 --- Comment #17 from Ville Voutilainen --- (In reply to Jens Maurer from comment #16) > I'd like to point out that there is no prohibition against writing > reinterpret_cast inside a constexpr function. It's just if you call that > function and

[Bug libstdc++/78420] [5/6/7 Regression] std::less<T*> is not a total order with -O2 enabled

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78420 --- Comment #14 from Ville Voutilainen --- Not in general, no, it doesn't have to always give a compile-time answer. But I believe the library intent is that when it compares compile-time constant pointers, it should give that answer at

[Bug libstdc++/78420] [5/6/7 Regression] std::less<T*> is not a total order with -O2 enabled

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78420 --- Comment #12 from Ville Voutilainen --- ..which is http://cplusplus.github.io/LWG/lwg-active.html#2491

[Bug libstdc++/78420] [5/6/7 Regression] std::less<T*> is not a total order with -O2 enabled

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78420 --- Comment #11 from Ville Voutilainen --- Ah, the plot thickens. Jens Maurer wrote: "Regarding the std::less issue, it seems a bug in the standard to require that it be constexpr and deliver a total order. After all, the addresses of

[Bug libstdc++/78420] std::less<T*> is not a total order with -O2 enabled

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78420 Ville Voutilainen changed: What|Removed |Added Known to work||4.5.4 Known to fail|

[Bug libstdc++/78420] std::less<T*> is not a total order with -O2 enabled

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78420 Ville Voutilainen changed: What|Removed |Added CC||ville.voutilainen at gmail dot com

[Bug c++/79094] New: Pack explansion in using-declaration rejects an attempt to inherit a pack of constructors

Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: ville.voutilainen at gmail dot com Target Milestone: --- template struct X : Args... { using Args::Args...; }; int main() { struct A {A() = default

[Bug libstdc++/78389] list::merge and list::sort are not exception safe

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78389 --- Comment #5 from Ville Voutilainen --- Fixed merge() on all active branches.

[Bug libstdc++/78389] list::merge and list::sort are not exception safe

||ville.voutilainen at gmail dot com Resolution|--- |FIXED --- Comment #2 from Ville Voutilainen --- Fixed on trunk.

[Bug libstdc++/78939] [C++17] interferes with structured binding from struct

||ville.voutilainen at gmail dot com Assignee|unassigned at gcc dot gnu.org |ville.voutilainen at gmail dot com --- Comment #5 from Ville Voutilainen --- Mine.

[Bug c++/78966] Unjustified variadic template instantiation

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78966 --- Comment #4 from Ville Voutilainen --- Note that clang also triggers the static_assert, so there might be something deeper going on here. :)

[Bug c++/78966] Unjustified variadic template instantiation

, ||ville.voutilainen at gmail dot com --- Comment #3 from Ville Voutilainen --- Jason, care to look at this? There have been suggestions along the lines that [temp.inst]/6 might mean that the template may or may not get instantiated, so I'm not sure whether

[Bug c++/78906] ICE with a member variable template whose type is a decltype of a member variable template of a class template

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78906 Ville Voutilainen changed: What|Removed |Added Keywords||ice-on-valid-code --- Comment #1

[Bug c++/78906] New: ICE with a member variable template whose type is a decltype of a member variable template of a class template

Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: ville.voutilainen at gmail dot com Target Milestone: --- template struct A { static constexpr int digits = 0; }; template

[Bug libstdc++/78058] Complex initialization of nested std::optional does not work

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78058 Ville Voutilainen changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug libstdc++/78058] Complex initialization of nested std::optional does not work

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78058 Ville Voutilainen changed: What|Removed |Added CC||ville.voutilainen at gmail dot com

[Bug libstdc++/78595] Unnecessary copies in _Rb_tree

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78595 Ville Voutilainen changed: What|Removed |Added Version|7.0 |unknown --- Comment #5 from Ville

[Bug libstdc++/78595] Unnecessary copies in _Rb_tree

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78595 --- Comment #4 from Ville Voutilainen --- (In reply to Jonathan Wakely from comment #3) While I'm at it, I'll move the constraint to the return type.

[Bug libstdc++/78595] Unnecessary copies in _Rb_tree

||2016-11-29 CC||ville.voutilainen at gmail dot com Assignee|unassigned at gcc dot gnu.org |ville.voutilainen at gmail dot com Ever confirmed|0 |1 --- Comment #1 from Ville Voutilainen

[Bug libstdc++/77495] optional assignment from {} acts weirdly

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77495 Ville Voutilainen changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug libstdc++/77495] optional assignment from {} acts weirdly

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77495 Bug 77495 depends on bug 77288, which changed state. Bug 77288 Summary: Std::experimental::optional::operator= implementation is broken in gcc 6.1 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77288 What|Removed

[Bug libstdc++/77288] Std::experimental::optional::operator= implementation is broken in gcc 6.1

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77288 Ville Voutilainen changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug c++/77999] GCC diagnoses usage of STL literal operators as invalid.

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77999 Ville Voutilainen changed: What|Removed |Added CC||ville.voutilainen at gmail dot com

[Bug c++/78031] Warning when a standard library UDL is brought to scope with a using-declaration

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78031 Ville Voutilainen changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug c++/78031] New: Warning when a standard library UDL is brought to scope with a using-declaration

: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: ville.voutilainen at gmail dot com Target Milestone: --- #include #include int main() { using std::literals::operator""s; std::cout << "

[Bug c++/77731] Parameter pack expansion doesn't work when used to define argument list

||2016-10-12 CC||ville.voutilainen at gmail dot com Ever confirmed|0 |1 --- Comment #1 from Ville Voutilainen --- Clang accepts the code.

<    1   2   3   4   5   6   >