From: Basile Starynkevitch <basile@starynkevitch.net>
To: mirimnan017@gmail.com
Cc: gcc@gcc.gnu.org, STARYNKEVITCH Basile <basile.starynkevitch@cea.fr>
Subject: Your GSoc'22 submission for GCC
Date: Sun, 26 Sep 2021 17:58:47 +0200 [thread overview]
Message-ID: <266cf9bc-925f-c2a9-4e1a-7c6e99922964@starynkevitch.net> (raw)
Hello Mir Mimmad,
If your future GSoC submission is about middle-end extensions to improve
GCC warnings, you might consider starting from the Bismon static source
code analyzer plugin on https://github.com/bstarynk/bismon/
<https://github.com/bstarynk/bismon/> and some /unofficial/
documentation on http://starynkevitch.net/Basile/bismon-doc.pdf
<http://starynkevitch.net/Basile/bismon-doc.pdf> (in PDF format, A4 paper)
Bismon is probably ending because of lack of funding. You could study
its source code and (if your teachers and funding organizations agree)
continue the work on it. I am supposed to work on Frama-C
<https://frama- c.com/> instead next week (starting from october 2021).
You could be interested by the DECODER European project, see
http://www.decoder-project.eu/ <http://www.decoder-project.eu/>
Regards.
PS. My pet open source project is RefPerSys <http://refpersys.org/>
(symbolic artificial intelligence). Jacques Pitrat's last book
Artificial Beings: the Conscience of a Conscious Machine
(ISBN-13: 978-1848211018) could interest you.
--
Basile Starynkevitch <basile@starynkevitch.net>
(only mine opinions / les opinions sont miennes uniquement)
92340 Bourg-la-Reine, France
web page: starynkevitch.net/Basile/
reply other threads:[~2021-09-26 15:58 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=266cf9bc-925f-c2a9-4e1a-7c6e99922964@starynkevitch.net \
--to=basile@starynkevitch.net \
--cc=basile.starynkevitch@cea.fr \
--cc=gcc@gcc.gnu.org \
--cc=mirimnan017@gmail.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).