Skip to content

Apply RESTRICT_STATIC MSVC workaround to arm/cache.c as well #289

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

MarijnS95
Copy link

In #283 a workaround was introduced to remove the restrict static attributes on MSVC where it is not supported.

This was only defined and used in arm/api.h however and not in arm/cache.c, leading to this file to fail compilation because it is included in ARM_SRCS for the windows_arm64 target in BUILD.bazel.

Fix that by replacing restrict static with RESTRICT_STATIC which will be defined by the arm/api.h header that is already included in arm/cache.c.

In pytorch#283 a workaround was
introduced to remove the `restrict static` attributes on MSVC where it
is not supported.

This was only defined and used in `arm/api.h` however and not in
`arm/cache.c`, leading to this file to fail compilation because it is
included in `ARM_SRCS` for the `windows_arm64` target in `BUILD.bazel`.

Fix that by replacing `restrict static` with `RESTRICT_STATIC` which
will be defined by the `arm/api.h` header that is already included
in `arm/cache.c`.
@facebook-github-bot
Copy link
Contributor

Hi @MarijnS95!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at [email protected]. Thanks!

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

Successfully merging this pull request may close these issues.

2 participants