boostorg / boostorg/build

Outdated Sparc processor list breaks atomic operations on Niagara processors

Open
#338 3 comments 0 reactions 1 assignee Claimed by @grafikrobot View on GitHub
bug transition
Dominant language
C++
Stars
251
Forks
63
PR merge metrics
No merged PRs in 30d

Description

See downstream bug with logs: https://bugs.gentoo.org/646234

The code tries to autodetect the processor architecture, and overrides (!) the CXXFLAGS by the user by appending the result of the autodetection. Sadly this does not know about anything newer than ultrasparc3 (gcc knows about -mcpu=niagara since 4.2). For all unknown processors it forces a fallback to v7, which is unnecessary since it's the compiler default if no architecture is passed, and it is extremely old and does not know about atomic operations on anything larger than single bytes. And to make it worse it doesn't link to libatomic then.

My suggestion is to entirely drop that code and just let the user pass what is deemed appropiate. This especially makes it much easier if I want to build a package for a machine that does not match the current type.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.