Skip to content

[DebugInfo][ObjectYAML] Remove duplicate "Flags" field from LabelSym #88194

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 1 commit into from
Apr 11, 2024

Conversation

nikitalita
Copy link
Contributor

@nikitalita nikitalita commented Apr 9, 2024

There was a duplicate flags field mistakenly left in LabelSym. LabelSym only has one flags field

@llvmbot
Copy link
Member

llvmbot commented Apr 9, 2024

@llvm/pr-subscribers-objectyaml

Author: None (nikitalita)

Changes

There was a duplicate flags field mistakenly left in LabelSym. [LabelSym only has one flags field](https://github.com/microsoft/microsoft-pdb/blob/805655a28bd8198004be2ac27e6e0290121a5e89/include/cvinfo.h#L3806


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

1 Files Affected:

  • (modified) llvm/lib/ObjectYAML/CodeViewYAMLSymbols.cpp (-1)
diff --git a/llvm/lib/ObjectYAML/CodeViewYAMLSymbols.cpp b/llvm/lib/ObjectYAML/CodeViewYAMLSymbols.cpp
index 64e1a58aa71a8a..e1d2700623ec3c 100644
--- a/llvm/lib/ObjectYAML/CodeViewYAMLSymbols.cpp
+++ b/llvm/lib/ObjectYAML/CodeViewYAMLSymbols.cpp
@@ -467,7 +467,6 @@ template <> void SymbolRecordImpl<LabelSym>::map(IO &IO) {
   IO.mapOptional("Offset", Symbol.CodeOffset, 0U);
   IO.mapOptional("Segment", Symbol.Segment, uint16_t(0));
   IO.mapRequired("Flags", Symbol.Flags);
-  IO.mapRequired("Flags", Symbol.Flags);
   IO.mapRequired("DisplayName", Symbol.Name);
 }
 

Copy link

github-actions bot commented Apr 9, 2024

⚠️ We detected that you are using a GitHub private e-mail address to contribute to the repo.
Please turn off Keep my email addresses private setting in your account.
See LLVM Discourse for more information.

Copy link
Collaborator

@jh7370 jh7370 left a comment

Choose a reason for hiding this comment

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

LGTM, but please see the warning from the bot about your email address.

@nikitalita
Copy link
Contributor Author

I'd rather not use my real e-mail, as I don't want to get a bunch of spam

@jh7370
Copy link
Collaborator

jh7370 commented Apr 11, 2024

I'd rather not use my real e-mail, as I don't want to get a bunch of spam

It is my understanding that LLVM has a policy of no GitHub noreply emails; there are many reasons why. Please see the Discourse thread on this topic.

@nikitalita
Copy link
Contributor Author

@jh7370
Copy link
Collaborator

jh7370 commented Apr 11, 2024

Wasn't a problem last time.

Thanks for pointing that out. I think my comment still stands, as the broad consensus (admittedly not unanimous) was that people should have public emails in the repository. It's quite possible @JDevlieghere wasn't aware of the thread. Please read the thread if you haven't already. I'll also post there to raise this again to try and understand where the consensus actually is and raise these two PRs as an example.

On the note of spam, at least two separate users reported getting very few spam emails that could be traced to their github emails (in one case, less than 30 a month, all filtered by gmail correctly). I personally can't comment because a) I rarely directly commit anymore, and b) I have a company email address, so I expect the company's spam filters filter things out without me ever seeing them.

@nikitalita
Copy link
Contributor Author

Ok, I have made my email address public

@jh7370
Copy link
Collaborator

jh7370 commented Apr 11, 2024

Ok, I have made my email address public

Thank you! Do you have commit access yet?

@nikitalita
Copy link
Contributor Author

I do not, so you will have to push the button for me.

@jh7370 jh7370 merged commit cca30df into llvm:main Apr 11, 2024
@jh7370
Copy link
Collaborator

jh7370 commented Apr 11, 2024

Done. Please keep an eye out for emails from the build bots indicating failures that might be related to your change.

Also, my apologies if you get a sudden influx of spam!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants