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

cmd/compile: possible inlining bug with variable renaming? #15111

Open
griesemer opened this issue Apr 4, 2016 · 0 comments
Open

cmd/compile: possible inlining bug with variable renaming? #15111

griesemer opened this issue Apr 4, 2016 · 0 comments
Labels
compiler/runtime Issues related to the Go compiler and/or runtime.
Milestone

Comments

@griesemer
Copy link
Contributor

griesemer commented Apr 4, 2016

A reminder for myself to investigate variable renaming for inlining. See #4326 for a test case where variable numbering is used to prevent name collisions when inlining.

Specifically, is it not possible that two different functions, when inlined, collide when variables and numbers are equal? Try to create test case.

@griesemer griesemer self-assigned this Apr 4, 2016
@griesemer griesemer added this to the Go1.7 milestone Apr 4, 2016
@griesemer griesemer modified the milestones: Unreleased, Go1.7 Apr 21, 2016
@griesemer griesemer modified the milestones: Proposal, Unreleased, Go1.9Maybe Mar 30, 2017
@griesemer griesemer modified the milestones: Go1.10, Go1.9Maybe Jun 16, 2017
@griesemer griesemer modified the milestones: Go1.10, Go1.11 Nov 3, 2017
@griesemer griesemer modified the milestones: Go1.11, Unplanned Jun 4, 2018
@gopherbot gopherbot added the compiler/runtime Issues related to the Go compiler and/or runtime. label Jul 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
compiler/runtime Issues related to the Go compiler and/or runtime.
Projects
None yet
Development

No branches or pull requests

2 participants