public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Richard Earnshaw <rearnsha@arm.com>
To: law@cygnus.com
Cc: richard.earnshaw@arm.com
Subject: Re: Minor arm cleanup
Date: Thu, 28 Oct 1999 02:06:00 -0000	[thread overview]
Message-ID: <199910280906.KAA24085@cam-mail1.cambridge.arm.com> (raw)
In-Reply-To: <22169.941064209@upchuck>

> 
> We generally frown upon lower-case macros.
> 
> This change changes the bad_pc and bad_args macros to be upper case.  That's
> it.
> 
> 	* tc-arm.c (bad_args, bad_pc): Renamed to BAD_ARGS and BAD_PC
> 	respectively.

Hmm, When I wrote this originally, bad_args and bad_pc were variables, so 
that compilers (eg sparcworks) that didn't put strings into read-only 
sections wouldn't generate dozens of duplicate strings.  My guess is that 
with the change to internationalize the strings this "optimization" was 
lost.

R.


  reply	other threads:[~1999-10-28  2:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-27 15:54 Jeffrey A Law
1999-10-28  2:06 ` Richard Earnshaw [this message]
1999-11-01 15:35   ` Andreas Schwab

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=199910280906.KAA24085@cam-mail1.cambridge.arm.com \
    --to=rearnsha@arm.com \
    --cc=law@cygnus.com \
    --cc=richard.earnshaw@arm.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).