public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Basile Starynkevitch <basile@starynkevitch.net>
To: gcc@gcc.gnu.org
Cc: jeremie.salvucci@free.fr
Subject: plugin-provided pragmas & Fortran or Ada?
Date: Tue, 22 Jun 2010 06:28:00 -0000	[thread overview]
Message-ID: <1277180442.24042.13.camel@glinka> (raw)

Hello,

Assuming a plugin (e.g. MELT) add a new pragma using PLUGIN_PRAGMAS, is
this pragma usable from Ada or Fortran code?

I am not very familiar with Ada or Fortran. I believe Ada has some
syntax for pragmas -but do Ada pragma have the same API inside GCC
plugins as C or C++ pragmas?- and I am not sure about Fortran. Many
Fortran dialects or implementations parse specially some kind of
comments -but I don't know if these are giving pragma events to plugins.

The intended MELT extension I have in mind would convert Gimple (built
by GCC from Ada or C or C++ or Fortran code) to some low-level C code
suitable for Frama-C. Frama-C is a free (LGPL licensed, coded in Ocaml)
static analyzer developed by my colleagues at CEA LIST (& also INRIA
Proval team). See http://frama-c.com/

Frama-C accept some special comments starting with /*@ in a language
called ACSL, see http://frama-c.com/acsl_tutorial_index.html and I was
thinking of using some new pragmas inside GCC to translate these pragmas
to ACSL syntax comments.

All this is exploratory work initiated by my intern Jeremie Salvucci. We
have no idea today if this can be worked out.

Cheers.
-- 
Basile STARYNKEVITCH         http://starynkevitch.net/Basile/
email: basile<at>starynkevitch<dot>net mobile: +33 6 8501 2359
8, rue de la Faiencerie, 92340 Bourg La Reine, France
*** opinions {are only mines, sont seulement les miennes} ***


             reply	other threads:[~2010-06-22  4:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-22  6:28 Basile Starynkevitch [this message]
2010-06-22  7:13 ` Duncan Sands
2010-06-22  7:18   ` Basile Starynkevitch
2010-06-22  9:34     ` Duncan Sands
2010-06-22 12:19     ` Eric Botcazou
2010-06-22  8:59 ` Tobias Burnus

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=1277180442.24042.13.camel@glinka \
    --to=basile@starynkevitch.net \
    --cc=gcc@gcc.gnu.org \
    --cc=jeremie.salvucci@free.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 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).