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

atomic_add_fetch_explicit doesn't compile on all platforms #2936

Closed
louberger opened this issue Aug 28, 2018 · 5 comments
Closed

atomic_add_fetch_explicit doesn't compile on all platforms #2936

louberger opened this issue Aug 28, 2018 · 5 comments
Assignees

Comments

@louberger
Copy link
Member

louberger commented Aug 28, 2018

see https://ci1.netdef.org/browse/FRR-FRRPULLREQ-CI003BUILD-5076
function introduced in #2933
...
28-Aug-2018 13:58:15 | lib/lib_clippy-memory.o: In function mt_count_alloc': 28-Aug-2018 13:58:15 | /home/ci/cibuild.5076/frr-source/lib/memory.c:42: undefined reference to atomic_add_fetch_explicit'
28-Aug-2018 13:58:15 | /home/ci/c

@mjstapp
Copy link
Contributor

mjstapp commented Aug 29, 2018

Hmm, wow, sorry to have broken something. are you certain that that fork has picked up the commit that introduced the new atomics? I do see that new api with an old gcc, but I don't seem to be able to look at the fork repo myself.

@louberger
Copy link
Member Author

louberger commented Aug 29, 2018 via email

@mjstapp
Copy link
Contributor

mjstapp commented Aug 29, 2018

by "fork repo" I meant "the labnconsulting repo where your fork lives" - I thought I would try to build with your branch, but I don't have access to it. I was able to use that new atomic on openbsd6 with gcc 4.2 and on ubuntu 14 with some slightly less old gcc 4, but just using frrouting master. I guess I will try setting up a freebsd 10 vm and repeating that test.

@mjstapp
Copy link
Contributor

mjstapp commented Aug 29, 2018

got it - stdatomic.h does not include aliases for all of the available gcc atomic primitives, which we seemed to have been relying on. sorry about that - will fix...

@mjstapp
Copy link
Contributor

mjstapp commented Aug 29, 2018

Should be fixed by PR 2942.

@qlyoung qlyoung closed this as completed Aug 31, 2018
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

3 participants