public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Nathan Sidwell <nathan@codesourcery.com>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: Kazu Hirata <kazu@codesourcery.com>,
	 gcc-patches@gcc.gnu.org,   law@redhat.com,  schwab@suse.de
Subject: Re: [patch] m68k: Fix binary compatibility problem with -mno-strict-align.  (Take 2)
Date: Wed, 29 Aug 2007 16:53:00 -0000	[thread overview]
Message-ID: <46D59E27.70708@codesourcery.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0708291622280.1820@scrub.home>

Roman Zippel wrote:

> Looking at this a little closer, I'm not sure why this is related to 
> alignment in first place. Whether a structure is returned in a register 
> should be controlled by -fpcc-struct-return/-freg-struct-return and the 
> DEFAULT_PCC_STRUCT_RETURN value in the config. In 
> function.c:aggregate_value_p there is shortly after the return_in_memory 
> hook the following test:
> 
>   if (flag_pcc_struct_return && AGGREGATE_TYPE_P (type))
>     return 1;
> 
> IMO the alignment should have no influence here, so where is this coming 
> from? 

store layout sets the mode of a structure depending on STRICT_ALIGNMENT.  For 
instance a {short, short} struct will get SI mode if STRICT_ALIGNMENT is false. 
  When it's true such a struct will get BLKmode.  The default can-return-in-reg 
hook examines the type's mode.  If it's BLKmode, it is returned in memory, if 
it's an integral mode it is returned in a register.

nathan
-- 
Nathan Sidwell    ::   http://www.codesourcery.com   ::         CodeSourcery

      parent reply	other threads:[~2007-08-29 16:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-25 15:59 Kazu Hirata
2007-08-28 13:32 ` Andreas Schwab
2007-08-29 14:57 ` Roman Zippel
2007-08-29 15:26   ` Kazu Hirata
2007-08-29 16:11     ` Roman Zippel
2007-08-29 17:14       ` Nathan Sidwell
2007-08-29 18:19         ` Roman Zippel
2007-08-29 18:28           ` Nathan Sidwell
2007-08-29 16:53   ` Nathan Sidwell [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=46D59E27.70708@codesourcery.com \
    --to=nathan@codesourcery.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=kazu@codesourcery.com \
    --cc=law@redhat.com \
    --cc=schwab@suse.de \
    --cc=zippel@linux-m68k.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).