public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <law@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>, gcc-patches@gcc.gnu.org
Cc: Phil Muldoon <pmuldoon@redhat.com>
Subject: Re: [PATCH 2/5] libcc1: Use libcc1.so.0->libcc1.so.1
Date: Wed, 22 Apr 2015 13:12:00 -0000	[thread overview]
Message-ID: <55379E52.7090209@redhat.com> (raw)
In-Reply-To: <20150421214116.14972.25534.stgit@host1.jankratochvil.net>

On 04/21/2015 03:41 PM, Jan Kratochvil wrote:
> Hi,
>
> see [patch 1/5], particularly:
> (3) Currently there is no backward or forward compatibility although there
>      could be one implemented.  Personally I think the 'compile' feature is
>      still in experimental stage so that it is OK to require last releases.
>      At least in Fedora we can keep GDB<->GCC in sync.
>
> GDB counterpart:
> 	[PATCH 2/4] compile: Use libcc1.so.0->libcc1.so.1
> 	https://sourceware.org/ml/gdb-patches/2015-04/msg00806.html
> 	Message-ID: <20150421213642.14147.93210.stgit@host1.jankratochvil.net>
>
>
> Jan
>
>
> include/ChangeLog
> 2015-04-21  Jan Kratochvil  <jan.kratochvil@redhat.com>
>
> 	* gcc-c-interface.h (GCC_C_FE_LIBCC): Update it to GCC_FE_VERSION_1.
> 	* gcc-interface.h (enum gcc_base_api_version): Add GCC_FE_VERSION_1.
>
> libcc1/ChangeLog
> 2015-04-21  Jan Kratochvil  <jan.kratochvil@redhat.com>
>
> 	* Makefile.am (libcc1_la_LDFLAGS): Add version-info 1.
> 	* Makefile.in: Regenerate.
> 	* libcc1.cc (vtable, gcc_c_fe_context): Update it to GCC_FE_VERSION_1.
OK.  Please install on the trunk.

jeff

  reply	other threads:[~2015-04-22 13:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-21 21:41 [PATCH 1/5] libcc1: Make libcc1.so->libcc1.so.0 Jan Kratochvil
2015-04-21 21:41 ` [PATCH 3/5] libcc1: set debug compile: Display GCC driver filename Jan Kratochvil
2015-04-22 13:12   ` Jeff Law
2015-04-21 21:41 ` [PATCH 5/5] libcc1: 'set debug compile': Display absolute " Jan Kratochvil
2015-04-22 13:09   ` Jeff Law
2015-04-21 21:41 ` [PATCH 4/5] libcc1: Add 'set compile-gcc' Jan Kratochvil
2015-04-22 13:10   ` Jeff Law
2015-04-21 21:41 ` [PATCH 2/5] libcc1: Use libcc1.so.0->libcc1.so.1 Jan Kratochvil
2015-04-22 13:12   ` Jeff Law [this message]
2015-04-22 13:13 ` [PATCH 1/5] libcc1: Make libcc1.so->libcc1.so.0 Jeff Law

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=55379E52.7090209@redhat.com \
    --to=law@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jan.kratochvil@redhat.com \
    --cc=pmuldoon@redhat.com \
    /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).