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

Link frontend contract tickets in the spec #1076

Merged
merged 4 commits into from
Feb 7, 2023
Merged

Link frontend contract tickets in the spec #1076

merged 4 commits into from
Feb 7, 2023

Conversation

burmako
Copy link
Contributor

@burmako burmako commented Feb 7, 2023

Now that we have clearly identified the deltas between how the StableHLO dialect is used by frontends and what is specced (see https://github.com/orgs/openxla/projects/6), I figured it would be good to link these deltas in the spec, so that it's clear what areas are expected to change in the near future.

As I was working on this pull request, I also called out several tickets which are not part of the Frontend Contract project, because they represented highly likely todos from the New Features project. I think this is also useful to include in the spec for the readers to understand the anticipated direction of StableHLO evolution.

Now that we have clearly identified the deltas between how the
StableHLO dialect is used by frontends and what is specced (see
https://github.com/orgs/openxla/projects/6), I figured it would be good
to link these deltas in the spec, so that it's clear what areas are
expected to change in the near future.
Copy link
Member

@sdasgup3 sdasgup3 left a comment

Choose a reason for hiding this comment

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

Thanks for bringing this up.

Other than the comments below, the following two tickets in frontend contract is not specified in the spec:
#606
#714

docs/spec.md Show resolved Hide resolved
docs/spec.md Show resolved Hide resolved
docs/spec.md Show resolved Hide resolved
docs/spec.md Show resolved Hide resolved
docs/spec.md Show resolved Hide resolved
docs/spec.md Show resolved Hide resolved
docs/spec.md Show resolved Hide resolved
@sdasgup3
Copy link
Member

sdasgup3 commented Feb 7, 2023

LGTM otherwise.

@sdasgup3 sdasgup3 self-requested a review February 7, 2023 19:17
@sdasgup3 sdasgup3 assigned burmako and unassigned sdasgup3 Feb 7, 2023
@burmako
Copy link
Contributor Author

burmako commented Feb 7, 2023

Thank you for the thorough review! To address the comment about #606 and #714, indeed I haven't included them in the PR because I didn't find a great way to call them out.

#606 is more of a double-check rather than something that I think will lead to change, and #714 is a particular case of the matter of associativity of reducers, so I figured it'd be fine to not mention them.

@burmako burmako merged commit 8cc948f into openxla:main Feb 7, 2023
@burmako burmako deleted the link branch February 7, 2023 19:33
GleasonK pushed a commit to GleasonK/stablehlo that referenced this pull request Feb 10, 2023
Now that we have clearly identified the deltas between how the StableHLO
dialect is used by frontends and what is specced (see
https://github.com/orgs/openxla/projects/6), I figured it would be good
to link these deltas in the spec, so that it's clear what areas are
expected to change in the near future.

As I was working on this pull request, I also called out several tickets
which are not part of the Frontend Contract project, because they
represented highly likely todos from the New Features project. I think
this is also useful to include in the spec for the readers to understand
the anticipated direction of StableHLO evolution.
atondwal pushed a commit to atondwal/stablehlo that referenced this pull request Mar 3, 2023
Now that we have clearly identified the deltas between how the StableHLO
dialect is used by frontends and what is specced (see
https://github.com/orgs/openxla/projects/6), I figured it would be good
to link these deltas in the spec, so that it's clear what areas are
expected to change in the near future.

As I was working on this pull request, I also called out several tickets
which are not part of the Frontend Contract project, because they
represented highly likely todos from the New Features project. I think
this is also useful to include in the spec for the readers to understand
the anticipated direction of StableHLO evolution.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants