public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Zack Weinberg <zack@codesourcery.com>
To: binutils@sources.redhat.com
Cc: hans-peter.nilsson@axis.com
Subject: Re: [RFA:] Fix bug with #APP/#NO_APP when using macros.
Date: Fri, 09 May 2003 04:01:00 -0000	[thread overview]
Message-ID: <87el38zs39.fsf@egil.codesourcery.com> (raw)
In-Reply-To: <m3el38vlev.fsf@gossamer.airs.com> (Ian Lance Taylor's message of "08 May 2003 20:39:04 -0700")

Ian Lance Taylor <ian@airs.com> writes:

> It's true that #NO_APP needs to be printed in ASM_FILE_START, but it's
> not true that the CRIS target is the only target which does it.
> m68k.h does it also.  I actually thought that the m68k was the only
> target which used #NO_APP, but I see that you used it for the CRIS.
>
> I take your point, though, which is that though targets other than
> CRIS and m68k emit #APP/#NO_APP around assembler statements, it is
> ineffective and pointless.

And since no one has noticed this up to now, does that mean that there
is no real performance benefit to be had from #NO_APP, and we can blow
away all the code that emits it from gcc?  Or should gcc be changed to
emit #NO_APP at file start?

zw

  reply	other threads:[~2003-05-09  4:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-08  8:08 Hans-Peter Nilsson
2003-05-08 21:39 ` Ian Lance Taylor
2003-05-09  1:09   ` Hans-Peter Nilsson
2003-05-09  3:39     ` Ian Lance Taylor
2003-05-09  4:01       ` Zack Weinberg [this message]
2003-05-09  4:12         ` Ian Lance Taylor
2003-05-09  4:38         ` Alan Modra
2003-05-09  9:10         ` Hans-Peter Nilsson
2003-05-09  9:28           ` Hans-Peter Nilsson
2003-05-13  1:09 ` Hans-Peter Nilsson
2003-05-13  1:27   ` Alan Modra
2003-05-13  2:39     ` Daniel Jacobowitz

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=87el38zs39.fsf@egil.codesourcery.com \
    --to=zack@codesourcery.com \
    --cc=binutils@sources.redhat.com \
    --cc=hans-peter.nilsson@axis.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).