Re: Late-breaking jit features (was Re: [PATCH][gcc] libgccjit: introduce gcc_jit_context_add_driver_option)

2019-02-05 Thread David Malcolm
On Tue, 2019-02-05 at 21:40 +, Andrea Corallo wrote: > David Malcolm writes: > > > On Sat, 2019-02-02 at 16:34 +0100, Jakub Jelinek wrote: > > > On Sat, Feb 02, 2019 at 10:18:43AM -0500, David Malcolm wrote: > > > > > > Alternatively, should these patches go into a branch of > > > > > > queued

Re: Late-breaking jit features (was Re: [PATCH][gcc] libgccjit: introduce gcc_jit_context_add_driver_option)

2019-02-05 Thread Andrea Corallo
David Malcolm writes: > On Sat, 2019-02-02 at 16:34 +0100, Jakub Jelinek wrote: >> On Sat, Feb 02, 2019 at 10:18:43AM -0500, David Malcolm wrote: >> > > > Alternatively, should these patches go into a branch of queued >> > > > jit >> > > > changes for gcc 10? >> > > >> > > Is there anything like

Re: Late-breaking jit features (was Re: [PATCH][gcc] libgccjit: introduce gcc_jit_context_add_driver_option)

2019-02-05 Thread David Malcolm
On Sat, 2019-02-02 at 16:34 +0100, Jakub Jelinek wrote: > On Sat, Feb 02, 2019 at 10:18:43AM -0500, David Malcolm wrote: > > > > Alternatively, should these patches go into a branch of queued > > > > jit > > > > changes for gcc 10? > > > > > > Is there anything like an ABI involved? If so we shoul

Re: Late-breaking jit features (was Re: [PATCH][gcc] libgccjit: introduce gcc_jit_context_add_driver_option)

2019-02-02 Thread Jakub Jelinek
On Sat, Feb 02, 2019 at 10:18:43AM -0500, David Malcolm wrote: > > > Alternatively, should these patches go into a branch of queued jit > > > changes for gcc 10? > > > > Is there anything like an ABI involved? If so we should avoid > > breaking it all the time. Otherwise JIT is not release critica

Re: Late-breaking jit features (was Re: [PATCH][gcc] libgccjit: introduce gcc_jit_context_add_driver_option)

2019-02-02 Thread David Malcolm
On Sat, 2019-02-02 at 08:26 +0100, Richard Biener wrote: > On February 1, 2019 10:11:12 PM GMT+01:00, David Malcolm dhat.com> wrote: > > On Mon, 2019-01-21 at 08:40 +, Andrea Corallo wrote: > > > Hi all, > > > Second version of the patch addressing David's comment about all- > > > non- > > > f

Re: Late-breaking jit features (was Re: [PATCH][gcc] libgccjit: introduce gcc_jit_context_add_driver_option)

2019-02-01 Thread Richard Biener
On February 1, 2019 10:11:12 PM GMT+01:00, David Malcolm wrote: >On Mon, 2019-01-21 at 08:40 +, Andrea Corallo wrote: >> Hi all, >> Second version of the patch addressing David's comment about all-non- >> failing-tests.h >> >> Adds gcc_jit_context_add_driver_option to the libgccjit ABI and a

Late-breaking jit features (was Re: [PATCH][gcc] libgccjit: introduce gcc_jit_context_add_driver_option)

2019-02-01 Thread David Malcolm
On Mon, 2019-01-21 at 08:40 +, Andrea Corallo wrote: > Hi all, > Second version of the patch addressing David's comment about all-non- > failing-tests.h > > Adds gcc_jit_context_add_driver_option to the libgccjit ABI and a > testcase for it. > > Using this interface is now possible to pass op

Re: [PATCH][gcc] libgccjit: introduce gcc_jit_context_add_driver_option

2019-01-21 Thread Kyrill Tkachov
Hi David, On 19/01/19 01:36, David Malcolm wrote: On Fri, 2019-01-18 at 19:25 +, Andrea Corallo wrote: > Hi all, > this patch add gcc_jit_context_add_driver_option to the libgccjit ABI > and a testcase for it. > > Using this interface is now possible to pass options affecting > assembler and

Re: [PATCH][gcc] libgccjit: introduce gcc_jit_context_add_driver_option

2019-01-18 Thread David Malcolm
On Fri, 2019-01-18 at 19:25 +, Andrea Corallo wrote: > Hi all, > this patch add gcc_jit_context_add_driver_option to the libgccjit ABI > and a testcase for it. > > Using this interface is now possible to pass options affecting > assembler and linker. > > Does not introduce any new regression