From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eigenstate.org ([206.124.132.107]) by ewsd; Tue Jun 18 16:37:46 EDT 2019 Received: from eigenstate.org (localhost [127.0.0.1]) by eigenstate.org (OpenSMTPD) with ESMTP id d267704f; Tue, 18 Jun 2019 13:37:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=eigenstate.org; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; s=mail; bh=bFKgi7KH6NdrTK+MZPhy2lZqia8=; b=bmCdrJroWdOqDe/+LoMYWap1mxS9 7ErOidlHU53v8hOtMYBtcEwI91fLup2EZqL5YhzhWKXNM6TB/KBOCZL/ZplJXI0J Nk3cQjklfLnystViEk880GHY7Hbt2Ko15oJBfjwsDufCPqW7clLn2w0A3wKkjG6V EfwM3kkZpjH1WUY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=eigenstate.org; h=date:from :to:cc:subject:message-id:in-reply-to:references:mime-version :content-type:content-transfer-encoding; q=dns; s=mail; b=NkM/gn aYkkuyslTzRsI/JeyAhE+WHYGIHnQdUikPB+1yhBRjTwGY1kZln89wCHRBgWaqtK yhBIpfsyKc/XAQS0pTo9O7RfTcVBEqIVvAM+bEU16YsVY7Ea63rDOBej/C1+fd7g DucUG3pq0+capLEGr1G+a3npW8X3e3rdK6pTU= Received: from zomg.markovcorp.com (markov.via.net [157.22.130.3]) by eigenstate.org (OpenSMTPD) with ESMTPSA id aa4b6506 (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256:NO); Tue, 18 Jun 2019 13:37:45 -0700 (PDT) Date: Tue, 18 Jun 2019 13:37:44 -0700 From: Ori Bernstein To: 9front@9front.org Cc: cinap_lenrek@felloff.net Subject: Re: [9front] Ape: Fix assert warnings. Message-Id: <20190618133744.b22ad0e0b196293e0b3edd13@eigenstate.org> In-Reply-To: <3D3F1554B533A0CDCBE6DCDADE6A7B23@felloff.net> References: <3D3F1554B533A0CDCBE6DCDADE6A7B23@felloff.net> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.32; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: rich-client property SQL over ACPI database framework-based full-stack-aware database I'll look more at the compiler, instead of committing workarounds. On Tue, 18 Jun 2019 18:46:19 +0200 cinap_lenrek@felloff.net wrote: > 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 > -- Ori Bernstein