Skip to content

[SYCL][FPGA] Changing "slave" to "agent" #3494

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

Merged
merged 2 commits into from
Apr 8, 2021
Merged

[SYCL][FPGA] Changing "slave" to "agent" #3494

merged 2 commits into from
Apr 8, 2021

Conversation

aarogon
Copy link
Contributor

@aarogon aarogon commented Apr 6, 2021

All the instances of "slave" have been changed to "agent" following
inclusivity guidelines. Lit tests pass with the changes.

IntelFPGALocalStaticSlaveMemVar has been deprecated.

  All the instances of slave have been changed to agent following
  inclusivity guidelines. Lit tests pass with the changes.

  IntelFPGALocalStaticSlaveMemVar has been deprecated.
Copy link
Contributor

@AaronBallman AaronBallman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oof, we changed seven subject lists to emit different diagnostic text and only needed to change one test case. That suggests we're missing some test coverage for subject appertainment for these (that's not your problem to worry about in this review, just an observation).

@AaronBallman
Copy link
Contributor

Btw, thank you for working on this, it's a great cleanup!

@aarogon
Copy link
Contributor Author

aarogon commented Apr 7, 2021

I had intentionally left IntelFPGALocalStaticSlaveMemVar for deprecation reasons, because someone may be using it downstream.

@AaronBallman
Copy link
Contributor

I had intentionally left IntelFPGALocalStaticSlaveMemVar for deprecation reasons, because someone may be using it downstream.

I don't think it's worth it. Downstream users are welcome to add it back in their downstream if they still need it.

Copy link
Contributor

@AaronBallman AaronBallman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@bader bader merged commit 7f6909f into intel:sycl Apr 8, 2021
@keryell
Copy link
Contributor

keryell commented Apr 8, 2021

Interesting!
The code I am working on is full of AXI master and AXI slave... Any suggestion?
At the same time this is part of an existing specification :-( https://developer.arm.com/documentation/ihi0051/a/Introduction/About-the-AXI4-Stream-protocol

@AaronBallman
Copy link
Contributor

Interesting!
The code I am working on is full of AXI master and AXI slave... Any suggestion?
At the same time this is part of an existing specification :-( https://developer.arm.com/documentation/ihi0051/a/Introduction/About-the-AXI4-Stream-protocol

If the existing specification exposes identifiers with those names, there's not much we can do aside from file an issue with the spec authors about their naming choices. However, for identifiers under our control, I'd recommend picking synonyms that describe the functionality. Some better names could be: controller/follower, source/sink, primary/secondary, etc.

(As an aside, this is also a good chance to correct any uses of whitelist/blacklist into better terms like allowlist/denylist, or sometimes better yet, AllowedWhatevers/RejectedWhatevers.)

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.

5 participants