On 27 March 2013 10:10, Richard Biener wrote:
> On Tue, Mar 26, 2013 at 6:55 PM, Frederic Riss
> wrote:
>> The cost arrays are filled up to
>> MAX_BITS_PER_WORD, thus as a temporary workaround I have defined
>> MAX_BITS_PER_WORD to 64, and I have softened the checks to fail only
>> above MAX_BIT
On Tue, Mar 26, 2013 at 6:55 PM, Frederic Riss wrote:
> While working on having the divisions by constants optimized by my GCC
> targeting, I realized that whatever *muldi3_highpart my backend
> provides, it would never be used because of the bounds checks that
> expmed.c does on the cost arrays.
While working on having the divisions by constants optimized by my GCC
targeting, I realized that whatever *muldi3_highpart my backend
provides, it would never be used because of the bounds checks that
expmed.c does on the cost arrays. For example:
choose_multiplier (abs_d, size, size - 1,
