This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
force_const_mem VOIDmode
- From: Alan Modra <amodra at gmail dot com>
- To: gcc-patches at gcc dot gnu dot org
- Date: Fri, 7 Jun 2013 11:30:53 +0930
- Subject: force_const_mem VOIDmode
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_unreachable(). Bootstrapped etc. powerpc64-linux.
* varasm.c (force_const_mem): Assert mode is not VOID or BLK.
Index: gcc/varasm.c
===================================================================
--- gcc/varasm.c (revision 199718)
+++ gcc/varasm.c (working copy)
@@ -3567,7 +3575,8 @@
*slot = desc;
/* Align the location counter as required by EXP's data type. */
- align = GET_MODE_ALIGNMENT (mode == VOIDmode ? word_mode : mode);
+ gcc_checking_assert (mode != VOIDmode && mode != BLKmode);
+ align = GET_MODE_ALIGNMENT (mode);
#ifdef CONSTANT_ALIGNMENT
{
tree type = lang_hooks.types.type_for_mode (mode, 0);
--
Alan Modra
Australia Development Lab, IBM