From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from duke.felloff.net ([216.126.196.34]) by ewsd; Tue Jun 18 12:46:26 EDT 2019
Message-ID: <3D3F1554B533A0CDCBE6DCDADE6A7B23@felloff.net>
Date: Tue, 18 Jun 2019 18:46:19 +0200
From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] Ape: Fix assert warnings.
In-Reply-To: 20190618093641.2ec61addb29b579338cacbde@eigenstate.org
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: abstract CMS rich-client framework 

no, stdio putc() macro has a different problem.

the null warning comes from trailing int cast
after the character assignment:

CAST INT (1) /tmp/b.c:6[stdin:231]
   AS CHAR (1) /tmp/b.c:6[stdin:231]
      IND CHAR (1) /tmp/b.c:6[stdin:231]
         POSTINC IND CHAR (1) /tmp/b.c:6[stdin:231]
            NAME "_IO_stream" 48 <10> IND CHAR /tmp/b.c:6[stdin:231]
            Z
         Z
      CONST "33" <20> CHAR /tmp/b.c:6[stdin:231]
   Z

the compiler could statically know if the COND has a
result and not insert the cast.

--
cinap