[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: about header file parsing

To: akrl <akrl@sdf.org>
Subject: Re: about header file parsing
From: Marc Nieper-Wißkirchen <marc@nieper-wisskirchen.de>
Date: Sun, 13 Jan 2019 21:24:35 +0100
Authentication-results: sourceware.org; auth=none
Cc: David Malcolm <dmalcolm@redhat.com>, Basile Starynkevitch <basile@starynkevitch.net>, jit@gcc.gnu.org
Delivered-to: listarch-jit@gcc.gnu.org
Delivered-to: mailing list jit@gcc.gnu.org
In-reply-to: <xjf36pw9vs6.fsf@sdf.org>
List-help: <mailto:jit-help@gcc.gnu.org>
List-post: <mailto:jit@gcc.gnu.org>
List-subscribe: <mailto:jit-subscribe@gcc.gnu.org>
Mailing-list: contact jit-help@gcc.gnu.org; run by ezmlm
References: <CAEYrNrTE-6VE=5nj0BZV=a-ekQnzK7Yv0n9bBVVCWHNbCLkDFA@mail.gmail.com> <xjf36pw9vs6.fsf@sdf.org>
Sender: jit-owner@gcc.gnu.org

Am So., 13. Jan. 2019 um 20:56 Uhr schrieb akrl <akrl@sdf.org>:

[...]

> Hi Marc,
> there's no technical problem into including these into the patch.
> But unless we have some special reason for that (like minimizing
> LIBGCCJIT_ABI changes) I would rather prefer to have this changes as a
> following patch.
> But I guess is good to have Dave's opinion on all of these points.

Indeed. What is the general policy with respect to the ABI version?
One version bump per patch/feature or one version bump per release
cycle?

[...]

Best,

Marc

Follow-Ups:
- Re: about header file parsing
  - From: akrl <akrl@sdf.org>

References:
- Re: about header file parsing
  - From: Marc Nieper-Wißkirchen <marc@nieper-wisskirchen.de>
- Re: about header file parsing
  - From: akrl <akrl@sdf.org>

Prev by Date: Re: about header file parsing
Next by Date: [FEATURE REQUEST] Implement gcc_jit_sig_atomic_type.
Previous by thread: Re: about header file parsing
Next by thread: Re: about header file parsing
Index(es):
- Date
- Thread