# US 2026/0064425 A1 · Chained retirement

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2026/0064425 A1
- Document ID: US20260064425A1
- Status: Published application
- Kind: A1
- Application number: 18/821,332
- Filed: 2024-08-30
- Published: 2026-03-05
- Earliest claimed: 2024-08-30
- Assignees: QUALCOMM Incorporated
- Applicants: QUALCOMM Incorporated
- Inventors: Damian MAIORANO; Priyank Satish DESHPANDE
- Web page: https://patentgrep.com/patent/US20260064425A1

## CPC

- G06F 9/3838: {Dependency mechanisms, e.g. register scoreboarding}
- G06F 9/3836: {Instruction issuing, e.g. dynamic instruction scheduling or out of order instruction execution}
- G06F 9/384: {Register renaming}
- G06F 9/3842: {Speculative instruction execution}
- G06F 9/3854: {Instruction completion, e.g. retiring, committing or graduating}
- G06F 9/3856: {Reordering of instructions, e.g. using queues or age tags}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Certain aspects of the present disclosure provide techniques for freeing physical register tags, generally including fetching a set of instructions for out-of-order execution, wherein the set of instructions includes at least one target instruction that depends on at least first and second parent instructions as sources of data, mapping a destination architectural register of the target instruction to a physical tag selected from a list of free tags, creating an entry in a lookup table to track dependency between the target instruction and the first and second parent instructions, updating the entry based on execution of the first and second parent instructions, and freeing the physical tag prior to retirement of a releasing instruction that writes to the destination architectural register, if at least one condition is met after updating the entry.

## Claims

### Claim 1

An apparatus, comprising:
circuitry configured to fetch a set of instructions for out-of-order execution, wherein the set of instructions includes at least one target instruction that depends on at least first and second parent instructions as sources of data;
circuitry configured to map a destination architectural register of the target instruction to a physical tag selected from a list of free tags;
circuitry configured to create an entry in a lookup table to track dependencies between the target instruction and the first and second parent instructions, wherein the entry includes:
a first source field populated with at least an ID of a first source architectural register of the target instruction; and
a second source field populated with at least an ID of a second source architectural register of the target instruction;
circuitry configured to update the entry based on execution of the first and second parent instructions; and
circuitry configured to free the physical tag prior to retirement of a releasing instruction that writes to the destination architectural register, if at least one condition is met after updating the entry.

### Claim 2 (depends on 1)

The apparatus of claim 1, wherein the entry further includes a field indicating, upon creation, that the entry is a most recently used (MRU) entry.

### Claim 3 (depends on 1)

The apparatus of claim 1, wherein the entry further includes:
a target ID field populated based on an ID of the target instruction;
a destination field populated based on an ID of the destination architectural register of the target instruction; and
a physical tag field populated based on an ID of the physical tag.

### Claim 4

(canceled)

### Claim 5 (depends on 1)

The apparatus of claim 1, wherein the circuitry configured to update the entry is configured to:
update a first parent ID field of the entry with an ID of the first parent instruction, based on a match between a destination field of the first parent instruction and the first source field or a match between the destination field of the first parent instruction and the second source field. wherein the destination field of the first parent instruction is populated with an ID of the destination architectural register of the target instruction; and
update a second parent ID field of the entry with an ID of the second parent instruction, based on a match between a destination field of the second parent instruction and the first source field or a match between the destination field of the second parent instruction and the second source field.

### Claim 6 (depends on 5)

The apparatus of claim 5, wherein the circuitry configured to update the entry is further configured to:
update a bit in the first parent ID field to indicate whether the match of the destination field of the first parent instruction was with the first source field or the second source field; and
update a bit in the second parent ID field to indicate whether the match of the destination field of the second parent instruction was with the first source field or the second source field.

### Claim 7 (depends on 5)

