public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@issan.informatik.uni-dortmund.de>
To: law@cygnus.com
Cc: Kamil Iskra <kamil@dwd.interkom.pl>,
	Richard Henderson <rth@cygnus.com>,
	Greg McGary <gkm@eng.ascend.com>,
	egcs@cygnus.com
Subject: Re: STRICT_ALIGNMENT is too strict for m68k
Date: Mon, 18 May 1998 06:02:00 -0000	[thread overview]
Message-ID: <vyz1ztsrluw.fsf@issan.informatik.uni-dortmund.de> (raw)
In-Reply-To: <11339.895451899@hurl.cygnus.com>

Jeffrey A Law <law@cygnus.com> writes:

|>   In message < Pine.LNX.3.96.980517174658.6643A-100000@jinks.home >you write:
|>   > > Yes.  See how it affects the alignment (and thus the size) of a 
|>   > > structure in layout_record.
|>   > 
|>   > I see. Thanks for the explanation.
|> It also effects how parameters are passed in registers for some
|> targets (see calls.c).

The m68k does not pass parameters in registers.

|>   > However, I spent some time today on this part of stor-layout.c trying to
|>   > understand it and build a testcase that would prove my patch wrong and so
|>   > far I failed.
|> Not worth the trouble to write a testcase for this.  We know the
|> change is ABI unsafe.

I have changed STRICT_ALIGNMENT to 0 some time ago in m68k-linux, and no
structure layout has ever changed.  I'm not convinced that this change
ever effects it, only the way unaligned accesses are handled.

-- 
Andreas Schwab                                      "And now for something
schwab@issan.informatik.uni-dortmund.de              completely different"
schwab@gnu.org

  reply	other threads:[~1998-05-18  6:02 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-05-14 15:38 Greg McGary
1998-05-14 22:14 ` Rask Ingemann Lambertsen
1998-05-15 12:05 ` Jim Wilson
1998-05-15 14:35   ` Greg McGary
1998-05-16 19:47     ` Richard Henderson
1998-05-18 12:09       ` Jim Wilson
1998-05-19  8:03         ` Kamil Iskra
1998-05-19 20:24           ` Jim Wilson
1998-05-18 11:32     ` Jim Wilson
1998-05-18 23:58     ` Jeffrey A Law
1998-05-16 19:47   ` Kamil Iskra
1998-05-16 22:35     ` Richard Henderson
1998-05-17 10:51       ` Kamil Iskra
1998-05-17 18:05         ` Jeffrey A Law
1998-05-18  6:02           ` Andreas Schwab [this message]
1998-05-18 23:58             ` Jim Wilson
1998-05-20  2:27               ` Andreas Schwab
1998-05-19 21:17             ` Rask Ingemann Lambertsen
1998-05-18 12:09     ` Jim Wilson

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=vyz1ztsrluw.fsf@issan.informatik.uni-dortmund.de \
    --to=schwab@issan.informatik.uni-dortmund.de \
    --cc=egcs@cygnus.com \
    --cc=gkm@eng.ascend.com \
    --cc=kamil@dwd.interkom.pl \
    --cc=law@cygnus.com \
    --cc=rth@cygnus.com \
    /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).