This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH 14/27] New files: gcc/jit/jit-builtins.{c|h}

From: Jeff Law <law at redhat dot com>
To: David Malcolm <dmalcolm at redhat dot com>, gcc-patches at gcc dot gnu dot org, jit at gcc dot gnu dot org
Date: Mon, 03 Nov 2014 14:04:11 -0700
Subject: Re: [PATCH 14/27] New files: gcc/jit/jit-builtins.{c|h}
Authentication-results: sourceware.org; auth=none
References: <1414774977-25605-1-git-send-email-dmalcolm at redhat dot com> <1414774977-25605-15-git-send-email-dmalcolm at redhat dot com>

On 10/31/14 11:02, David Malcolm wrote:

These files implement support for builtins, for the
   gcc_jit_context_get_builtin_function
API entrypoint.

Only a subset of builtins are currently supported, based on those
that I needed when porting GNU Octave's JIT.

Attempts to use other builtins may lead to an error:
   "unimplemented primitive type for builtin"
being emitted on the gcc_jit_context.

gcc/jit/
	* jit-builtins.c: New.
	* jit-builtins.h: New.

So how do you envision maintenance on this in the future? Reality isfolks are regularly adding new builtins, are they going to have toupdate the JIT too?


OK for the trunk.

jeff

Follow-Ups:
- Re: [PATCH 14/27] New files: gcc/jit/jit-builtins.{c|h}
  - From: David Malcolm

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]