The apparatus of claim 5, wherein the circuitry configured to update the entry is further configured to update a confidence field of the entry based on at least one of:
the match between the destination field of the first parent instruction and the first source field or the second source field; or
the match between the destination field of the second parent instruction and the first source field or the second source field.

### Claim 8 (depends on 7)

The apparatus of claim 7, wherein the at least one condition is considered met if the confidence field exceeds a threshold value.

### Claim 9 (depends on 1)

The apparatus of claim 1, further comprising:
circuitry configured to cache data stored in a location associated with the physical tag prior to or when releasing the physical tag.

### Claim 10 (depends on 9)

The apparatus of claim 9, wherein the data stored in a location associated with the physical tag is cached in a data field of the entry.

### Claim 11

A method of out-of-order processing, comprising:
fetching a set of instructions for out-of-order execution, wherein the set of instructions includes at least one target instruction that depends on at least first and second parent instructions as sources of data;
mapping a destination architectural register of the target instruction to a physical tag selected from a list of free tags;
creating an entry in a lookup table to track dependencies between the target instruction and the first and second parent instructions, wherein the entry includes:
a first source field populated with at least an ID of a first source architectural register of the target instruction; and
a second source field populated with at least an ID of a second source architectural register of the target instruction;
updating the entry based on execution of the first and second parent instructions; and
freeing the physical tag prior to retirement of a releasing instruction that writes to the destination architectural register, if at least one condition is met after updating the entry.

### Claim 12 (depends on 11)

The method of claim 11, wherein the entry further includes a field indicating, upon creation, that the entry is a most recently used (MRU) entry.

### Claim 13 (depends on 11)

The method of claim 11, wherein the entry further includes:
a target ID field populated based on an ID of the target instruction;
a destination field populated based on an ID of the destination architectural register of the target instruction; and
a physical tag field populated based on an ID of the physical tag.

### Claim 14

(canceled)

### Claim 15 (depends on 11)

The method of claim 11, wherein updating the entry comprises:
updating a first parent ID field of the entry with an ID of the first parent instruction, based on a match between a destination field of the first parent instruction and the first source field or a match between the destination field of the first parent instruction and the second source field. wherein the destination field is populated with an ID of the destination architectural register of the target instruction; and
updating a second parent ID field of the entry with an ID of the second parent instruction, based on a match between a destination field of the second parent instruction and the first source field or a match between the destination field of the second parent instruction and the second source field.

### Claim 16 (depends on 15)

The method of claim 15, wherein updating the entry further comprises:
updating a bit in the first parent ID field to indicate whether the match of the destination field of the first parent instruction was with the first source field or the second source field; and
updating a bit in the second parent ID field to indicate whether the match of the destination field of the second parent instruction was with the first source field or the second source field.

### Claim 17 (depends on 15)

The method of claim 15, wherein the updating further comprises updating a confidence field of the entry based on at least one of:
the match between of the destination field of the first parent instruction and the first source field or the second source field; or
the match between of the destination field of the first parent instruction and the first source field or the second source field.

### Claim 18 (depends on 17)

The method of claim 17, wherein the at least one condition is considered met if the confidence field exceeds a threshold value.

### Claim 19 (depends on 11)

The method of claim 11, further comprising:
caching data stored in a location associated with the physical tag prior to or when releasing the physical tag.

### Claim 20

An apparatus, comprising:
means for fetching a set of instructions for out-of-order execution, wherein the set of instructions includes at least one target instruction that depends on at least first and second parent instructions as sources of data;
means for mapping a destination architectural register of the target instruction to a physical tag selected from a list of free tags;
means for creating an entry in a lookup table to track dependencies between the target instruction and the first and second parent instructions, wherein the entry includes:
a first source field populated with at least an ID of a first source architectural register of the target instruction; and
a second source field populated with at least an ID of a second source architectural register of the target instruction;
means for updating the entry based on execution of the first and second parent instructions; and
means for freeing the physical tag prior to retirement of a releasing instruction that writes to the destination architectural register, if at least one condition is met after updating the entry.
