--- Comment #7 from gpderetta at gmail dot com 2009-03-19 12:14 ---
Hi, I'm the author of Boost.Coroutine (not yet part of boost, but one day...).
I have the exact same problem: gcc caches the address of TLS variables across
function calls which breaks when coroutines move fro
++
Assignee: unassigned at gcc dot gnu.org
Reporter: gpderetta at gmail dot com
It seems that at least GCC 4.7 fails with an hard error on failure to lookup a
function via ADL in a sfinae context, if a function of that name is not visible
in scope. The following test fails to compile unless
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=26461
--- Comment #11 from Giovanni Deretta ---
In the last few years it has been clear that threads are not enough and
coroutines have seen a resurgence in many languages. Go, which is directly
supported by GCC, make them a first class construct; boos
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: gpderetta at gmail dot com
Target Milestone: ---
As an extension to C++, g++ allows the following:
struct B {
struct { int bar; };
};
int main()
{
B foo;
(void)foo.bar
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: gpderetta at gmail dot com
Target Milestone: ---
struct V {
virtual void foo();
};
struct wV final : V {
};
struct oV final : V {
void foo();
};
void call(V& x)
{
x.foo();
}
void call(wV& x)
{
