Skip to content
This repository has been archived by the owner on Nov 7, 2022. It is now read-only.

Export upstream memory barrier functions #5

Closed
andre-richter opened this issue Apr 4, 2019 · 3 comments
Closed

Export upstream memory barrier functions #5

andre-richter opened this issue Apr 4, 2019 · 3 comments
Labels
good first issue Good for newcomers help wanted Extra attention is needed

Comments

@andre-richter
Copy link
Member

Reexport memory barrier funcs from rust-lang/stdarch#557

@andre-richter andre-richter added help wanted Extra attention is needed good first issue Good for newcomers labels Apr 4, 2019
@rahealy
Copy link

rahealy commented Nov 26, 2019

Most of this is new to me but I think these are documented here:

https://doc.rust-lang.org/core/arch/arm/index.html
https://doc.rust-lang.org/core/arch/aarch64/index.html

If these are the correct dependencies would you prefer putting the re-exports in barriers.rs or removing barriers.rs and putting the re-exports into lib.rs?

@andre-richter
Copy link
Member Author

I gave this a shot some time ago, but memory fails me a bit.
I think re-exporting those had the unpleasant side effect that users of cortex-a then would need to add some experimental intrinsics global attribute to their top level file.

That's a bit against the intention of the crate for taking care of these hassles for the user.

Let me have a look again if the re-exporting is feasible under these circumstances and come back to you soon!

Thanks,
Andre

@andre-richter
Copy link
Member Author

Closing this for now since I lost track of it and don't have resources to implement this at the moment.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants