Re: force_const_mem VOIDmode

2013-06-13 Thread Alan Modra
On Thu, Jun 13, 2013 at 04:29:44PM +0200, Andreas Krebbel wrote: > On 07/06/13 04:00, Alan Modra wrote: > > force_const_mem() isn't supposed to handle VOIDmode or BLKmode, so the > > check for VOIDmode when aligning is needless. If we ever did get one > > of these modes in a constant pool, this >

Re: force_const_mem VOIDmode

2013-06-13 Thread Andreas Krebbel
On 07/06/13 04:00, Alan Modra wrote: > force_const_mem() isn't supposed to handle VOIDmode or BLKmode, so the > check for VOIDmode when aligning is needless. If we ever did get one > of these modes in a constant pool, this > > pool->offset += GET_MODE_SIZE (mode); Hi Alan, the assertion is tr

Re: force_const_mem VOIDmode

2013-06-07 Thread Richard Biener
On Fri, Jun 7, 2013 at 4:00 AM, Alan Modra wrote: > force_const_mem() isn't supposed to handle VOIDmode or BLKmode, so the > check for VOIDmode when aligning is needless. If we ever did get one > of these modes in a constant pool, this > > pool->offset += GET_MODE_SIZE (mode); > > won't add to

force_const_mem VOIDmode

2013-06-06 Thread Alan Modra
force_const_mem() isn't supposed to handle VOIDmode or BLKmode, so the check for VOIDmode when aligning is needless. If we ever did get one of these modes in a constant pool, this pool->offset += GET_MODE_SIZE (mode); won't add to the pool size, and output_constant_pool_2() will hit a gcc_unre