Skip to content

[clang] MangledSymbol: remove pointless copy of vector #90012

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

Merged
merged 5 commits into from
May 7, 2024

Conversation

sookach
Copy link
Contributor

@sookach sookach commented Apr 25, 2024

This pr addresses #87255 adds a std::move call to the names in MangledSymbol's constructor.

Copy link

Thank you for submitting a Pull Request (PR) to the LLVM Project!

This PR will be automatically labeled and the relevant teams will be
notified.

If you wish to, you can add reviewers by using the "Reviewers" section on this page.

If this is not working for you, it is probably because you do not have write
permissions for the repository. In which case you can instead tag reviewers by
name in a comment by using @ followed by their GitHub username.

If you have received no comments on your PR for a week, you can request a review
by "ping"ing the PR by adding a comment “Ping”. The common courtesy "ping" rate
is once a week. Please remember that you are asking for valuable time from other developers.

If you have further questions, they may be answered by the LLVM GitHub User Guide.

You can also ask questions in a comment on this PR, on the LLVM Discord or on the forums.

@llvmbot llvmbot added the clang Clang issues not falling into any other category label Apr 25, 2024
@llvmbot
Copy link
Member

llvmbot commented Apr 25, 2024

@llvm/pr-subscribers-clang

Author: Andrew Sukach (soukatch)

Changes

This pr addresses #87255 adds a std::move call to the names in MangledSymbol's constructor.


Full diff: https://github.com/llvm/llvm-project/pull/90012.diff

1 Files Affected:

  • (modified) clang/lib/Frontend/InterfaceStubFunctionsConsumer.cpp (+2-1)
diff --git a/clang/lib/Frontend/InterfaceStubFunctionsConsumer.cpp b/clang/lib/Frontend/InterfaceStubFunctionsConsumer.cpp
index d58f5bb0919906..81a827dba26b90 100644
--- a/clang/lib/Frontend/InterfaceStubFunctionsConsumer.cpp
+++ b/clang/lib/Frontend/InterfaceStubFunctionsConsumer.cpp
@@ -33,7 +33,8 @@ class InterfaceStubFunctionsConsumer : public ASTConsumer {
 
     MangledSymbol(const std::string &ParentName, uint8_t Type, uint8_t Binding,
                   std::vector<std::string> Names)
-        : ParentName(ParentName), Type(Type), Binding(Binding), Names(Names) {}
+        : ParentName(ParentName), Type(Type), Binding(Binding),
+          Names(std::move(Names)) {}
   };
   using MangledSymbols = std::map<const NamedDecl *, MangledSymbol>;
 

@sookach
Copy link
Contributor Author

sookach commented Apr 25, 2024

@dcb314 @shafik @EugeneZelenko Please let me know if this change looks good. Thanks!

Copy link
Collaborator

@shafik shafik left a comment

Choose a reason for hiding this comment

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

LGTM

@sookach
Copy link
Contributor Author

sookach commented Apr 26, 2024

Looking at the logs, and the error seems to be unrelated to the changes made
https://buildkite.com/llvm-project/clang-ci/builds/16430#018f132d-506e-440c-b18b-fed98237def9/54-5446

@shafik
Copy link
Collaborator

shafik commented Apr 26, 2024

Looking at the logs, and the error seems to be unrelated to the changes made https://buildkite.com/llvm-project/clang-ci/builds/16430#018f132d-506e-440c-b18b-fed98237def9/54-5446

You can try using --allow-empty to do an empty commit to kick off the build again.

@sookach sookach force-pushed the pr/mangledsymbol-move branch from c2195e4 to 9007597 Compare April 26, 2024 05:28
@Endilll
Copy link
Contributor

Endilll commented Apr 26, 2024

@shafik I wonder how checking size of a vector is now considered an expensive check.
(I stumbled upon it while reviewing)

#ifdef EXPENSIVE_CHECKS
assert(MangledNames.size() <= 1 && "Expected only one name mangling.");
#endif

Copy link
Contributor

@Endilll Endilll left a comment

Choose a reason for hiding this comment

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

Thank you for spotting and fixing this!

@sookach
Copy link
Contributor Author

sookach commented May 3, 2024

@AaronBallman would it be possible to get an approval while all the checks are green? Thanks!

Copy link
Collaborator

@AaronBallman AaronBallman left a comment

Choose a reason for hiding this comment

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

LGTM!

@AaronBallman AaronBallman merged commit e84fae8 into llvm:main May 7, 2024
Copy link

github-actions bot commented May 7, 2024

@soukatch Congratulations on having your first Pull Request (PR) merged into the LLVM Project!

Your changes will be combined with recent changes from other authors, then tested
by our build bots. If there is a problem with a build, you may receive a report in an email or a comment on this PR.

Please check whether problems have been caused by your change specifically, as
the builds can include changes from many authors. It is not uncommon for your
change to be included in a build that fails due to someone else's changes, or
infrastructure issues.

How to do this, and the rest of the post-merge process, is covered in detail here.

If your change does cause a problem, it may be reverted, or you can revert it yourself.
This is a normal part of LLVM development. You can fix your changes and open a new PR to merge them again.

If you don't get any reports, no action is required from you. Your changes are working as expected, well done!

@sookach
Copy link
Contributor Author

sookach commented May 7, 2024

Thank you everyone for the reviews!

@AaronBallman
Copy link
Collaborator

Thank you everyone for the reviews!

Thank you for the improvement!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
clang Clang issues not falling into any other category
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants