Skip to content

MachineInstrBuilder: Introduce copyMIMetadata() function. #133535

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

Open
wants to merge 3 commits into
base: users/pcc/spr/main.machineinstrbuilder-introduce-copymimetadata-function
Choose a base branch
from

Conversation

pcc
Copy link
Contributor

@pcc pcc commented Mar 28, 2025

This reduces the amount of boilerplate required when adding a new
field to MIMetadata and reduces the chance of bugs like the
one I fixed in TargetInstrInfo::reassociateOps.

Created using spr 1.3.6-beta.1
Copy link

github-actions bot commented Mar 28, 2025

✅ With the latest revision this PR passed the C/C++ code formatter.

pcc added a commit to pcc/llvm-project that referenced this pull request Apr 3, 2025
This reduces the amount of boilerplate required when adding a new
field to MIMetadata and reduces the chance of bugs like the
one I fixed in TargetInstrInfo::reassociateOps.

Pull Request: llvm#133535
pcc added a commit to pcc/llvm-project that referenced this pull request Apr 4, 2025
This reduces the amount of boilerplate required when adding a new
field to MIMetadata and reduces the chance of bugs like the
one I fixed in TargetInstrInfo::reassociateOps.

Pull Request: llvm#133535
pcc added 2 commits May 12, 2025 21:38
Created using spr 1.3.6-beta.1
Created using spr 1.3.6-beta.1
pcc added a commit to pcc/llvm-project that referenced this pull request May 24, 2025
This reduces the amount of boilerplate required when adding a new
field to MIMetadata and reduces the chance of bugs like the
one I fixed in TargetInstrInfo::reassociateOps.

Pull Request: llvm#133535
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

Successfully merging this pull request may close these issues.

1 participant