From: Zack Weinberg <zack@codesourcery.com>
To: Hans-Peter Nilsson <hp@bitrange.com>
Cc: Andreas Schwab <schwab@suse.de>, binutils@sources.redhat.com
Subject: Re: demand_empty_rest_of_line and ignore_rest_of_line
Date: Sun, 25 Apr 2004 00:03:00 -0000 [thread overview]
Message-ID: <87brlhdk47.fsf@codesourcery.com> (raw)
In-Reply-To: <Pine.BSF.4.58.0404241755510.6786@dair.pair.com> (Hans-Peter Nilsson's message of "Sat, 24 Apr 2004 18:17:36 -0400 (EDT)")
Hans-Peter Nilsson <hp@bitrange.com> writes:
> That conclusion is incorrect. #NO_APP for cris-* is output
> through default_file_start. It seems there are multiple blessed
> ways to get that #NO_APP out. Hmm, I thought that kind of
> multiplicity was something Zack W disliked but apparently not. ;-)
I *tried*. Y'all keep moving the goalposts. ;-)
>> Maybe the #APP/#NO_APP switching should be removed and input scrubbing
>> enabled all the time, given how few targets actually disable it.
>
> See binutils archives from last time this came up (search for
> "no_app"). It saves as much as 1% off the compile time. I
> think *more* targets should use it, but most would need to tweak
> their md:s to avoid redundant spaces.
Frankly, (as someone who has to stare at GCC's assembly output all the
damn time), I do not think 1% speedup is worth the *severe*
degradation in readability that this would impose. I would much
rather put effort into making GAS's parser be faster in
input-scrubbing mode.
zw
next prev parent reply other threads:[~2004-04-24 23:37 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-17 16:36 Nathan Sidwell
2004-03-17 16:43 ` Hans-Peter Nilsson
2004-03-17 16:49 ` Ian Lance Taylor
2004-03-18 10:29 ` Nathan Sidwell
2004-03-18 13:15 ` Ian Lance Taylor
2004-04-23 23:15 ` Andreas Schwab
2004-04-24 17:36 ` Hans-Peter Nilsson
2004-04-24 17:57 ` Andreas Schwab
2004-04-24 18:26 ` Hans-Peter Nilsson
2004-04-24 19:22 ` Andreas Schwab
2004-04-24 21:31 ` Hans-Peter Nilsson
2004-04-24 21:33 ` Andreas Schwab
2004-04-24 23:25 ` Hans-Peter Nilsson
2004-04-24 23:37 ` Andreas Schwab
2004-04-25 0:03 ` Zack Weinberg [this message]
2004-04-25 0:22 ` Hans-Peter Nilsson
2004-04-26 0:28 ` Zack Weinberg
2004-04-26 0:58 ` Hans-Peter Nilsson
2004-04-26 2:14 ` Hans-Peter Nilsson
2004-04-25 23:35 ` Ian Lance Taylor
2004-04-26 0:51 ` Zack Weinberg
2004-04-26 2:46 ` Ian Lance Taylor
2004-04-26 3:13 ` Zack Weinberg
2004-04-26 14:16 ` Ian Lance Taylor
2004-04-26 14:22 ` Andreas Schwab
2004-04-26 14:34 ` Richard Earnshaw
2004-04-26 15:29 ` Ian Lance Taylor
2004-04-26 19:26 ` Hans-Peter Nilsson
2004-04-26 19:42 ` Kai Henningsen
2004-04-26 19:45 ` Ian Lance Taylor
2004-04-26 20:04 ` Ian Lance Taylor
2004-04-27 1:32 ` Zack Weinberg
2004-04-27 2:02 ` Hans-Peter Nilsson
2004-04-27 2:38 ` Zack Weinberg
2004-04-27 2:35 ` Alan Modra
2004-04-27 3:13 ` Zack Weinberg
2004-04-27 4:33 ` Ian Lance Taylor
2004-04-27 5:19 ` Zack Weinberg
2004-04-27 6:52 ` Ian Lance Taylor
2004-04-27 11:43 ` Richard Earnshaw
2004-04-27 2:47 ` Ian Lance Taylor
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=87brlhdk47.fsf@codesourcery.com \
--to=zack@codesourcery.com \
--cc=binutils@sources.redhat.com \
--cc=hp@bitrange.com \
--cc=schwab@suse.de \
/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).