From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.3 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id BFD7DC433E0 for ; Tue, 19 May 2020 11:23:32 +0000 (UTC) Received: from isis.lip6.fr (isis.lip6.fr [132.227.60.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 4AA8B20708 for ; Tue, 19 May 2020 11:23:32 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 4AA8B20708 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=inria.fr Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=cocci-bounces@systeme.lip6.fr Received: from systeme.lip6.fr (systeme.lip6.fr [132.227.104.7]) by isis.lip6.fr (8.15.2/8.15.2) with ESMTP id 04JBNTcn007062; Tue, 19 May 2020 13:23:29 +0200 (CEST) Received: from systeme.lip6.fr (systeme.lip6.fr [127.0.0.1]) by systeme.lip6.fr (Postfix) with ESMTP id 630B57559; Tue, 19 May 2020 13:23:29 +0200 (CEST) Received: from isis.lip6.fr (isis.lip6.fr [132.227.60.2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by systeme.lip6.fr (Postfix) with ESMTPS id 436093DC8 for ; Tue, 19 May 2020 13:23:28 +0200 (CEST) Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by isis.lip6.fr (8.15.2/8.15.2) with ESMTPS id 04JBNR8R006208 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Tue, 19 May 2020 13:23:27 +0200 (CEST) X-IronPort-AV: E=Sophos;i="5.73,410,1583190000"; d="scan'208";a="450381953" Received: from abo-173-121-68.mrs.modulonet.fr (HELO hadrien) ([85.68.121.173]) by mail2-relais-roc.national.inria.fr with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 19 May 2020 13:23:27 +0200 Date: Tue, 19 May 2020 13:23:27 +0200 (CEST) From: Julia Lawall X-X-Sender: jll@hadrien To: Markus Elfring In-Reply-To: <5c451649-4077-e54c-e01d-6bdbc0d02046@web.de> Message-ID: References: <4a677190-b494-138c-4782-eec033a77377@web.de> <0a93e321-42de-3534-9c4a-d67132a1289e@web.de> <8f3cbbd1-653e-ab2d-5a41-18eec00ae828@web.de> <5c451649-4077-e54c-e01d-6bdbc0d02046@web.de> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="8323329-1386965043-1589887407=:2503" X-Greylist: Sender IP whitelisted, Sender e-mail whitelisted, not delayed by milter-greylist-4.4.3 (isis.lip6.fr [132.227.60.2]); Tue, 19 May 2020 13:23:29 +0200 (CEST) X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.4.3 (isis.lip6.fr [132.227.60.2]); Tue, 19 May 2020 13:23:27 +0200 (CEST) X-Scanned-By: MIMEDefang 2.78 on 132.227.60.2 X-Scanned-By: MIMEDefang 2.78 on 132.227.60.2 Cc: Chuhong Yuan , cocci@systeme.lip6.fr Subject: Re: [Cocci] How to match function calls in macros? X-BeenThere: cocci@systeme.lip6.fr X-Mailman-Version: 2.1.13 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: cocci-bounces@systeme.lip6.fr Errors-To: cocci-bounces@systeme.lip6.fr This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --8323329-1386965043-1589887407=:2503 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8BIT On Tue, 19 May 2020, Markus Elfring wrote: > >> Can the semantic patch language help to insist for a search that a bit > >> of source code belongs to the implementation of a function-like macro? > > > > That's what the search that was written does. The pattern that comes > > after #define has to be in the definition of the macro. > > I suggest to consider additional source code variants. > With which SmPL constructs should be ensured that a search pattern > like “<+... f(...) ...+>” refers only to content from the same logical source line? > https://en.cppreference.com/w/c/language/translation_phases#Phase_2 Please stop asking the same question over and over. In the context of a macro definition, <+... f(...) ...+> will only match what is from the same logical source line. Because that is all that there is in a macro definition. If Coccinelle is working on a macro definition, it works only on that macro definition. If it is working on a function definition, it works only on that function definition. julia --8323329-1386965043-1589887407=:2503 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Cocci mailing list Cocci@systeme.lip6.fr https://systeme.lip6.fr/mailman/listinfo/cocci --8323329-1386965043-1589887407=:2503--