Skip to content

Conversation

@rastogishubham
Copy link

With -fcas-emit-casid-file, a .casid file will be emitted next to the object file only when -fcas-backend-mode=native, or -fcas-backend-mode=verify is used and the output is directed to a file, rather than stdout.

@rastogishubham
Copy link
Author

@swift-ci please test llvm

@adrian-prantl
Copy link

Nice! It might make future cherry-picking easier if we separate the clang and llvm changes into separate commits.

Copy link

@cachemeifyoucan cachemeifyoucan left a comment

Choose a reason for hiding this comment

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

LGTM in general.

Other suggestion I will make is to make all the CASIDOS to be the last parameter with a default value (nullptr) when possible. That will keep the diff a lot smaller downstream. It can be re-ordered when upstreaming.

Also since this is a LLVM CodeGen option, I prefer the bulk of the testing should be done in llvm test. That is using llvm-mc or llc to test CASID file output. Instead of using clang to do all the testing.

With -fcas-emit-casid-file, a .casid file will be emitted next to the
object file only when -fcas-backend-mode=native, or
-fcas-backend-mode=verify is used and the output is directed to a file,
rather than stdout.
This change enables -fcas-emit-casid-file to the llvm backend and allows
emission of a .casid file when -fcas-backend and
-fcas-backend-mode=native or -fcas-backend-mode=verify is used
@rastogishubham
Copy link
Author

@swift-ci please test

@rastogishubham
Copy link
Author

@swift-ci please test llvm

1 similar comment
@rastogishubham
Copy link
Author

@swift-ci please test llvm

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