From: elfring@users.sourceforge.net (SF Markus Elfring)
To: cocci@systeme.lip6.fr
Subject: [Cocci] Searching for pass-through functions
Date: Tue, 07 Oct 2014 22:20:24 +0200 [thread overview]
Message-ID: <54344B08.6000008@users.sourceforge.net> (raw)
In-Reply-To: <alpine.DEB.2.02.1410072144150.2079@localhost6.localdomain6>
>> Would you like to clarify corresponding details?
>
> It is completely useless to me without knowing what C files are affected.
They are stored in a public repository.
http://git.minix3.org/index.cgi?p=minix.git;a=tree
I guess that the 24 occurrences of the message 'Failure("lexing: empty token")'
can be discussed a bit later.
I got the message 'EXN:File "./ctlcocci_integration.ml", line 246, characters
4-10: Assertion failed' for the following source files.
1. external/bsd/llvm/dist/clang/test/Sema/statements.c
2. external/bsd/llvm/dist/clang/test/Sema/vla.c
3. external/bsd/llvm/dist/clang/test/Sema/scope-check.c
I got the message 'EXN:Common.Timeout' for the following source files.
1. sys/external/bsd/compiler_rt/dist/test/Unit/udivmodti4_test.c
2. external/bsd/llvm/dist/clang/test/Parser/parser_overflow.c
3. external/public-domain/sqlite/dist/sqlite3.c
The command-line parameter "show-trying" does not display more useful
information in these cases. Is this a bit strange?
I got the message 'EXN:Failure("is_pass_through: node 612: return ...[1,2,259]
in getanswer reachable by inconsistent control-flow paths")' for the source file
'lib/libc/net/gethnamaddr.c'.
I got the message 'EXN:Failure("internal error: there is no noconst or
novolatile keyword")' for the source file
'external/bsd/llvm/dist/clang/test/Sema/declspec.c'.
Regards,
Markus
next prev parent reply other threads:[~2014-10-07 20:20 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-04 17:49 [Cocci] Searching for pass-through functions SF Markus Elfring
2014-10-04 19:17 ` Julia Lawall
2014-10-04 20:22 ` SF Markus Elfring
2014-10-04 21:32 ` Julia Lawall
2014-10-05 6:48 ` SF Markus Elfring
2014-10-05 9:39 ` Julia Lawall
2014-10-05 13:15 ` SF Markus Elfring
2014-10-05 11:45 ` SF Markus Elfring
2014-10-05 11:48 ` Julia Lawall
2014-10-05 12:15 ` SF Markus Elfring
2014-10-05 15:33 ` Julia Lawall
2014-10-05 16:38 ` SF Markus Elfring
2014-10-05 16:42 ` Julia Lawall
2014-10-05 16:55 ` SF Markus Elfring
2014-10-05 17:01 ` Julia Lawall
2014-10-05 17:09 ` SF Markus Elfring
2014-10-05 18:37 ` SF Markus Elfring
2014-10-08 11:40 ` SF Markus Elfring
2014-10-08 11:51 ` Julia Lawall
2014-10-08 12:01 ` SF Markus Elfring
2014-10-08 12:08 ` Julia Lawall
2014-10-08 12:20 ` SF Markus Elfring
2014-10-08 12:48 ` Julia Lawall
2014-10-08 13:01 ` SF Markus Elfring
2014-10-08 18:05 ` SF Markus Elfring
2014-10-09 5:37 ` Julia Lawall
2014-10-07 19:39 ` SF Markus Elfring
2014-10-07 19:44 ` Julia Lawall
2014-10-07 20:20 ` SF Markus Elfring [this message]
2014-10-07 20:26 ` Julia Lawall
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=54344B08.6000008@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--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.