-
Notifications
You must be signed in to change notification settings - Fork 5.6k
Commit
Summary: `std::atomic_wait()` and `std::atomic_notify_one()` are marked as unavailable. Not really sure what that means, but it seems to be breaking some open source builds #1527. Explicitly qualify the calls into those functions to try and fix the build break. Since we cannot conditionally import either of the above (because they are marked as unavailable), we can't rely on the standard implementations. To prevent ADL from kicking in when the standard-library defines these, we fully qualify these and use `tag_invoke` for the customization points used in tests. Reviewed By: davidtgoldblatt Differential Revision: D26742072 fbshipit-source-id: 9f44bbfd37530f5ecffa3e03d673cfb1df953299
- Loading branch information
There are no files selected for viewing
11 comments
on commit 8477e25
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi,
when will this release be deployed please? Flipper-Folly
is currently breaking all react native builds using Xcode 12.5, as shown here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi,
when will this release be deployed please?
Flipper-Folly
is currently breaking all react native builds using Xcode 12.5, as shown here
+1
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi,
when will this release be deployed please?
Flipper-Folly
is currently breaking all react native builds using Xcode 12.5, as shown here
+1
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is released from the folly side. However, flipper and react-native may be pinned to older revisions of folly and have not yet updated their pins and picked up this change.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very thanks , in my case only add line decribe in folly/synchronization/DistributedMutex-inl.h
and work
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very thanks , in my case only add line decribe in folly/synchronization/DistributedMutex-inl.h
and work
Where is the folly folder you are describing?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hoping for this to be released soon, currently preventing us from upgrading to 0.64.1 from 0.63.4
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
still looking for solutions
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same error right now
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Upgrade to 0.65, it's fixed there.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This works to me:
-
Open "DistributedMutex-inl.h" (VSCode) //Use ctrl + p if you dont find it
-
find this block of code:
template
void wakeTimedWaiters(Atomic* state, bool timedWaiters) {
if (UNLIKELY(timedWaiters)) {
atomic_notify_one(state); <---- replace this line with this----> folly::atomic_notify_one(state); // evade ADL
}
} -
clean build folder on xCode
-
build again
@aary FWIW libc++ marks the synchronization library as unavailable on Apple platforms because we couldn't guarantee that is was going to be ABI stable yet. See https://reviews.llvm.org/D96790 for tracking updates to this.