Skip to contentSkip to conversation

Predication vs. Branching

linux-ia64 Jonathan Case Nicklin 3 participants 5 messages Sep 19, 2000

lore
Share & tools
lore
#0 lore raw
Quoted 11 lines · Dan Pop
Quoted 5 lines · Jonathan Case Nicklin

This might not be the appropriate forum, but what the heck. Does anyone have
a definitive answer on what happens to predicated instructions that are not
executed (ie where in the pipeline are they discarded).

According to the manual, they become NOPs of the appropriate type.

Dan

Dan,
But When? Do they always consume execution resources or are they
dropped as soon as their predicate dependency is fulfilled... assuming their

dependent predicate evaluates false and that there are predicate dependent instructions in the pipeline.

-Jonathan Nicklin

#1 lore raw
Quoted 7 lines · Dan Pop
Quoted 5 lines · Jonathan Case Nicklin
Quoted 3 lines · Dan Pop
Quoted 1 line · Jonathan Case Nicklin

This might not be the appropriate forum, but what the heck. Does

anyone

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

have
a definitive answer on what happens to predicated instructions

that are

Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 2 lines

not
executed (ie where in the pipeline are they discarded).

According to the manual, they become NOPs of the appropriate type.

Quoted 6 lines
Quoted 6 lines
Quoted 1 line

Dan

Dan,
But When? Do they always consume execution resources or are they

dropped as soon as their predicate dependency is fulfilled...

assuming their

Quoted 2 lines
Quoted 2 lines

dependent predicate evaluates false and that there are predicate

dependent

Quoted 24 lines
Quoted 1 line

instructions in the pipeline.

According to the Itanium microarchitecture manual, they do consume execution resources, by their mere presence in the bundle.

I.e. the following code still keeps the CPU busy for one cycle:

{.mib

        nop.m   0
        nop.i   0
        nop.b   0
}
{.mib
        nop.m   0
        nop.i   0
        nop.b   0

}

No execution unit can be assigned to a more useful instruction during that cycle.

Replacing the NOPs by predicated away instructions of the corresponding types shouldn't change anything.

Quoted 6 lines

Dan

_______________________________________________
Linux-IA64 mailing list
[email protected]
http://lists.linuxia64.org/lists/listinfo/linux-ia64

Dan,

okey-dokey... The predicated instructions that are not executed do consume
execution resources because they evaluate to NOPs... and NOPs do carry all
the way through the pipeline until commit (this is what i was curious about).
Now the question is, at what point does it become more efficient to branch
rather than predicate? I assume this would dependent on the pipeline depth
and total Instruction Fetch Bandwidth.

Thanks,
Jonathan Nicklin

#2 lore raw
In reply to Jonathan Case Nicklin
Quoted 5 lines · Jonathan Case Nicklin

This might not be the appropriate forum, but what the heck. Does anyone have
a definitive answer on what happens to predicated instructions that are not
executed (ie where in the pipeline are they discarded).

According to the manual, they become NOPs of the appropriate type.

Dan

#3 lore raw
In reply to Jonathan Case Nicklin
Quoted 12 lines · Jonathan Case Nicklin
Quoted 10 lines · Dan Pop
Quoted 5 lines · Jonathan Case Nicklin

This might not be the appropriate forum, but what the heck. Does anyone have
a definitive answer on what happens to predicated instructions that are not
executed (ie where in the pipeline are they discarded).

According to the manual, they become NOPs of the appropriate type.

Quoted 8 lines
Quoted 1 line

Dan

Dan,
But When? Do they always consume execution resources or are they
dropped as soon as their predicate dependency is fulfilled... assuming their

dependent predicate evaluates false and that there are predicate dependent instructions in the pipeline.

According to the Itanium microarchitecture manual, they do consume execution resources, by their mere presence in the bundle.

I.e. the following code still keeps the CPU busy for one cycle:

{.mib

	nop.m	0
	nop.i	0
	nop.b	0
}
{.mib
	nop.m   0
	nop.i   0
	nop.b   0

}

No execution unit can be assigned to a more useful instruction during that cycle.

Replacing the NOPs by predicated away instructions of the corresponding types shouldn't change anything.

Dan

#4 lore raw
In reply to Jonathan Case Nicklin

Jonathan writes:
Now the question is, at what point does it become more efficient to
branch
rather than predicate? I assume this would dependent on the pipeline
depth
and total Instruction Fetch Bandwidth.

It has less to do with those factors than it does with statistical factors regarding the code graph you're trying to execute. Imagine, for example, an if-then-else clause. If the then and else branches can be packed into the same number of execution cycles, predication is a clear win. But if the branches are unbalanced, say one takes 10 cycles and the other can be done in 2, then the answer depends on execution frequency. Predicated, either branch is going to take 10 cycles. If the longer side gets executed 80% of the time then predication makes sense--the penalty paid 20% of the time should be less than the pipeline stalls imposed by the jumps. (A more accurate answer about the exact balance point would be dependent on the pipeline depth and other factors as you suggest.) If the short side gets the 80%, then branching should in general win over predication.
_______________________________________________________________________
Robert Reed [email protected]
Intel ISV Performance Lab/ Oregon Application Analysis Team
Dept. EY2-05, 5350 NE Elam Young Parkway phone 503-696-3814
Hillsboro, OR 97124-6461 fax 503-696-3730
_______________________________________________________________________
-----Original Message-----
From: Jonathan Case Nicklin [mailto:[email protected]]
Sent: Tuesday, September 19, 2000 6:14 AM
To: [email protected]
Subject: Re: [linux-ia64] Predication vs. Branching

Quoted 7 lines · Dan Pop
Quoted 5 lines · Jonathan Case Nicklin
Quoted 3 lines · Dan Pop
Quoted 1 line · Jonathan Case Nicklin

This might not be the appropriate forum, but what the heck. Does

anyone

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

have
a definitive answer on what happens to predicated instructions

that are

Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 2 lines

not
executed (ie where in the pipeline are they discarded).

According to the manual, they become NOPs of the appropriate type.

Quoted 6 lines
Quoted 6 lines
Quoted 1 line

Dan

Dan,
But When? Do they always consume execution resources or are they

dropped as soon as their predicate dependency is fulfilled...

assuming their

Quoted 2 lines
Quoted 2 lines

dependent predicate evaluates false and that there are predicate

dependent

Quoted 24 lines
Quoted 1 line

instructions in the pipeline.

According to the Itanium microarchitecture manual, they do consume execution resources, by their mere presence in the bundle.

I.e. the following code still keeps the CPU busy for one cycle:

{.mib

        nop.m   0
        nop.i   0
        nop.b   0
}
{.mib
        nop.m   0
        nop.i   0
        nop.b   0

}

No execution unit can be assigned to a more useful instruction during that cycle.

Replacing the NOPs by predicated away instructions of the corresponding types shouldn't change anything.

Quoted 6 lines

Dan

_______________________________________________
Linux-IA64 mailing list
[email protected]
http://lists.linuxia64.org/lists/listinfo/linux-ia64

Dan,

okey-dokey... The predicated instructions that are not executed do consume
execution resources because they evaluate to NOPs... and NOPs do carry all
the way through the pipeline until commit (this is what i was curious about).
Now the question is, at what point does it become more efficient to branch
rather than predicate? I assume this would dependent on the pipeline depth
and total Instruction Fetch Bandwidth.

Thanks,
Jonathan Nicklin

_______________________________________________
Linux-IA64 mailing list
[email protected]
http://lists.linuxia64.org/lists/listinfo/linux-ia64