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

codegen should ideally not need to know the optimization level #123958

Closed
iritkatriel opened this issue Sep 11, 2024 · 6 comments
Closed

codegen should ideally not need to know the optimization level #123958

iritkatriel opened this issue Sep 11, 2024 · 6 comments
Assignees
Labels
interpreter-core (Objects, Python, Grammar, and Parser dirs)

Comments

@iritkatriel
Copy link
Member

iritkatriel commented Sep 11, 2024

Optimization level is used for things that can be done in ast_opt. I'll try to move them there.

Linked PRs

@hugovk
Copy link
Member

hugovk commented Sep 15, 2024

PR merged, closing issue.

@hugovk hugovk closed this as completed Sep 15, 2024
@iritkatriel iritkatriel reopened this Sep 15, 2024
@iritkatriel
Copy link
Member Author

There's another usage still to remove.

@hugovk
Copy link
Member

hugovk commented Sep 15, 2024

Thanks, sorry I was too quick with the close button :)

@Eclips4
Copy link
Member

Eclips4 commented Sep 15, 2024

So, the only remaining occurrence of OPTIMIZATION_LEVEL is related to the assert statement.
@iritkatriel, are you currently working on this? If not, can I attempt to fix it?

@iritkatriel
Copy link
Member Author

I have a patch for it. Thanks.

@iritkatriel
Copy link
Member Author

I got as far as I could with this, the assert optimization needs to stay in ast_opt (see discussion on PR).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
interpreter-core (Objects, Python, Grammar, and Parser dirs)
Projects
None yet
Development

No branches or pull requests

3 participants