From: "Mark E." <snowball3@bigfoot.com>
To: binutils@sourceware.cygnus.com
Subject: Re: patch for COFF .section
Date: Thu, 29 Jun 2000 21:55:00 -0000 [thread overview]
Message-ID: <395BF031.21178.4C7BA6@localhost> (raw)
Thanks for checking it in.
I've studied the !BFD_ASSEMBLER version of obj_coff_section and it also
doesn't warn in not warning about changing attributes after they've already
been set, but with a twist. !bfd gas for DJGPP takes this:
.section .foo,"x"
.section .foo,"b"
.section .foo,"w"
and sets the section attributes for code, data, and bss.
The problem with fixing this is you can't tell the difference between a
section that was just created by subseg_new and an existing section that
happens to have the default flags.
Mark
next reply other threads:[~2000-06-29 21:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-29 21:55 Mark E. [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-06-29 16:54 Nick Clifton
2000-06-27 12:54 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=395BF031.21178.4C7BA6@localhost \
--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).