Skip to content

Conversation

@rastogishubham
Copy link

The CAS schema for the debug info sections is getting complicated, to make sure we are aware of how the different sections are laid out, we want to document the information in the header file so it can be updated whenever a change it made

Copy link

@felipepiovezan felipepiovezan left a comment

Choose a reason for hiding this comment

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

Nice!!

@rastogishubham
Copy link
Author

This patch doesn't have a ref from the debug info cu to the debug string cas blocks because that patch isn't merged yet, the idea would be to update this diagram when we change something

Choose a reason for hiding this comment

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

Is this true? Isn't that data stored in the distinctdataref?

Copy link
Author

Choose a reason for hiding this comment

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

No, we had an experimental patch where we moved the dw_form_addrs into the distinctdataref, but since I could not address some of the comments that were left in that patch, it has not been merged yet.

#5343

# This is the 1st commit message:

Add some documentation that describes the CAS schema

# This is the commit message swiftlang#2:

Addressed review comments

# This is the commit message swiftlang#3:

Addressed some more feedback
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.

3 participants