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: output a DW_LNE_end_sequence instruction at the end of every function's line table #34380

Open
jeremyfaller opened this issue Sep 18, 2019 · 1 comment
Labels
compiler/runtime Issues related to the Go compiler and/or runtime. NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone

Comments

@jeremyfaller
Copy link
Contributor

As we move DWARF generation out of the linker and into the compiler, we've taken some short cuts when emitting the line table. Specifically, rather than outputting a DW_LNE_end_sequence at the end of every function's debug_lines table, we reset the state machine. See discussion HERE.

We are blocked on Delve supporting multiple DW_LNE_end_sequences per compilation unit. See Delve's issue HERE.

In addition to making the state machine mechanics simpler, we can remove the assert in the linker that PCs are monotonically increasing per functions in a compilation unit. Again, see the discussion.

@jeremyfaller jeremyfaller self-assigned this Sep 18, 2019
@jeremyfaller
Copy link
Contributor Author

CC: @aarzilli

@jeremyfaller jeremyfaller changed the title cmd/compile: output a DW_LNE_end_sequence instruction at the end of every function's line table unti cmd/compile: output a DW_LNE_end_sequence instruction at the end of every function's line table unit Sep 18, 2019
@jeremyfaller jeremyfaller changed the title cmd/compile: output a DW_LNE_end_sequence instruction at the end of every function's line table unit cmd/compile: output a DW_LNE_end_sequence instruction at the end of every function's line table Sep 18, 2019
@jeremyfaller jeremyfaller removed their assignment Mar 23, 2022
@mknyszek mknyszek added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label Mar 23, 2022
@prattmic prattmic added this to the Backlog milestone May 20, 2022
@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. NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Projects
Development

No branches or pull requests

4 participants