the @name attribute seems to be redundant

[yegor256]

This is what I see in XMIR after jeo:disassemble:

[..]
<o base="jeo.seq.of3" name="@">
  <o base="jeo.opcode.aload" name="aload-1C"><!-- #25:aload(0) -->
    <o base="jeo.int"><!-- 25 -->
      <o base="org.eolang.bytes">00-00-00-00-00-00-00-19</o>
    </o>
[...]

Here, I believe, you may stop using @name attribute, since you have all necessary information in the @base -- you know the name of the opcode.

If you remove @name, you can remove three XSL from the unroll procedure: add-cuts.xsl, remove-cuts.xsl, and vars-float-down.xsl.

[yegor256]

@volodya-lombrozo check this out please

[volodya-lombrozo]

@yegor256 I will check it, thank you.

[volodya-lombrozo]

@yegor256 I have removed opcode names and then add-cuts.xsl, remove-cuts.xsl, and vars-float-down.xsl transformations from the unroll procedure. And after it the tests failed. Seems, just removing names doesn't help.
You can find more info here: #935

[yegor256]

@volodya-lombrozo I don't see the logs of failure in the PR :(

[volodya-lombrozo]

@yegor256 Here is the failed pipeline: https://github.com/objectionary/jeo-maven-plugin/actions/runs/12135454483/job/33834545174?pr=935

As you can see, the phi-unphi integration test failed:

Error:  The following builds failed:
Error:  *  phi-unphi/pom.xml

Here are logs from the phi-unphi integration test:
build.log

By using the following link you may download the failed pipeline folders (and find exact files that were created during all phases): https://github.com/objectionary/jeo-maven-plugin/actions/runs/12135454483/artifacts/2265953649

Long story short, I'm getting something like:

Caused by: java.lang.IllegalArgumentException: Annotation [o: null] has no child at index 0
    at org.eolang.jeo.representation.xmir.XmlAnnotation.child (XmlAnnotation.java:99)
    at org.eolang.jeo.representation.xmir.XmlAnnotation.descriptor (XmlAnnotation.java:78)
    at org.eolang.jeo.representation.xmir.XmlAnnotation.bytecode (XmlAnnotation.java:58)
    at java.util.stream.ReferencePipeline$3$1.accept (ReferencePipeline.java:195)
    at java.util.ArrayList$ArrayListSpliterator.forEachRemaining (ArrayList.java:1655)
    at java.util.stream.AbstractPipeline.copyInto (AbstractPipeline.java:484)
    at java.util.stream.AbstractPipeline.wrapAndCopyInto (AbstractPipeline.java:474)
    at java.util.stream.ReduceOps$ReduceOp.evaluateSequential (ReduceOps.java:913)
    at java.util.stream.AbstractPipeline.evaluate (AbstractPipeline.java:234)
    at java.util.stream.ReferencePipeline.collect (ReferencePipeline.java:578)
    at org.eolang.jeo.representation.bytecode.BytecodeAnnotations.<init> (BytecodeAnnotations.java:61)
    at org.eolang.jeo.representation.xmir.XmlAnnotations.bytecode (XmlAnnotations.java:54)
    at java.util.Optional.map (Optional.java:265)

It means, that phi/unphi makes the final xmir unreadable by jeo.

[0pdd]

@yegor256 the puzzle #936 is still not solved.

[yegor256]

@volodya-lombrozo thanks!

[0pdd]

@yegor256 the only puzzle #936 is solved here.