public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Olivier Hainque <hainque@act-europe.fr>
To: Richard Henderson <rth@redhat.com>, gcc@gcc.gnu.org
Cc: hainque@act-europe.fr
Subject: Re: STACK_BOUNDARY on alpha ports ?
Date: Thu, 22 Jan 2004 11:39:00 -0000	[thread overview]
Message-ID: <20040122123138.A12954@rome.act-europe.fr> (raw)
In-Reply-To: <20040121181636.GB14799@redhat.com>; from rth@redhat.com on Wed, Jan 21, 2004 at 10:16:36AM -0800

Richard Henderson wrote:
> Someone needs to check OpenVMS and Unicos ABIs, since they
> do *not* currently enforce 128-bit alignment.

 The OpenVMS calling standard for alpha states (3.7.1 Call conventions):

   o Stack usage: At any time, the stack pointer must denote an address that
     has the minimum alignment required by the Alpha hardware. In addition,
     whenever control is transferred to another procedure, the stack must be
     octaword aligned.

 Would setting STACK_BOUNDARY to 128 be the right way to address that ?

 I see it does not only impact the allocation of frames as a whole, but also
 the alignment of various pointers within a frame (from what init_emit does).


 As for Unicos, the status of it's support in GCC is unclear to me.  
 
 The section in "supported platforms" is not attractive and I couldn't find
 a mention of unicos in MAINTAINTERS.

  parent reply	other threads:[~2004-01-22 11:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-21 14:35 Olivier Hainque
2004-01-21 18:20 ` Richard Henderson
2004-01-22 10:00   ` Olivier Hainque
2004-01-22 11:39   ` Olivier Hainque [this message]
2004-01-22 19:36     ` Richard Henderson

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=20040122123138.A12954@rome.act-europe.fr \
    --to=hainque@act-europe.fr \
    --cc=gcc@gcc.gnu.org \
    --cc=rth@redhat.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).