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

Map each FUNCTION_BLOCK #16

Open
5 tasks
woodruffw opened this issue Jan 17, 2022 · 1 comment
Open
5 tasks

Map each FUNCTION_BLOCK #16

woodruffw opened this issue Jan 17, 2022 · 1 comment
Labels
C:mapper Concerns the llvm-mapper crate. enhancement New feature or request help wanted Extra attention is needed

Comments

@woodruffw
Copy link
Owner

I'm going to try to constrain #14 to just the MODULE_CODE_FUNCTION records, not the FUNCTION_BLOCKs themselves.

Mapping FUNCTION_BLOCK requires support for three subblocks:

  • CONSTANTS_BLOCK
  • VALUE_SYMTAB_BLOCK
  • METADATA_ATTACHMENT
  • METADATA_BLOCK
  • USELIST_BLOCK
@woodruffw woodruffw added enhancement New feature or request help wanted Extra attention is needed C:mapper Concerns the llvm-mapper crate. labels Jan 17, 2022
@jw910731
Copy link
Contributor

jw910731 commented Sep 2, 2023

Is there any way to construct an example bitcode file that has a VALUE_SYMTAB_BLOCK in FUNCTION_BLOCK ?
I was unable to get a file that has this property and had difficulty to do further research and help.

My current way of creating bitcode file relies on clang and clang++

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C:mapper Concerns the llvm-mapper crate. enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants