From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dibyendu Majumdar Subject: Re: [RFC v0 0/4] Give a type to constants too Date: Fri, 11 Aug 2017 11:28:23 +0100 Message-ID: References: <20170311154725.87906-1-luc.vanoostenryck@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: Received: from mail-ua0-f182.google.com ([209.85.217.182]:32927 "EHLO mail-ua0-f182.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751545AbdHKK2Y (ORCPT ); Fri, 11 Aug 2017 06:28:24 -0400 Received: by mail-ua0-f182.google.com with SMTP id 80so13468382uas.0 for ; Fri, 11 Aug 2017 03:28:23 -0700 (PDT) In-Reply-To: Sender: linux-sparse-owner@vger.kernel.org List-Id: linux-sparse@vger.kernel.org To: Luc Van Oostenryck Cc: Christopher Li , Linus Torvalds , Sparse Mailing-list , Jeff Garzik , Pekka Enberg Hi Luc, On 10 August 2017 at 23:34, Luc Van Oostenryck wrote: > * the OP_PUSH instructions do a perfect job of giving a type to functions > arguments > * the OP_PUSH instructions also nicely abstract away the *operation* of > argument passing that all architectures have. It's a good thing. > It is true that OP_PUSH instructions resolved the issue I was having. However there is something odd about them as they are not really instructions in the instruction stream, are they? They get added as arguments to the OP_CALL instruction. The solution works great though. Regards Dibyendu