From: "Mark E." <snowball3@bigfoot.com>
To: binutils@sourceware.cygnus.com, djgpp-workers@delorie.com
Subject: Re: DJGPP and alignment
Date: Wed, 21 Jul 1999 21:51:00 -0000 [thread overview]
Message-ID: <199907220451.EAA27350@out5.ibm.net> (raw)
In-Reply-To: <19990722003428.12362.qmail@daffy.airs.com>
> Or it would if .ctors and .dtors were not specially handled in
> coff_new_section_hook in coffcode.h. So you're OK on constructors and
> destructors if you do indeed use the section names .ctors and .dtors.
>
Ouch, we don't. Our linker script has .ctor and .dtor (yep, no 's'). I just
checked out DJGPP's config files from cvs and sure enough it's .ctor
and .dtor that are emitted. I suppose either a test for .ctor and .dtor
would have to be added in the COFF new section hook, or gcc can be
changed for 3.0 to emit .ctors and .dtors and then fixup the linker script
so either would work.
At any rate, I'd like to hear from the DJGPP folks before deciding
whether or not to proceed with the patch given the conflict.
Mark
---
Mark Elbrecht, snowball3@bigfoot.com
http://snowball.frogspace.net/
next prev parent reply other threads:[~1999-07-21 21:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-21 9:07 Mark E.
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. [this message]
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=199907220451.EAA27350@out5.ibm.net \
--to=snowball3@bigfoot.com \
--cc=binutils@sourceware.cygnus.com \
--cc=djgpp-workers@delorie.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).