From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25753 invoked by alias); 22 May 2003 14:17:48 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 25716 invoked from network); 22 May 2003 14:17:47 -0000 Received: from unknown (HELO caip.rutgers.edu) (128.6.236.10) by sources.redhat.com with SMTP; 22 May 2003 14:17:47 -0000 Received: (from ghazi@localhost) by caip.rutgers.edu (8.9.3/8.9.3) id KAA23629; Thu, 22 May 2003 10:17:47 -0400 (EDT) Date: Thu, 22 May 2003 14:32:00 -0000 From: "Kaveh R. Ghazi" Message-Id: <200305221417.KAA23629@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 ? X-SW-Source: 2003-05/txt/msg02007.txt.bz2 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