All of the same stuff is still in it, e.g:
4. 4. The Constant Pool
"5.4.3. Resolution
5.4.3.2. Field Resolution
6. The Java Virtual Machine Instruction Set

"putstatic" bytecode from section 6.5
"invokevirtual" bytecode from section 6.5

I did not check for any differences in the language of those sections. But since they have to be 100% backward compatible, there won't be any major surprises.

[ Reply to This | Parent | # ]

In Andrew McFadden's testimony, he described how Dalvik bytecodes don't contain symbolic references either (probably for similar reasons -- simplicity and interpreter efficiency). They keep the symbols elsewhere in the .dex file, and they can share the same symbol between multiple Dalvik bytecode instructions (just like a constant pool entry in a Java .class file can be shared by multiple Java bytecode instructions).

During cross, Oracle tried to elicit some sort of statement from him that they could twist to mean the Dalvik bytecode contained a symbolic reference:

excerpt from Cross Examination of Mr. McFadden, by Oracle:

Oracle: So the role of the iget instruction is to obtain actual field data from an object and store it in a Dalvik register, true, sir?

Mr. McFadden: Yes.

Oracle: iget with 01 as the field index, it doesn't store the number 01 in a Dalvik register, right?

Mr. McFadden: Right.

Oracle: It doesn't obtain 2 or 76 and store those in a Dalvik register, does it?

It doesn't obtain the name "byte", does it?

[five or six more questions along these lines, getting more and more excited]

Mr. McFadden: Yes.

Oracle: The actual data is what it stores, right?

Mr. McFadden: Yes.

Oracle: True or false: the Dalvik iget instruction never contains the actual memory location of the actual field it's supposed to get, true?

Mr. McFadden: True.

Oracle: True or false: the va operand is not the memory location of the actual field?

Mr. McFadden: True.

Oracle: The vb and field@CCCC are not the memory location of the actual field?

Mr. McFadden: True.

[By this point the Oracle lawyer looks like he's just triumphantly unveiled the murder weapon. I have no idea what his questions were supposed to mean, though, and the witness sounded like he didn't either. I didn't see the jury's response.]

The second half of the questions Google asked him on redirect, establish that the Dalvik instructions only contain a numeric index, and that this is NOT the same as containing a symbolic reference.

excerpt from Redirect Examination of Mr. McFadden, by Google:

Google: Why did you use the term "data" here?

Mr. McFadden: To contrast with the instruction stream.

Google: Is the instruction stream separate from the data?

Oracle: Leading.

Judge: Try not to lead.

Google: To what extent are the instructions and tables separate in the dex file?

Mr. McFadden: A lot of things are interleaved, but the instructions for a given method are distinct. They occur in a solid block inside the dex file, so you can find a chunk which is the instructions for a given method.

Google: Page 17, "insns", is that the chunk you were referring to?

Mr. McFadden: Yes.

Google: Slide 21. Mr. Jacobs asked if "1" in the instruction stream corresponds to "fun", remember that?

Mr. McFadden: I think so.

Google: What does "1" tell you?

Mr. McFadden: Index into the field IDs table.

Google: Does it tell you a location?

Mr. McFadden: Yes.

Google: What happens when you get to location 1 in the field table?

Mr. McFadden: You read the data there, and chase that to the next location.

Google: What happens when you reach the string data table?

Mr. McFadden: At that point, you're no longer working with numeric values; you've got string data, and you have to use those to find a matching field.

[More leading questions, shut down by the judge again]

Google: What's the difference between a reference where you use a symbol like this, and reference using numeric values?

Mr. McFadden: Numeric references take you directly to the next place you need to be. Symbolic references like "fun" don't give you an address, you have to take them and compare them against something else. You need to find the field that matches them. You can't just go straight there, you have to search for it.

A lot of David August's testimony was also about demonstrating that the Dalvik instructions don't contain a symbolic reference:

excerpt from David August Testimony, Google's Witness:

Google: Did you see Mitchell's report that Android's resolve.c infringes [claim numbers] of the '104 patent?

Mr. August: Yes. I believe it doesn't infringe [claims].

Resolve.c operates on instructions that contain references. The '104 patent requires that those references be symbolic references, but resolve.c doesn't do that.

I believe dexopt does not infringe claims 27 or 49 [?] of the '104 patent. They require that the instructions contain symbolic references, but dexopt doesn't operate on instructions that contain symbolic references. Also, dexopt is a static process, and the claims require that this occurs dynamically instead of statically.

excerpt from David August Testimony, Google's Witness:

Google: Okay, let's talk about the '104 patent.

Mr. August: It describes a way of executing instructions that contain symbolic references.

Figure 8 shows how to handle a symbolic reference inside a "load" instruction, and how to improve its performance. The steps involve resolving the reference "y", finding its location (in this case, slot 2), and remembering its location by overwriting the instruction "load 'y'" with "load 2".

The claims require that the symbolic references be inside the instruction.

Claim 11: "instructions containing one or more symbolic references".

Google: To what extent is that requirement also reflected in figure 8?

Mr. August: We see it throughout the patent. It's in the figures, it's in the claims, etc.

Google: Are you familiar with the Android code accused of infringing?

Mr. August: Yes, I'm very familiar.

Google: How much time have you spent viewing the code?

Mr. August: In relation to this case, more than 50 hours.

Google: Are you familiar with the format of dex files? What is it?

Mr. August: It's a Dalvik VM program file, containing both instructions and data which instruct the program how to perform an operation.

They contain symbolic references, but they're not inside instructions. You'll find plenty of symbolic references outside of instructions, but not inside instructions.

Mr. McFadden did a great job of explaining how resolve.c works at a high level.

...

I looked at the court's claim construction order: "a symbolic reference is a reference that identifies data by a name other than the numeric memory location of the data, and that is resolved dynamically rather than statically".

The Dalvik VM does not operate on instructions that contain symbolic references.

[Points out the instruction stream in McFadden's demonstrative slides, which doesn't contain any symbols]

Google: Where are the symbolic references in this figure?

Mr. August: You see some here in the string data table. "fun" was the example that was covered most heavily.

Google: To what extent does the 1 in the instruction stream represent the symbol "fun"?

Mr. August: It doesn't represent it; it gives its location. The 1 indicates that in the field ID table we'll find other data, in location 1. In this case, the other data is two pieces: there's a 02, which is a numeric reference (the location of more data), and the 76, which is another numeric reference. Those are known as indexes. It's another way of saying its location in the table.

The 02 is referring to another index, in the string ID table, which gives you 08, yet another index. This one's in the string data table, which gives the actual symbol.

Google: What's the difference between an index and an offset?

Mr. August: They're often used interchangeably. They're both numeric memory locations. In Dalvik, you might use "offset" to mean an offset from the beginning of the dex file, and "index" to refer to a location in the constant pool.

Google: Do they both refer to locations in memory?

Mr. August: They're both numeric memory locations.

excerpt from David August Testimony, Google's Witness:

Judge: So it sounds to me like the key point that you make (and believe me, I'm not saying that you're right or wrong, just trying to understand), that in that bottom box, those instructions never contain an "x" or a "y", they always contain a number?

David August: They always contain a number that refers to a memory location. You'll never find a sequence of characters like "x" or "y" there. I think there's no disagreement there.

Judge: So what is the disagreement? Google: So, what is the disagreement? [laughter]

David August: I think they must be imagining some sort of transitive property, where you follow a numeric reference to a numeric reference to a symbolic reference and it somehow makes the whole thing symbolic. Or maybe they're saying that the "instruction" contains all this data, not just the opcode and the operands.

Google: Three issues: first, Dr. Mitchell says that an index is a symbolic reference, correct?

David August: Sometimes.

Google: Is there a disagreement as to whether the instruction stream contains indexes?

David August: No, there's no disagreement. They contain indexes.

Google: Why would you move "y" out of the instruction stream and put it into the string table?

David August: It's about efficiency of executing the instructions. If you have an instruction like "52" (get), you'd like it to be a fixed size. CCCC is four digits -- well, it's hex digits, but close enough -- it's a fixed length. Now if you have a symbolic reference like "y" or, sorry, "fun", it's much more complicated. Now you have to figure out how long it is. You have to figure out when to stop, so you don't run into the other instructions. All of that is much less efficient than just knowing that an instruction that gets data is just two numbers: 52, 01, regardless of the length of the identifier.

[ Reply to This | Parent | # ]

[ Reply to This | Parent | # ]