Summary: | sys-devel/gcc-6.4.0: std::shared_future broken on armv5 (was: sys-devel/llvm-4.0.1-r1) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Markus Meier <maekke> |
Component: | Current packages | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | CC: | arm, llvm, mgorny |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | ARM | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 637210 | ||
Attachments: | sys-devel:llvm-4.0.1-r1:20180318-204738.log.gz |
Description
Markus Meier
2018-03-19 19:35:00 UTC
maekke confirmed with a test case like: #include <future> std::shared_future<void> foo; that gcc errors out on this code on lower ARM versions. As for LLVM itself, I think it would be best to just mask it on the relevant profiles. Ping. Can we proceed in any way with LLVM stablereq? Otherwise, I'd like to proclaim arch team timeout and removing stable keywords from old versions of LLVM on arm. Versions long gone. |