Fix concrete invoke dependency resolution when method context is null#4750
Merged
liannacasper merged 2 commits intomasterfrom Apr 14, 2026
Merged
Conversation
Contributor
✅ Continuous Quality ReportTest & Coverage
Static Analysis
Generated automatically by the PR CI workflow. |
Contributor
✅ ByteCodeTranslator Quality ReportTest & Coverage
Benchmark Results
Static Analysis
Generated automatically by the PR CI workflow. |
Collaborator
|
Compared 37 screenshots: 37 matched. Benchmark Results
Detailed Performance Metrics
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
resolveConcreteInvokeOwner()previously bail/returnednullwhengetMethod()was unavailable which caused concrete-class header/includes to be skipped and later produced calls to targets without declarations.Description
getMethod()to be non-null inInvoke.resolveConcreteInvokeOwner()andCustomInvoke.resolveConcreteInvokeOwner()so concrete-owner resolution can run during dependency analysis even when no method context exists.currentClasslookup null-safe and keep the self/inner-class guard only whencurrentClassis present.vm/ByteCodeTranslator/src/com/codename1/tools/translator/bytecodes/Invoke.javaand.../CustomInvoke.javawith small, equivalent edits in both files.Testing
mvn -f vm/ByteCodeTranslator/pom.xml -DskipTests compilewhich succeeded.export JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64 && export PATH="$JAVA_HOME/bin:$PATH" && mvn -f vm/ByteCodeTranslator/pom.xml -DskipTests compilebut that failed because the documented Java 8 path is not available in this environment.Codex Task