From: Jeff Law <law@redhat.com>
To: David Malcolm <dmalcolm@redhat.com>,
gcc-patches@gcc.gnu.org, jit@gcc.gnu.org
Subject: Re: [PATCH 2/2] jit: add switch statements
Date: Thu, 01 Jan 2015 00:00:00 -0000 [thread overview]
Message-ID: <558C5398.7060404@redhat.com> (raw)
In-Reply-To: <1435259621-45194-2-git-send-email-dmalcolm@redhat.com>
On 06/25/2015 01:13 PM, David Malcolm wrote:
>
> * It extends the libgccjit API. It's not clear to me yet how to
> manage extensions of the libgccjit API: should I use symbol maps
> and versioning, or bump the SONAME? I'm thinking of providing
> precanned feature macros within libgccjit.h e.g:
>
> #define LIBGCCJIT_HAVE_SWITCH_STATEMENT
Seems to me you should use a symbol map and bump the version.
jeff
>
next prev parent reply other threads:[~2015-06-25 19:16 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-01 0:00 switches in GCC JIT? Basile Starynkevitch
2015-01-01 0:00 ` David Malcolm
2015-01-01 0:00 ` Basile Starynkevitch
2015-01-01 0:00 ` David Malcolm
2015-01-01 0:00 ` David Malcolm
2015-01-01 0:00 ` Dibyendu Majumdar
2015-01-01 0:00 ` David Malcolm
2015-01-01 0:00 ` Dibyendu Majumdar
2015-01-01 0:00 ` Basile Starynkevitch
2015-01-01 0:00 ` [PATCH 1/2] Add gcc/typed-splay-tree.h David Malcolm
2015-01-01 0:00 ` Jeff Law
2015-01-01 0:00 ` David Malcolm
2015-01-01 0:00 ` Jeff Law
2015-01-01 0:00 ` [PATCH 2/2] jit: add switch statements David Malcolm
2015-01-01 0:00 ` Basile Starynkevitch
2015-01-01 0:00 ` David Malcolm
2015-01-01 0:00 ` Jeff Law [this message]
2015-01-01 0:00 ` Managing ABI compatibility (was Re: [PATCH 2/2] jit: add switch statements) David Malcolm
2015-01-01 0:00 ` David Malcolm
2015-01-01 0:00 ` [PATCH, committed] jit: add switch statements David Malcolm
2015-01-01 0:00 ` [PATCH 2/2] " Basile Starynkevitch
2015-01-01 0:00 ` David Malcolm
2015-01-01 0:00 ` switches in GCC JIT? 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=558C5398.7060404@redhat.com \
--to=law@redhat.com \
--cc=dmalcolm@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jit@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).