From: Nick Clifton <nickc@cygnus.com>
To: snowball3@bigfoot.com
Cc: binutils@sourceware.cygnus.com
Subject: Re: Minor fix to COFF .section change
Date: Wed, 05 Jul 2000 14:47:00 -0000 [thread overview]
Message-ID: <200007052147.OAA01114@elmo.cygnus.com> (raw)
Hi Mark,
: > that creates a new target macro (eg TC_COFF_DEFAULT_SECTION_ATTRIBUTES)
:
: > If you can also generate a
: > paragraph to go into doc/internals.texi describing this new macro,
:
: No problem. So I don't waste your time by guessing and guessing wrong, would
: please let me know where in internals.texi the paragraph should go?
Sure. I would suggest adding the entry to the end of the table that
deals with internal macros in the' CPU backend' node (around line 1341
of the gas/doc/internals.texi file).
Cheers
Nick
next reply other threads:[~2000-07-05 14:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-05 14:47 Nick Clifton [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-07-03 10:42 Nick Clifton
2000-07-03 20:28 ` Mark E.
2000-07-02 14:22 Mark E.
2000-07-02 7:10 Mark E.
2000-07-01 18:39 Mark E.
2000-07-01 20:14 ` DJ Delorie
2000-07-02 7:08 ` Mark E.
2000-07-02 7:08 ` 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=200007052147.OAA01114@elmo.cygnus.com \
--to=nickc@cygnus.com \
--cc=binutils@sourceware.cygnus.com \
--cc=snowball3@bigfoot.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).