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

fix issues with atomic operations #2604

Merged
merged 5 commits into from Apr 4, 2018
Merged

Conversation

rgerhards
Copy link
Member

@rgerhards rgerhards commented Apr 1, 2018

... on platforms that do not support them natively. None of them actually break building except when warning-free compile is enforced.

closes #2612

... which also resulted in problems with atomic instruction code not
being detected.
commit 87c8f47 fixed missing mutex
definition, but did not do so via the macros originally intended for
this purpose. It still was very useful, as the patch made omkafka
compile on systems without atomic operations. And did so without
causing any real overhead.

Nevertheless this commit now adjust to use the rsyslog-core intended
way of doing things.
can be considered cosmetic, but we really want a clean compile
@rgerhards rgerhards added the bug label Apr 1, 2018
@rgerhards rgerhards added this to the v8.35 milestone Apr 1, 2018
@rgerhards
Copy link
Member Author

@janmejay If you have second, I would appreciate if you could check the failed Travis build. An obvious cure is to cast away the sign difference, but I have not yet checked if that is problematic. If you do not have time, I'll do that later on. But if you know, that would be much appreciated.

@janmejay
Copy link
Member

janmejay commented Apr 2, 2018

@rgerhards fixed here: rgerhards#40 ( over #2604 )

Create support for unsigned 32-bit atomic arithmetic
@rgerhards rgerhards merged commit 600de2e into rsyslog:master Apr 4, 2018
@rgerhards rgerhards deleted the followup-2569 branch April 4, 2018 06:34
@lock
Copy link

lock bot commented Dec 27, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Dec 27, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

wrong configure switch for atomic ops
2 participants