Skip to content

Conversation

@Midar
Copy link
Contributor

@Midar Midar commented Feb 8, 2025

Allow direct dispatch for the ObjFW runtime

@github-actions
Copy link

github-actions bot commented Feb 8, 2025

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 clang Clang issues not falling into any other category clang:frontend Language frontend issues, e.g. anything involving "Sema" labels Feb 8, 2025
@llvmbot
Copy link
Member

llvmbot commented Feb 8, 2025

@llvm/pr-subscribers-clang-codegen

@llvm/pr-subscribers-clang

Author: Jonathan Schleifer (Midar)

Changes

There was no reason for it to ever be disabled.


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

1 Files Affected:

  • (modified) clang/include/clang/Basic/ObjCRuntime.h (+1-1)
diff --git a/clang/include/clang/Basic/ObjCRuntime.h b/clang/include/clang/Basic/ObjCRuntime.h
index 1ccf60f0b7bee7..df42b438986111 100644
--- a/clang/include/clang/Basic/ObjCRuntime.h
+++ b/clang/include/clang/Basic/ObjCRuntime.h
@@ -473,7 +473,7 @@ class ObjCRuntime {
     case GCC: return false;
     case GNUstep:
       return (getVersion() >= VersionTuple(2, 2));
-    case ObjFW: return false;
+    case ObjFW: return true;
     }
     llvm_unreachable("bad kind");
   }

@Midar
Copy link
Contributor Author

Midar commented Feb 8, 2025

Would @rjmccall be the appropriate reviewer?

@Midar
Copy link
Contributor Author

Midar commented Feb 8, 2025

Also, would it be possible to get this into 20.1?

@Midar
Copy link
Contributor Author

Midar commented Feb 8, 2025

Actually, I realized this needs more work, as GenerateDirectMethodPrologue needs to be implemented. Moving to draft.

@Midar Midar marked this pull request as draft February 8, 2025 18:19
@Midar Midar changed the title Allow direct dispatch for the ObjFW runtime Allow direct dispatch for the ObjFW runtime >= 1.3 Feb 8, 2025
@Midar
Copy link
Contributor Author

Midar commented Feb 8, 2025

Copied the necessary parts from CGObjCMac to just ObjFW, as GNUstep decided to do it very differently.

Theoretically, the same could be done for the GCC runtime. Should it?

@Midar Midar marked this pull request as ready for review February 8, 2025 18:54
@llvmbot llvmbot added the clang:codegen IR generation bugs: mangling, exceptions, etc. label Feb 8, 2025
@Midar Midar changed the title Allow direct dispatch for the ObjFW runtime >= 1.3 Allow direct dispatch for the ObjFW runtime Feb 9, 2025
@Sirraide Sirraide requested a review from rjmccall February 10, 2025 09:16
@Midar
Copy link
Contributor Author

Midar commented Feb 24, 2025

@rjmccall @davidchisnall @ahatanak Could any of you have a look, please? I'd think this is rather straightforward.

Copy link
Contributor

@rjmccall rjmccall left a comment

Choose a reason for hiding this comment

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

Mostly LGTM.

const ObjCInterfaceDecl *OID = cast<ObjCInterfaceDecl>(CD);
assert(
OID &&
"GenerateDirectMethod() should be called with the Class Interface");
Copy link
Contributor

Choose a reason for hiding this comment

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

cast is already an asserting cast, so this should just be a comment. But really, if this is reliably true (it's never passed an implementation or a category?), I wonder why it's not expressed in the type of this method.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This is straight up copied from CGObjCMac, so I have no idea why it was done this way :)

Copy link
Contributor

Choose a reason for hiding this comment

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

Heh, alright.

@Midar Midar requested a review from rjmccall March 2, 2025 23:19
Copy link
Contributor

@rjmccall rjmccall left a comment

Choose a reason for hiding this comment

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

LGTM

@Midar
Copy link
Contributor Author

Midar commented Mar 16, 2025

@rjmccall What's required to get this merged now that it has your LGTM?

@efriedma-quic efriedma-quic merged commit a187060 into llvm:main Mar 23, 2025
10 checks passed
@github-actions
Copy link

@Midar 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!

@Midar Midar deleted the objfw-direct branch March 23, 2025 17:46
@Midar
Copy link
Contributor Author

Midar commented Mar 23, 2025

Thanks for merging! Is there a way to get this into 20.1.2?

@efriedma-quic
Copy link
Collaborator

@Midar
Copy link
Contributor Author

Midar commented Mar 24, 2025

Thanks, that looks like it'll have to wait for 21.

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

Labels

clang:codegen IR generation bugs: mangling, exceptions, etc. clang:frontend Language frontend issues, e.g. anything involving "Sema" clang Clang issues not falling into any other category

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants