Searched refs:F_dot_P (Results 1 – 4 of 4) sorted by relevance
234 FT_Long F_dot_P; /* dot product of freedom and projection */ member
1716 exc->F_dot_P ) ); in Direct_Move()1728 exc->F_dot_P ) ); in Direct_Move()1736 exc->F_dot_P ) ); in Direct_Move()1754 exc->F_dot_P ) ); in Direct_Move()1796 exc->F_dot_P ) ); in Direct_Move_Orig()1804 exc->F_dot_P ) ); in Direct_Move_Orig()2541 exc->F_dot_P = exc->GS.projVector.x; in Compute_Funcs()2543 exc->F_dot_P = exc->GS.projVector.y; in Compute_Funcs()2545 exc->F_dot_P = in Compute_Funcs()2566 if ( exc->F_dot_P == 0x4000L ) in Compute_Funcs()[all …]
862 exec->F_dot_P = 0x4000L; in tt_size_run_fpgm()
1086 [truetype] Scale F_dot_P down.1090 by 4 and routinely occupied 32 bits in an FT_Long field F_dot_P.1096 for which the true value of F_dot_P is .6 * 0x40000000 = 0x26666666.1098 rounding and F_dot_P is assigned 0x26660000. The lower bits were1102 performance when FT_MulDiv with the scaled-down F_dot_P is less1104 of F_dot_P to FT_F2Dot14 at this point.1106 * src/truetype/ttinterp.c (Compute_Funcs): Scale F_dot_P down by 141109 the use of F_dot_P field.1111 assignment of F_dot_P to its theoretical maximum in case we decide