From: Andreas Schwab <schwab@suse.de>
To: Hans-Peter Nilsson <hp@bitrange.com>
Cc: binutils@sources.redhat.com
Subject: Re: demand_empty_rest_of_line and ignore_rest_of_line
Date: Sat, 24 Apr 2004 21:33:00 -0000 [thread overview]
Message-ID: <jeoephhxlv.fsf@sykes.suse.de> (raw)
In-Reply-To: <Pine.BSF.4.58.0404241431020.68135@dair.pair.com> (Hans-Peter Nilsson's message of "Sat, 24 Apr 2004 15:22:57 -0400 (EDT)")
Hans-Peter Nilsson <hp@bitrange.com> writes:
> On Sat, 24 Apr 2004, Andreas Schwab wrote:
>> Hans-Peter Nilsson <hp@bitrange.com> writes:
>>
>> > I think you forgot CRIS.
>>
>> CRIS doesn't as of current gcc mainline, and probably never did.
>
> I assume you mean s/gcc/glibc/?.
No. gcc for cris does not (re-)define TARGET_ASM_FILE_START_APP_OFF, so
the assembler never goes into NO_APP mode.
>> m68k always did it.
>
> No, at least for a while it (m68k-linux) didn't. See for
> example the gcc-3.3 branch as of Mon Feb 23 18:58:32 GMT 2004.
I can't find any relevant changes in this time frame under config/m68k on
the 3.3 branch. IIRC m68k-linux never redefined ASM_FILE_START and still
inherits TARGET_ASM_FILE_START_APP_OFF from m68k.h.
> Not that any of this is relevant wrt. the actual incorrectness
> of emitting comments while in #NO_APP mode.
Maybe the #APP/#NO_APP switching should be removed and input scrubbing
enabled all the time, given how few targets actually disable it.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, MaxfeldstraÃe 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2004-04-24 21:31 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 [this message]
2004-04-24 23:25 ` Hans-Peter Nilsson
2004-04-24 23:37 ` Andreas Schwab
2004-04-25 0:03 ` Zack Weinberg
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=jeoephhxlv.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=binutils@sources.redhat.com \
--cc=hp@bitrange.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).