From: julia.lawall@lip6.fr (Julia Lawall)
To: cocci@systeme.lip6.fr
Subject: [Cocci] [bug] exists do not work if file group is too big (>49)
Date: Wed, 16 May 2018 22:29:30 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1805162228160.3296@hadrien> (raw)
In-Reply-To: <20180516202430.GE2994@redhat.com>
> [glisse at localhost ~]$ spatch --version
> spatch version 1.0.6 compiled with OCaml version 4.05.0
> Flags passed to the configure script: --build=x86_64-redhat-linux-gnu --host=x86_64-redhat-linux-gnu --program-prefix= --disable-dependency-tracking --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc --datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib64 --libexecdir=/usr/libexec --localstatedir=/var --sharedstatedir=/var/lib --mandir=/usr/share/man --infodir=/usr/share/info --enable-release=yes --with-python=/usr/bin/python3 --with-menhir=/usr/bin/menhir
> Python scripting support: yes
> Syntax of regular expresssions: PCRE
I don't think this indicates whether it is bytecode or native code, and I
don't know what the fedora people offer.
My bytecode executable is 41M and my native code executable is 13M.
julia
next prev parent reply other threads:[~2018-05-16 20:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-16 19:16 [Cocci] [bug] exists do not work if file group is too big (>49) Jerome Glisse
2018-05-16 19:37 ` Julia Lawall
2018-05-16 19:54 ` Jerome Glisse
2018-05-16 20:02 ` Julia Lawall
2018-05-16 20:15 ` Jerome Glisse
2018-05-16 20:20 ` Julia Lawall
2018-05-16 20:24 ` Jerome Glisse
2018-05-16 20:29 ` Julia Lawall [this message]
2018-05-16 20:35 ` Jerome Glisse
[not found] ` <10d2d384-95c0-dec1-b284-f5afb7d9ce81@users.sourceforge.net>
2018-05-17 14:50 ` [Cocci] Checking consequences from “exists” usage with big file name selection Jerome Glisse
[not found] ` <128b6146-5368-12bb-ae42-236982ff3494@users.sourceforge.net>
2018-05-17 14:45 ` [Cocci] exists do not work if file group is too big Jerome Glisse
2018-05-17 20:45 ` Julia Lawall
2018-05-17 21:00 ` Jerome Glisse
2018-05-17 21:11 ` Julia Lawall
2018-05-17 21:32 ` Jerome Glisse
[not found] ` <d1902859-7b9b-4dea-0e5b-8d4876f90495@users.sourceforge.net>
2018-05-18 16:03 ` [Cocci] Checking run times for transformation of Linux source code with SmPL Julia Lawall
[not found] ` <416a7972-d6ce-38b2-9983-ce0446b5ab61@users.sourceforge.net>
2018-05-18 16:49 ` Julia Lawall
[not found] ` <f9b0c961-7182-86ea-bb39-486ffc732db0@users.sourceforge.net>
2018-05-18 17:13 ` Julia Lawall
2018-05-17 20:21 ` [Cocci] [bug] exists do not work if file group is too big (>49) Julia Lawall
2018-05-17 20:31 ` Julia Lawall
2018-05-17 21:04 ` Jerome Glisse
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.20.1805162228160.3296@hadrien \
--to=julia.lawall@lip6.fr \
--cc=cocci@systeme.lip6.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.