From: Basile Starynkevitch <basile@starynkevitch.net>
To: Basile Starynkevitch <basile@starynkevitch.net>
Cc: gcc-melt@googlegroups.com, gcc@gcc.gnu.org
Subject: Re: Announce: MELT 0.9.5rc2 release candidate (for GCC 4.6 and 4.7)
Date: Mon, 02 Apr 2012 10:35:00 -0000 [thread overview]
Message-ID: <20120402103525.GA27488@ours.starynkevitch.net> (raw)
In-Reply-To: <20120402103051.GA27387@ours.starynkevitch.net>
On Mon, Apr 02, 2012 at 12:30:51PM +0200, Basile Starynkevitch wrote:
> Hello All,
>
> It is my pleasure to announce the MELT plugin 0.9.5 release candidate 2 for GCC 4.6 or 4.7.
MELT is a high-level domain specific language to extend GCC
> ################################################################
> NEWS for 0.9.5rc2 MELT plugin for GCC 4.6 & 4.7
> [[April 2nd 2012]] release candidate 2
>
> Alternative infix syntax is abandoned (it was never implemented)
>
> Accept $(sub sepxr) in macro-string and $[seq sepxr]
>
> Handle SIGIO Unix signals with asynchronous input channels
> (experimental feature)
>
> Can be compiled by C++ (since GCC 4.7 often is)
>
> All the values are translated to melt_ptr_t variables, not void*
> ones.
> ###############################################################
>
> I believe it should work for a GCC 4.7 compiled in C++ mode.
> Thanks to Alexnadre Lissy & Romain Geissler for their help.
>
> Please test and report bugs or build success or failure on
> gcc-melt@googlegroups.com list.
Sorry, I forgot the download information
The release candidate 2 of MELT plugin 0.9.5 is still perhaps buggy but is available from
http://gcc-melt.org/melt-0.9.5rc2-plugin-for-gcc-4.6-or-4.7.tar.gz
as a gzipped tar archive of 4476348 bytes and md5sum 75e528535b05a03f452b55018b6b085b.
You could try building it e.g. with
make CC=gcc-4.7 CXX=g++-4.7
or perhaps with
make MELTGCC=gcc-4.7 GCCMELT_CC=g++-4.7.
Please report bugs on gcc-melt list. It is extracted from MELT branch svn revision 186078, april 2nd 2012.
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} ***
prev parent reply other threads:[~2012-04-02 10:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-29 20:02 pre-announce: MELT 0.9.5rc1 plugin for GCC 4.6 & 4.7 pre-release candidate 1 (and help needed on make issues) Basile Starynkevitch
2012-03-29 20:45 ` [GCC-MELT-386] " Romain Geissler
2012-03-29 21:03 ` [GCC-MELT-387] " Basile Starynkevitch
2012-03-29 21:29 ` Romain Geissler
2012-03-30 5:22 ` Basile Starynkevitch
2012-03-30 9:41 ` MELT 0.9.5rc1 etc Basile Starynkevitch
2012-03-31 0:23 ` [GCC-MELT-391] " Romain Geissler
2012-03-31 7:08 ` Basile Starynkevitch
2012-03-31 8:52 ` Romain Geissler
2012-03-31 10:28 ` Basile Starynkevitch
2012-03-31 11:55 ` Romain Geissler
2012-03-31 12:03 ` Romain Geissler
2012-03-31 12:39 ` [GCC-MELT-397] " Basile Starynkevitch
2012-03-31 13:07 ` Jonathan Wakely
2012-03-31 13:56 ` Romain Geissler
2012-03-31 14:30 ` Basile Starynkevitch
2012-04-02 10:31 ` Announce: MELT 0.9.5rc2 release candidate (for GCC 4.6 and 4.7) Basile Starynkevitch
2012-04-02 10:35 ` Basile Starynkevitch [this message]
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=20120402103525.GA27488@ours.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).