From: "Mark E." <snowball3@bigfoot.com>
To: binutils@sourceware.cygnus.com
Subject: DJGPP and alignment
Date: Wed, 21 Jul 1999 09:07:00 -0000 [thread overview]
Message-ID: <199907211607.QAA38452@out1.ibm.net> (raw)
Hello again,
A consensus of the DJGPP workers has decided that the default
alignment should be 16 bytes instead of the current 4 bytes since 16 is
the recommended Intel alignment.
Do I need another to handle the non-BFD case or does this one cover
it?
Note for coff-go32.c I made the attached patch relative to my last one.
Mark
---
Mark Elbrecht, snowball3@bigfoot.com
http://snowball.frogspace.net/
next reply other threads:[~1999-07-21 9:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-21 9:07 Mark E. [this message]
1999-07-21 9:31 ` Donn Terry
1999-07-21 17:30 ` Mark E.
1999-07-21 11:47 ` Richard Henderson
1999-07-21 17:30 ` Mark E.
1999-07-21 17:35 ` Ian Lance Taylor
1999-07-21 20:23 ` Donn Terry
1999-07-22 0:13 ` Ian Lance Taylor
1999-07-21 21:51 ` Mark E.
1999-07-22 1:10 ` Eli Zaretskii
1999-07-22 6:08 ` Mark E.
1999-07-21 9:57 Mark E.
1999-07-22 8:23 John Marshall
1999-07-22 11:53 ` Ian Lance Taylor
1999-07-22 13:34 ` Mark E.
1999-07-22 14:37 ` Ian Lance Taylor
1999-07-22 11:32 Mark E.
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=199907211607.QAA38452@out1.ibm.net \
--to=snowball3@bigfoot.com \
--cc=binutils@sourceware.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).