public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <ian@zembu.com>
To: "Dmitry Timoshkov" <dmitry@baikal.ru>
Cc: <binutils@sources.redhat.com>
Subject: Re: GAS: support for .previous in the i386 win32 target
Date: Tue, 05 Jun 2001 11:31:00 -0000	[thread overview]
Message-ID: <sipucivkw3.fsf@daffy.airs.com> (raw)
In-Reply-To: <009601c0edb6$a93e7f50$cc823bd5@dima>

"Dmitry Timoshkov" <dmitry@baikal.ru> writes:

> Is there any reason that there is no support for section
> stack manipulation directives in the GAS i386 win32 target?

The general rule of thumb on targets for which the main assembler is
supplied by the vendor is to add pseudo-ops used by the vendor's
assembler.  I suppose win32 is sort of a special case, since the MS
assembler is quite different from gas.

> Are there plans to add support for them (namely .previous)?

I doubt it, but if you write a patch yourself and send it in, somebody
would probably apply it.

Ian

      reply	other threads:[~2001-06-05 11:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-05  3:56 Dmitry Timoshkov
2001-06-05 11:31 ` Ian Lance Taylor [this message]

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=sipucivkw3.fsf@daffy.airs.com \
    --to=ian@zembu.com \
    --cc=binutils@sources.redhat.com \
    --cc=dmitry@baikal.ru \
    /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).