public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
To: gcc-bugs@gcc.gnu.org, gcc@gcc.gnu.org
Subject: Why is there a `0' flag used with `%I' in asm_fprintf ?
Date: Thu, 22 May 2003 14:32:00 -0000	[thread overview]
Message-ID: <200305221417.KAA23629@caip.rutgers.edu> (raw)

Many uses of asm_fprintf in m68k.c and a few in m68hc11.c use the `0'
flag in conjunction with `%I' when calling asm_fprintf.  Reading
through the function body of asm_fprintf in final.c, it appears that
the zero is consumed, but has no effect.  I.e. `%0I' just spits out
IMMEDIATE_PREFIX unmodified as would plain `%I'.

So it seems harmless except for the fact that someone reading the code
in m68k.c might think the `0' flag is supposed to do something.
Should all instances of `%0I' be changed to `%I', or have I missed
something?

		Thanks,
		--Kaveh
--
Kaveh R. Ghazi			ghazi@caip.rutgers.edu

             reply	other threads:[~2003-05-22 14:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-22 14:32 Kaveh R. Ghazi [this message]
2003-05-22 15:59 ` Kaveh R. Ghazi

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=200305221417.KAA23629@caip.rutgers.edu \
    --to=ghazi@caip.rutgers.edu \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    /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).