Hi List,

On certain pvs* manual pages, I'm seeing text like this

"(!) Warning

It is unsafe to use the same f-variable for both input and output of
pvs opcodes. Using the same one might lead to undefined behavior on
some opcodes. Use a different one on the left and right sides of the
opcode. "

Why is this not safe? Will the use of pvsinit avoid this type of
"undefined behavior"? What exactly is this "undefined behavior" and
how does it affect the performance loop?


-David