public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Basile Starynkevitch <basile@starynkevitch.net>
To: gcc-melt@googlegroups.com
Cc: gcc@gcc.gnu.org
Subject: [Ann] GCC MELT plugin 0.9.4 for GCC 4.6 & 4.7
Date: Fri, 02 Mar 2012 17:51:00 -0000	[thread overview]
Message-ID: <20120302185053.d8aa6f91876d70469c319fd6@starynkevitch.net> (raw)
In-Reply-To: <20120301134616.GA26812@ours.starynkevitch.net>

Hello All

It is my pleasure to announce the GCC MELT plugin version 0.9.4 for GCC 4.6 & 4.7.

MELT is a high level domain specific language to extend GCC.
See http://gcc-melt.org/ for more

The MELT plugin 0.9.4 for GCC 4.6 and 4.7 is available as a gzipped source tar archive
from http://gcc-melt.org/melt-0.9.4-plugin-for-gcc-4.6-or-4.7.tgz of size 4353062 bytes
and md5sum 3949d71132c79e833f68b3f35e2d1f9c (march 2nd 2012).

It is extracted from MELT branch svn revision 184792.
The version number 0.9.4 of the MELT plugin is unrelated to the version of the GCC
compiler (4.6 or 4.7) for which it is supposed to work. Bug reports and patches are
welcome (to the gcc-melt@googlegroups.com list).

################################################################
NEWS for 0.9.4 MELT plugin for GCC 4.6 (and 4.7 when available)
released on March 02nd, 2012

   Language improvements
   =====================

Add CHEADER macro to insert header c-code. For example

   (cheader #{#include <readline/readline.h>}#)
or 
   (cheader #{inline int succ(int x) { return x+1;}}#)

[you still need dirty tricks to link an external library into a MELT
module; as a temporary workaround, consider editing melt-module.mk for
them, perhaps defining GCCMELT_MODULE_EXTRALIBES there, or link
manually the library into melt.so meta-plugin]

   Runtime 
   =======

Hash maps have an auxiliary data value, which can be accessed and set
at will. 

   Translator
   ==========

All C-generating devices (primitives, c-iterators, ...) emit their
code in a syntax checking C function, which is never called, but is
emitted to ensure the emittable C code is syntactically correct. This
catch typos in (defprimitive ...) etc... even for e.g. yet unused
primitives.

   Bugs 
   ====

Many bugs have been corrected.
########################################################

Regards.
-- 
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 mine, sont seulement les miennes} ***

       reply	other threads:[~2012-03-02 17:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20120301134616.GA26812@ours.starynkevitch.net>
2012-03-02 17:51 ` Basile Starynkevitch [this message]
2012-03-04 15:32   ` [Ann] GCC MELT plugin 0.9.4.b " Basile Starynkevitch

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=20120302185053.d8aa6f91876d70469c319fd6@starynkevitch.net \
    --to=basile@starynkevitch.net \
    --cc=gcc-melt@googlegroups.com \
    --cc=gcc@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).