From: Michele Martone <michelemartone@users.sourceforge.net>
To: linux-kernel@vger.kernel.org, kernelnewbies@kernelnewbies.org
Cc: Julia Lawall <julia.lawall@lip6.fr>, cocci@systeme.lip6.fr
Subject: Munich, Germany, Oct. 8th: Intro to Semantic Patching with Coccinelle
Date: Sat, 21 Sep 2019 08:31:50 +0200 [thread overview]
Message-ID: <20190921063150.GN5628@localhost> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2152 bytes --]
Dear Kernel Hackers,
Coccinelle is a tool routinely used to automatically upgrade Linux
kernel drivers, or catch certain bugs in C programs, or to restructure
C programs.
So some of you may be interested in the following event I'm holding
near Munich, Germany:
*******************************************************************************
"Introduction to Semantic Patching of C programs with Coccinelle"
Tuesday, October 8, 2019, 10:00 - 17:00
Leibniz Supercomputing Centre (LRZ) of the Bavarian Academy of Sciences and
Humanities, Garching near Munich, Boltzmannstr. 1
The maintenance of a large software project can be very demanding. External
factors like evolving third-party software library APIs, or constantly changing
hardware platforms might require significant code adaptions for the code to run
efficiently, or to run at all. Failure in coping with this can lead to
obsolescence, loss of performance, incompatibility, vendor lock-in, bugs.
Have you ever wondered how to detect and manipulate specified classes of C code
constructs, be it for code analysis, or better, to restructure an arbitrarily
large codebase according to a specified, non-trivial `pattern', without writing
a C compiler?
In this training we introduce you to a tool to do exactly this: match and
restructure C codebases in a programmatic, formal way. The training will also
show how to analyze code looking for interesting patterns (e.g. bugs),
integrate with your Python scripts to achieve the custom transformations you
need, and leverage Coccinelle's limited C++ support. Special attention will be
on performance-oriented transformations, of other interests of HPC
practitioners.
After this training, you shall be able to write your own code transformations,
be it for a refactoring, performance improvement, paving the way to an
experimental fork, or for debugging and further analysis.
Teacher: Dr. Michele Martone (LRZ)
Registration and further information
https://www.lrz.de/services/compute/courses/2019-10-08_hspc1w19/
*******************************************************************************
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 163 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
reply other threads:[~2019-09-21 6:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20190921063150.GN5628@localhost \
--to=michelemartone@users.sourceforge.net \
--cc=cocci@systeme.lip6.fr \
--cc=julia.lawall@lip6.fr \
--cc=kernelnewbies@kernelnewbies.org \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).