This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: alignment: store_one_arg vs emit_push_insn
- From: Richard Henderson <rth at redhat dot com>
- To: DJ Delorie <dj at redhat dot com>
- Cc: gcc at gcc dot gnu dot org
- Date: Fri, 9 May 2003 17:03:12 -0700
- Subject: Re: alignment: store_one_arg vs emit_push_insn
- References: <200305092334.h49NYa422781@greed.delorie.com>
On Fri, May 09, 2003 at 07:34:36PM -0400, DJ Delorie wrote:
> /* Some types will require stricter alignment, which will be
> provided for elsewhere in argument layout. */
> parm_align = MAX (PARM_BOUNDARY, TYPE_ALIGN (TREE_TYPE (pval)));
MAX is correct in this case because we know that we're storing
to a parameter, and we know that PARM_BOUNDARY is the minimum
alignment of any parameter.
> The way the code is now, xstormy16 is trying to access
> a byte-aligned object with a HImode move, and failing
You don't give enough information to determine why this might
be the case.
r~