From a984e92e9e7758c3255d584cdbc3d107c837cecf Mon Sep 17 00:00:00 2001 From: Joey Ye Date: Tue, 14 Jan 2014 07:29:25 +0000 Subject: [PATCH] plugin.texi (Building GCC plugins): Update to C++. 2014-01-14 Joey Ye * doc/plugin.texi (Building GCC plugins): Update to C++. From-SVN: r206597 --- gcc/ChangeLog | 4 ++++ gcc/doc/plugins.texi | 18 +++++++++--------- 2 files changed, 13 insertions(+), 9 deletions(-) diff --git a/gcc/ChangeLog b/gcc/ChangeLog index 53428a637e9..3a832d0e898 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,7 @@ +2014-01-14 Joey Ye + + * doc/plugin.texi (Building GCC plugins): Update to C++. + 2014-01-14 Kirill Yukhin * config/i386/avx512erintrin.h (_mm_rcp28_round_sd): New. diff --git a/gcc/doc/plugins.texi b/gcc/doc/plugins.texi index f1983808b06..a283a7162aa 100644 --- a/gcc/doc/plugins.texi +++ b/gcc/doc/plugins.texi @@ -465,18 +465,18 @@ integer numbers, so a plugin could ensure it is built for GCC 4.7 with The following GNU Makefile excerpt shows how to build a simple plugin: @smallexample -GCC=gcc -PLUGIN_SOURCE_FILES= plugin1.c plugin2.c -PLUGIN_OBJECT_FILES= $(patsubst %.c,%.o,$(PLUGIN_SOURCE_FILES)) -GCCPLUGINS_DIR:= $(shell $(GCC) -print-file-name=plugin) -CFLAGS+= -I$(GCCPLUGINS_DIR)/include -fPIC -O2 +HOST_GCC=g++ +TARGET_GCC=gcc +PLUGIN_SOURCE_FILES= plugin1.c plugin2.cc +GCCPLUGINS_DIR:= $(shell $(TARGET_GCC) -print-file-name=plugin) +CXXFLAGS+= -I$(GCCPLUGINS_DIR)/include -fPIC -fno-rtti -O2 -plugin.so: $(PLUGIN_OBJECT_FILES) - $(GCC) -shared $^ -o $@@ +plugin.so: $(PLUGIN_SOURCE_FILES) + $(HOST_GCC) -shared $(CXXFLAGS) $^ -o $@@ @end smallexample -A single source file plugin may be built with @code{gcc -I`gcc --print-file-name=plugin`/include -fPIC -shared -O2 plugin.c -o +A single source file plugin may be built with @code{g++ -I`gcc +-print-file-name=plugin`/include -fPIC -shared -fno-rtti -O2 plugin.c -o plugin.so}, using backquote shell syntax to query the @file{plugin} directory.