On 12/12/2017 01:28 AM, Markus Trippelsdorf wrote:
> As the testcase shows, trunk currently generates horrible code for
> divisions used in tight loops. This happens because the algorithm
> expanding div/mod doesn't take parallelism into account and this makes
> the cost model unrealistic.
> Fix th
As the testcase shows, trunk currently generates horrible code for
divisions used in tight loops. This happens because the algorithm
expanding div/mod doesn't take parallelism into account and this makes
the cost model unrealistic.
Fix the issue by increasing the estimated latencies a bit.
Tested
