Re: Backport PR 69400: Invalid 128-bit modulus result

2016-05-19 Thread Richard Biener
On Thu, May 19, 2016 at 9:27 AM, Richard Sandiford wrote: > There doesn't seem to have been any fallout from the fix for PR69400 > and it applies cleanly to gcc-5-branch. > > Bootstrapped & regression-tested on x86_64-linux-ngu. OK for gcc 5? Ok. Thanks, Richard. > Thanks, > Richard > > > Back

Backport PR 69400: Invalid 128-bit modulus result

2016-05-19 Thread Richard Sandiford
There doesn't seem to have been any fallout from the fix for PR69400 and it applies cleanly to gcc-5-branch. Bootstrapped & regression-tested on x86_64-linux-ngu. OK for gcc 5? Thanks, Richard Backport from mainline: gcc/ 2016-01-26 Richard Sandiford PR tree-optimization/69400

Re: PR 69400: Invalid 128-bit modulus result

2016-01-22 Thread Jakub Jelinek
On Fri, Jan 22, 2016 at 09:43:52AM +, Richard Sandiford wrote: > gcc/ > PR tree-optimization/69400 > * wide-int.cc (wi_pack): Take the precision as argument and > perform canonicalization here rather than in the callers. > Use the main loop to handle all full-width HWIs.

PR 69400: Invalid 128-bit modulus result

2016-01-22 Thread Richard Sandiford
As described in the PR, wi::divmod_internal was sign- rather than zero-extending a modulus result in cases where the result has fewer HWIs than the precision and the upper bit of the upper HWI was set. This patch tries to make things more robust by getting wi_pack to handle the canonicalisation st