public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Dave Love <d.love@dl.ac.uk>
To: egcs@cygnus.com
Subject: Re: double alignment patch for x86
Date: Mon, 18 Aug 1997 15:11:59 -0000	[thread overview]
Message-ID: <9708181406.AA23985@issan.informatik.uni-dortmund.de> (raw)
Message-ID: <19970818151159._59jd2P-Pqf5ZhDk9MqUB_Zyb-d1kmSR1XcxkTIRlYE@z> (raw)
In-Reply-To: Sun, 17 Aug 1997 15:47:30 -0600"

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

 Jeffrey> HJ has already submitted this patch.  I'd like to hear from
 Jeffrey> Stan Cox before doing anything with it since he's the x86
 Jeffrey> maintainer.

If nothing else, could STACK_BOUNDARY be changed to 64 on glibc2
systems where the startup does seem to do double alignment, thus 32 is
presumably incorrect?  That will sort out the problem for G77 on GNU
systems using libc2.

Making it 64, dependent on -malign-double, would solve the problem for
us on other GNU/Linux with a patched crt or on other systems which do
double-align the stack.  I'd meant to try to find out what stack
alignment DJGPP and BSD provide but haven't done so.

             reply	other threads:[~1997-08-18 15:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-08-18 14:53 Philippe Laliberte [this message]
1997-08-18 14:53 ` front end interface Andreas Schwab
1997-08-18 14:54 ` Reload patch to improve 386 code Jeffrey A Law
1997-08-18 15:10 ` Will egcs support MachTen? Jeffrey A Law
1997-08-18 15:11 ` double alignment patch for x86 Dave Love
1997-08-18 15:11 ` GCC Projects? Jeffrey A Law
1997-08-18 15:11 Reload patch to improve 386 code meissner
1997-08-18 15:22 ` Monday morning Jeffrey A Law

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=9708181406.AA23985@issan.informatik.uni-dortmund.de \
    --to=d.love@dl.ac.uk \
    --cc=egcs@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).