Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failing to build callcc test with g++-4.9 #52

Closed
DaoWen opened this issue Apr 13, 2017 · 3 comments
Closed

Failing to build callcc test with g++-4.9 #52

DaoWen opened this issue Apr 13, 2017 · 3 comments

Comments

@DaoWen
Copy link
Contributor

DaoWen commented Apr 13, 2017

The callcc test fails to build when using version 4.9 of the GCC toolchain. The compiler gives an error about ambiguous overloads of the callcc function, which I think is a known bug in gcc-4.9 that was fixed in gcc-5.

I got the same error on Linux for in both PowerPC (32-bit) and x86_64 builds. Unfortunately, gcc-4.9 was the newest compiler I was able to get installed on the 32-bit PowerPC system for testing, so without support for that toolchain I can't test the ppc/sysv/elf platform (see #50).

I tried adding an extra disable_overload to disambiguate the call, which allowed me to compile, but then the test failed due to bad values being passed through the continuation object... I will try to look at this again later, but you're obviously more familiar with the codebase, and I'm hoping if you can get g++-4.9 installed that you'll have a much easier time debugging this.

@olk
Copy link
Member

olk commented Apr 13, 2017

You could compile the unit-tests without "-std=c++" - then only fcontext-API (asm implementation) is tested.

I can check if a workaround is available for gcc-4.8/gcc-4.9 - several versions of clang, intel, msvc are able to build boost.context.

@DaoWen
Copy link
Contributor Author

DaoWen commented Apr 13, 2017

You could compile the unit-tests without "-std=c++" - then only fcontext-API (asm implementation) is tested.

Yes, I actually tried building with gcc-4.7 first (which doesn't support thread_local), and the fcontext tests passed. I suppose that should be sufficient for verifying the ppc32 code, so I won't worry about this issue anymore. Thanks!

@olk
Copy link
Member

olk commented Apr 13, 2017

fine - ty

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants