From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: gdb-patches@sourceware.org
Cc: Phil Muldoon <pmuldoon@redhat.com>
Subject: [PATCH 2/4] compile: Use libcc1.so.0->libcc1.so.1
Date: Tue, 21 Apr 2015 21:36:00 -0000 [thread overview]
Message-ID: <20150421213642.14147.93210.stgit@host1.jankratochvil.net> (raw)
In-Reply-To: <20150421213635.14147.15653.stgit@host1.jankratochvil.net>
Hi,
see [patch 1/4], 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.
include/* changes are here only FYI, master repository of those files is GCC.
Jan
gdb/ChangeLog
2015-04-21 Jan Kratochvil <jan.kratochvil@redhat.com>
* compile/compile-c-support.c (c_get_compile_context): Use
GCC_FE_VERSION_1.
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.
---
gdb/compile/compile-c-support.c | 2 +-
include/gcc-c-interface.h | 2 +-
include/gcc-interface.h | 3 ++-
3 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/gdb/compile/compile-c-support.c b/gdb/compile/compile-c-support.c
index e3c01f2..b09e1bf 100644
--- a/gdb/compile/compile-c-support.c
+++ b/gdb/compile/compile-c-support.c
@@ -107,7 +107,7 @@ c_get_compile_context (void)
gdb_assert (func != NULL);
}
- context = (*func) (GCC_FE_VERSION_0, GCC_C_FE_VERSION_0);
+ context = (*func) (GCC_FE_VERSION_1, GCC_C_FE_VERSION_0);
if (context == NULL)
error (_("The loaded version of GCC does not support the required version "
"of the API."));
diff --git a/include/gcc-c-interface.h b/include/gcc-c-interface.h
index 7108952..0eff259 100644
--- a/include/gcc-c-interface.h
+++ b/include/gcc-c-interface.h
@@ -197,7 +197,7 @@ struct gcc_c_context
/* The name of the .so that the compiler builds. We dlopen this
later. */
-#define GCC_C_FE_LIBCC "libcc1.so." STRINGIFY (GCC_FE_VERSION_0)
+#define GCC_C_FE_LIBCC "libcc1.so." STRINGIFY (GCC_FE_VERSION_1)
/* The compiler exports a single initialization function. This macro
holds its name as a symbol. */
diff --git a/include/gcc-interface.h b/include/gcc-interface.h
index df7db6e..1b33e7d 100644
--- a/include/gcc-interface.h
+++ b/include/gcc-interface.h
@@ -44,7 +44,8 @@ struct gcc_base_context;
enum gcc_base_api_version
{
- GCC_FE_VERSION_0 = 0
+ GCC_FE_VERSION_0 = 0,
+ GCC_FE_VERSION_1 = 1,
};
/* The operations defined by the GCC base API. This is the vtable for
next prev parent reply other threads:[~2015-04-21 21:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-21 21:36 [PATCH 1/4] compile: Use libcc1.so->libcc1.so.0 Jan Kratochvil
2015-04-21 21:36 ` [PATCH 3/4] compile: set debug compile: Display GCC driver filename Jan Kratochvil
2015-04-23 20:40 ` cancel: " Jan Kratochvil
2015-04-21 21:36 ` Jan Kratochvil [this message]
2015-04-23 20:40 ` cancel: [PATCH 2/4] compile: Use libcc1.so.0->libcc1.so.1 Jan Kratochvil
2015-04-21 21:37 ` [PATCH 4/4] compile: Add 'set compile-gcc' Jan Kratochvil
2015-04-22 7:21 ` Eli Zaretskii
2015-04-23 21:09 ` Jan Kratochvil
2015-04-24 6:16 ` Eli Zaretskii
2015-04-24 6:19 ` Jan Kratochvil
2015-04-23 20:40 ` cancel: " Jan Kratochvil
2015-04-23 20:40 ` cancel: [PATCH 1/4] compile: Use libcc1.so->libcc1.so.0 Jan Kratochvil
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=20150421213642.14147.93210.stgit@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--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