On 14/07/11 15:15, Richard Guenther wrote:
Is this version OK?
Ok.
I've just committed this slightly updated patch.
I found some bugs while testing, now fixed. Most of the changes in this
patch are context changes, and using widened_mode to handle VOIDmode
constants.
Andrew
2011-08-19
On 21/07/11 20:29, Joseph S. Myers wrote:
On Tue, 12 Jul 2011, Richard Guenther wrote:
(**) We really ought to forbid any arithmetic on types that have non-mode
precision and only allow conversions to/from such types.
Arithmetic on such types is a perfectly reasonable notion to have in
On 23/06/11 15:39, Andrew Stubbs wrote:
This patch has two effects:
1. It permits the use of widening multiply instructions that widen by
more than one mode. E.g. HImode - DImode.
2. It enables the use of widening multiply instructions for (extended)
inputs of narrower mode than the
On Tue, Jul 12, 2011 at 11:50 AM, Andrew Stubbs a...@codesourcery.com wrote:
On 23/06/11 15:39, Andrew Stubbs wrote:
This patch has two effects:
1. It permits the use of widening multiply instructions that widen by
more than one mode. E.g. HImode - DImode.
2. It enables the use of widening
On 12/07/11 12:05, Richard Guenther wrote:
(**) We really ought to forbid any arithmetic on types that have non-mode
precision and only allow conversions to/from such types.
Hmmm, presumably the problem is that we might have a compatible
precision, but the backends actually work with purely
On Tue, Jul 12, 2011 at 1:26 PM, Andrew Stubbs andrew.stu...@gmail.com wrote:
On 12/07/11 12:05, Richard Guenther wrote:
(**) We really ought to forbid any arithmetic on types that have non-mode
precision and only allow conversions to/from such types.
Hmmm, presumably the problem is that we
