This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: PR 55438: Incorrect use of BIGGEST_ALIGNMENT

From: Andreas Schwab <schwab at linux-m68k dot org>
To: Eric Botcazou <ebotcazou at adacore dot com>
Cc: Richard Sandiford <rdsandiford at googlemail dot com>, gcc-patches at gcc dot gnu dot org
Date: Tue, 27 Nov 2012 00:40:46 +0100
Subject: Re: PR 55438: Incorrect use of BIGGEST_ALIGNMENT
References: <871ufi7svh.fsf@talisman.default> <2385141.taqiEgospT@polaris> <87txscchrx.fsf@talisman.default> <2788010.lbKgRQuCzs@polaris>

Eric Botcazou <ebotcazou@adacore.com> writes:

> We could conceivably have an aligned mode with bitsize 32 and alignment 16 
> (i.e. STRICT_ALIGNMENT 1 and BIGGEST_ALIGNMENT 16), meaning that we can use 
> 16-bit aligned 32-bit chunks in this mode.

That's actually what m68k traditionally had.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

References:
- PR 55438: Incorrect use of BIGGEST_ALIGNMENT
  - From: Richard Sandiford
- Re: PR 55438: Incorrect use of BIGGEST_ALIGNMENT
  - From: Eric Botcazou
- Re: PR 55438: Incorrect use of BIGGEST_ALIGNMENT
  - From: Richard Sandiford
- Re: PR 55438: Incorrect use of BIGGEST_ALIGNMENT
  - From: Eric Botcazou

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]