* [patch] remove more GCJ references
@ 2016-11-15 10:55 Matthias Klose
2016-11-15 15:52 ` Jeff Law
0 siblings, 1 reply; 7+ messages in thread
From: Matthias Klose @ 2016-11-15 10:55 UTC (permalink / raw)
To: GCC Patches, GCJ-patches
[-- Attachment #1: Type: text/plain, Size: 667 bytes --]
This patch removes some references to gcj in the top level and config
directories and in the gcc documentation. The change to the config directory
requires regenerating aclocal.m4 and configure in each sub directory.
Ok for the trunk?
Matthias
<toplevel>
2016-11-14 Matthias Klose <doko@ubuntu.com>
* config-ml.in: Remove references to GCJ.
* configure.ac: Likewise.
* configure: Regenerate.
config/
2016-11-14 Matthias Klose <doko@ubuntu.com>
multi.m4: Don't set GCJ.
gcc/
2016-11-14 Matthias Klose <doko@ubuntu.com>
* doc/install.texi: Remove references to gcj/libjava.
* doc/invoke.texi: Likewise.
[-- Attachment #2: remove-gcj-refs.diff --]
[-- Type: text/x-diff, Size: 14925 bytes --]
<toplevel>
2016-11-14 Matthias Klose <doko@ubuntu.com>
* config-ml.in: Remove references to GCJ.
* configure.ac: Likewise.
* configure: Regenerate.
config/
2016-11-14 Matthias Klose <doko@ubuntu.com>
multi.m4: Don't set GCJ.
gcc/
2016-11-14 Matthias Klose <doko@ubuntu.com>
* doc/install.texi: Remove references to gcj/libjava.
* doc/invoke.texi: Likewise.
Index: config/multi.m4
===================================================================
--- config/multi.m4 (revision 242381)
+++ config/multi.m4 (working copy)
@@ -64,5 +64,4 @@
CONFIG_SHELL=${CONFIG_SHELL-/bin/sh}
CC="$CC"
CXX="$CXX"
-GFORTRAN="$GFORTRAN"
-GCJ="$GCJ"])])dnl
+GFORTRAN="$GFORTRAN"])])dnl
Index: config-ml.in
===================================================================
--- config-ml.in (revision 242381)
+++ config-ml.in (working copy)
@@ -511,7 +511,6 @@
ADAFLAGS="$(ADAFLAGS) $${flags}" \
prefix="$(prefix)" \
exec_prefix="$(exec_prefix)" \
- GCJFLAGS="$(GCJFLAGS) $${flags}" \
GOCFLAGS="$(GOCFLAGS) $${flags}" \
CXXFLAGS="$(CXXFLAGS) $${flags}" \
LIBCFLAGS="$(LIBCFLAGS) $${flags}" \
@@ -746,13 +745,12 @@
break
fi
done
- ml_config_env='CC="${CC_}$flags" CXX="${CXX_}$flags" F77="${F77_}$flags" GCJ="${GCJ_}$flags" GFORTRAN="${GFORTRAN_}$flags" GOC="${GOC_}$flags"'
+ ml_config_env='CC="${CC_}$flags" CXX="${CXX_}$flags" F77="${F77_}$flags" GFORTRAN="${GFORTRAN_}$flags" GOC="${GOC_}$flags"'
if [ "${with_target_subdir}" = "." ]; then
CC_=$CC' '
CXX_=$CXX' '
F77_=$F77' '
- GCJ_=$GCJ' '
GFORTRAN_=$GFORTRAN' '
GOC_=$GOC' '
else
@@ -795,18 +793,6 @@
esac
done
- GCJ_=
- for arg in ${GCJ}; do
- case $arg in
- -[BIL]"${ML_POPDIR}"/*)
- GCJ_="${GCJ_}"`echo "X${arg}" | sed -n "s/X\\(-[BIL]${popdir_rx}\\).*/\\1/p"`/${ml_dir}`echo "X${arg}" | sed -n "s/X-[BIL]${popdir_rx}\\(.*\\)/\\1/p"`' ' ;;
- "${ML_POPDIR}"/*)
- GCJ_="${GCJ_}"`echo "X${arg}" | sed -n "s/X\\(${popdir_rx}\\).*/\\1/p"`/${ml_dir}`echo "X${arg}" | sed -n "s/X${popdir_rx}\\(.*\\)/\\1/p"`' ' ;;
- *)
- GCJ_="${GCJ_}${arg} " ;;
- esac
- done
-
GFORTRAN_=
for arg in ${GFORTRAN}; do
case $arg in
Index: configure.ac
===================================================================
--- configure.ac (revision 242381)
+++ configure.ac (working copy)
@@ -1256,7 +1256,6 @@
AS_FOR_BUILD=${AS_FOR_BUILD-as}
CC_FOR_BUILD=${CC_FOR_BUILD-gcc}
CXX_FOR_BUILD=${CXX_FOR_BUILD-g++}
- GCJ_FOR_BUILD=${GCJ_FOR_BUILD-gcj}
GFORTRAN_FOR_BUILD=${GFORTRAN_FOR_BUILD-gfortran}
GOC_FOR_BUILD=${GOC_FOR_BUILD-gccgo}
DLLTOOL_FOR_BUILD=${DLLTOOL_FOR_BUILD-dlltool}
@@ -1270,7 +1269,6 @@
AS_FOR_BUILD="\$(AS)"
CC_FOR_BUILD="\$(CC)"
CXX_FOR_BUILD="\$(CXX)"
- GCJ_FOR_BUILD="\$(GCJ)"
GFORTRAN_FOR_BUILD="\$(GFORTRAN)"
GOC_FOR_BUILD="\$(GOC)"
DLLTOOL_FOR_BUILD="\$(DLLTOOL)"
@@ -3183,7 +3181,6 @@
AC_SUBST(CXXFLAGS_FOR_BUILD)
AC_SUBST(CXX_FOR_BUILD)
AC_SUBST(DLLTOOL_FOR_BUILD)
-AC_SUBST(GCJ_FOR_BUILD)
AC_SUBST(GFORTRAN_FOR_BUILD)
AC_SUBST(GOC_FOR_BUILD)
AC_SUBST(LDFLAGS_FOR_BUILD)
@@ -3293,7 +3290,6 @@
NCN_STRICT_CHECK_TARGET_TOOLS(CC_FOR_TARGET, cc gcc)
NCN_STRICT_CHECK_TARGET_TOOLS(CXX_FOR_TARGET, c++ g++ cxx gxx)
NCN_STRICT_CHECK_TARGET_TOOLS(GCC_FOR_TARGET, gcc, ${CC_FOR_TARGET})
-NCN_STRICT_CHECK_TARGET_TOOLS(GCJ_FOR_TARGET, gcj)
NCN_STRICT_CHECK_TARGET_TOOLS(GFORTRAN_FOR_TARGET, gfortran)
NCN_STRICT_CHECK_TARGET_TOOLS(GOC_FOR_TARGET, gccgo)
Index: gcc/doc/install.texi
===================================================================
--- gcc/doc/install.texi (revision 242381)
+++ gcc/doc/install.texi (working copy)
@@ -338,10 +338,6 @@
Used by various scripts to generate some files included in SVN (mainly
Unicode-related and rarely changing) from source tables.
-@item @command{jar}, or InfoZIP (@command{zip} and @command{unzip})
-
-Necessary to build libgcj, the GCJ runtime.
-
@end table
Several support libraries are necessary to build GCC, some are required,
@@ -2139,240 +2135,6 @@
tools.
@end table
-@subheading Java-Specific Options
-
-The following option applies to the build of the Java front end.
-
-@table @code
-@item --disable-libgcj
-Specify that the run-time libraries
-used by GCJ should not be built. This is useful in case you intend
-to use GCJ with some other run-time, or you're going to install it
-separately, or it just happens not to build on your particular
-machine. In general, if the Java front end is enabled, the GCJ
-libraries will be enabled too, unless they're known to not work on
-the target platform. If GCJ is enabled but @samp{libgcj} isn't built, you
-may need to port it; in this case, before modifying the top-level
-@file{configure.ac} so that @samp{libgcj} is enabled by default on this platform,
-you may use @option{--enable-libgcj} to override the default.
-
-@end table
-
-The following options apply to building @samp{libgcj}.
-
-@subsubheading General Options
-
-@table @code
-@item --enable-java-maintainer-mode
-By default the @samp{libjava} build will not attempt to compile the
-@file{.java} source files to @file{.class}. Instead, it will use the
-@file{.class} files from the source tree. If you use this option you
-must have executables named @command{ecj1} and @command{gjavah} in your path
-for use by the build. You must use this option if you intend to
-modify any @file{.java} files in @file{libjava}.
-
-@item --with-java-home=@var{dirname}
-This @samp{libjava} option overrides the default value of the
-@samp{java.home} system property. It is also used to set
-@samp{sun.boot.class.path} to @file{@var{dirname}/lib/rt.jar}. By
-default @samp{java.home} is set to @file{@var{prefix}} and
-@samp{sun.boot.class.path} to
-@file{@var{datadir}/java/libgcj-@var{version}.jar}.
-
-@item --with-ecj-jar=@var{filename}
-This option can be used to specify the location of an external jar
-file containing the Eclipse Java compiler. A specially modified
-version of this compiler is used by @command{gcj} to parse
-@file{.java} source files. If this option is given, the
-@samp{libjava} build will create and install an @file{ecj1} executable
-which uses this jar file at runtime.
-
-If this option is not given, but an @file{ecj.jar} file is found in
-the topmost source tree at configure time, then the @samp{libgcj}
-build will create and install @file{ecj1}, and will also install the
-discovered @file{ecj.jar} into a suitable place in the install tree.
-
-If @file{ecj1} is not installed, then the user will have to supply one
-on his path in order for @command{gcj} to properly parse @file{.java}
-source files. A suitable jar is available from
-@uref{ftp://sourceware.org/pub/java/}.
-
-@item --disable-getenv-properties
-Don't set system properties from @env{GCJ_PROPERTIES}.
-
-@item --enable-hash-synchronization
-Use a global hash table for monitor locks. Ordinarily,
-@samp{libgcj}'s @samp{configure} script automatically makes
-the correct choice for this option for your platform. Only use
-this if you know you need the library to be configured differently.
-
-@item --enable-interpreter
-Enable the Java interpreter. The interpreter is automatically
-enabled by default on all platforms that support it. This option
-is really only useful if you want to disable the interpreter
-(using @option{--disable-interpreter}).
-
-@item --disable-java-net
-Disable java.net. This disables the native part of java.net only,
-using non-functional stubs for native method implementations.
-
-@item --disable-jvmpi
-Disable JVMPI support.
-
-@item --disable-libgcj-bc
-Disable BC ABI compilation of certain parts of libgcj. By default,
-some portions of libgcj are compiled with @option{-findirect-dispatch}
-and @option{-fno-indirect-classes}, allowing them to be overridden at
-run-time.
-
-If @option{--disable-libgcj-bc} is specified, libgcj is built without
-these options. This allows the compile-time linker to resolve
-dependencies when statically linking to libgcj. However it makes it
-impossible to override the affected portions of libgcj at run-time.
-
-@item --enable-reduced-reflection
-Build most of libgcj with @option{-freduced-reflection}. This reduces
-the size of libgcj at the expense of not being able to do accurate
-reflection on the classes it contains. This option is safe if you
-know that code using libgcj will never use reflection on the standard
-runtime classes in libgcj (including using serialization, RMI or CORBA).
-
-@item --with-ecos
-Enable runtime eCos target support.
-
-@item --without-libffi
-Don't use @samp{libffi}. This will disable the interpreter and JNI
-support as well, as these require @samp{libffi} to work.
-
-@item --enable-libgcj-debug
-Enable runtime debugging code.
-
-@item --enable-libgcj-multifile
-If specified, causes all @file{.java} source files to be
-compiled into @file{.class} files in one invocation of
-@samp{gcj}. This can speed up build time, but is more
-resource-intensive. If this option is unspecified or
-disabled, @samp{gcj} is invoked once for each @file{.java}
-file to compile into a @file{.class} file.
-
-@item --with-libiconv-prefix=DIR
-Search for libiconv in @file{DIR/include} and @file{DIR/lib}.
-
-@item --enable-sjlj-exceptions
-Force use of the @code{setjmp}/@code{longjmp}-based scheme for exceptions.
-@samp{configure} ordinarily picks the correct value based on the platform.
-Only use this option if you are sure you need a different setting.
-
-@item --with-system-zlib
-Use installed @samp{zlib} rather than that included with GCC@.
-
-@item --with-win32-nlsapi=ansi, unicows or unicode
-Indicates how MinGW @samp{libgcj} translates between UNICODE
-characters and the Win32 API@.
-
-@item --enable-java-home
-If enabled, this creates a JPackage compatible SDK environment during install.
-Note that if --enable-java-home is used, --with-arch-directory=ARCH must also
-be specified.
-
-@item --with-arch-directory=ARCH
-Specifies the name to use for the @file{jre/lib/ARCH} directory in the SDK
-environment created when --enable-java-home is passed. Typical names for this
-directory include i386, amd64, ia64, etc.
-
-@item --with-os-directory=DIR
-Specifies the OS directory for the SDK include directory. This is set to auto
-detect, and is typically 'linux'.
-
-@item --with-origin-name=NAME
-Specifies the JPackage origin name. This defaults to the 'gcj' in
-java-1.5.0-gcj.
-
-@item --with-arch-suffix=SUFFIX
-Specifies the suffix for the sdk directory. Defaults to the empty string.
-Examples include '.x86_64' in 'java-1.5.0-gcj-1.5.0.0.x86_64'.
-
-@item --with-jvm-root-dir=DIR
-Specifies where to install the SDK. Default is $(prefix)/lib/jvm.
-
-@item --with-jvm-jar-dir=DIR
-Specifies where to install jars. Default is $(prefix)/lib/jvm-exports.
-
-@item --with-python-dir=DIR
-Specifies where to install the Python modules used for aot-compile. DIR should
-not include the prefix used in installation. For example, if the Python modules
-are to be installed in /usr/lib/python2.5/site-packages, then
---with-python-dir=/lib/python2.5/site-packages should be passed. If this is
-not specified, then the Python modules are installed in $(prefix)/share/python.
-
-@item --enable-aot-compile-rpm
-Adds aot-compile-rpm to the list of installed scripts.
-
-@item --enable-browser-plugin
-Build the gcjwebplugin web browser plugin.
-
-@item --enable-static-libjava
-Build static libraries in libjava. The default is to only build shared
-libraries.
-
-@table @code
-@item ansi
-Use the single-byte @code{char} and the Win32 A functions natively,
-translating to and from UNICODE when using these functions. If
-unspecified, this is the default.
-
-@item unicows
-Use the @code{WCHAR} and Win32 W functions natively. Adds
-@code{-lunicows} to @file{libgcj.spec} to link with @samp{libunicows}.
-@file{unicows.dll} needs to be deployed on Microsoft Windows 9X machines
-running built executables. @file{libunicows.a}, an open-source
-import library around Microsoft's @code{unicows.dll}, is obtained from
-@uref{http://libunicows.sourceforge.net/}, which also gives details
-on getting @file{unicows.dll} from Microsoft.
-
-@item unicode
-Use the @code{WCHAR} and Win32 W functions natively. Does @emph{not}
-add @code{-lunicows} to @file{libgcj.spec}. The built executables will
-only run on Microsoft Windows NT and above.
-@end table
-@end table
-
-@subsubheading AWT-Specific Options
-
-@table @code
-@item --with-x
-Use the X Window System.
-
-@item --enable-java-awt=PEER(S)
-Specifies the AWT peer library or libraries to build alongside
-@samp{libgcj}. If this option is unspecified or disabled, AWT
-will be non-functional. Current valid values are @option{gtk} and
-@option{xlib}. Multiple libraries should be separated by a
-comma (i.e.@: @option{--enable-java-awt=gtk,xlib}).
-
-@item --enable-gtk-cairo
-Build the cairo Graphics2D implementation on GTK@.
-
-@item --enable-java-gc=TYPE
-Choose garbage collector. Defaults to @option{boehm} if unspecified.
-
-@item --disable-gtktest
-Do not try to compile and run a test GTK+ program.
-
-@item --disable-glibtest
-Do not try to compile and run a test GLIB program.
-
-@item --with-libart-prefix=PFX
-Prefix where libart is installed (optional).
-
-@item --with-libart-exec-prefix=PFX
-Exec prefix where libart is installed (optional).
-
-@item --disable-libarttest
-Do not try to compile and run a test libart program.
-
-@end table
-
@subsubheading Overriding @command{configure} test results
Sometimes, it might be necessary to override the result of some
Index: gcc/doc/invoke.texi
===================================================================
--- gcc/doc/invoke.texi (revision 242381)
+++ gcc/doc/invoke.texi (working copy)
@@ -11438,10 +11438,9 @@
across different shared libraries. In that case, each of the libraries
as well as the application itself should use the shared @file{libgcc}.
-Therefore, the G++ and GCJ drivers automatically add
-@option{-shared-libgcc} whenever you build a shared library or a main
-executable, because C++ and Java programs typically use exceptions, so
-this is the right thing to do.
+Therefore, the G++ and driver automatically adds @option{-shared-libgcc}
+ whenever you build a shared library or a main executable, because C++
+ programs typically use exceptions, so this is the right thing to do.
If, instead, you use the GCC driver to create shared libraries, you may
find that they are not always linked with the shared @file{libgcc}.
@@ -11455,7 +11454,7 @@
costs at library load time.
However, if a library or main executable is supposed to throw or catch
-exceptions, you must link it using the G++ or GCJ driver, as appropriate
+exceptions, you must link it using the G++ driver, as appropriate
for the languages used in the program, or using the option
@option{-shared-libgcc}, such that it is linked with the shared
@file{libgcc}.
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [patch] remove more GCJ references
2016-11-15 10:55 [patch] remove more GCJ references Matthias Klose
@ 2016-11-15 15:52 ` Jeff Law
2016-11-15 17:28 ` Matthias Klose
2016-11-15 20:41 ` Matthias Klose
0 siblings, 2 replies; 7+ messages in thread
From: Jeff Law @ 2016-11-15 15:52 UTC (permalink / raw)
To: Matthias Klose, GCC Patches, GCJ-patches
On 11/15/2016 03:55 AM, Matthias Klose wrote:
> This patch removes some references to gcj in the top level and config
> directories and in the gcc documentation. The change to the config directory
> requires regenerating aclocal.m4 and configure in each sub directory.
>
> Ok for the trunk?
>
> Matthias
>
> <toplevel>
>
> 2016-11-14 Matthias Klose <doko@ubuntu.com>
>
> * config-ml.in: Remove references to GCJ.
> * configure.ac: Likewise.
> * configure: Regenerate.
>
> config/
>
> 2016-11-14 Matthias Klose <doko@ubuntu.com>
>
> multi.m4: Don't set GCJ.
>
> gcc/
>
> 2016-11-14 Matthias Klose <doko@ubuntu.com>
>
> * doc/install.texi: Remove references to gcj/libjava.
> * doc/invoke.texi: Likewise.
>
OK.
jeff
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [patch] remove more GCJ references
2016-11-15 15:52 ` Jeff Law
@ 2016-11-15 17:28 ` Matthias Klose
2016-11-15 20:41 ` Matthias Klose
1 sibling, 0 replies; 7+ messages in thread
From: Matthias Klose @ 2016-11-15 17:28 UTC (permalink / raw)
To: GCC Patches, GCJ-patches
[-- Attachment #1: Type: text/plain, Size: 1130 bytes --]
On 15.11.2016 16:52, Jeff Law wrote:
> On 11/15/2016 03:55 AM, Matthias Klose wrote:
>> This patch removes some references to gcj in the top level and config
>> directories and in the gcc documentation. The change to the config directory
>> requires regenerating aclocal.m4 and configure in each sub directory.
>>
>> Ok for the trunk?
>>
>> Matthias
>>
>> <toplevel>
>>
>> 2016-11-14 Matthias Klose <doko@ubuntu.com>
>>
>> * config-ml.in: Remove references to GCJ.
>> * configure.ac: Likewise.
>> * configure: Regenerate.
>>
>> config/
>>
>> 2016-11-14 Matthias Klose <doko@ubuntu.com>
>>
>> multi.m4: Don't set GCJ.
>>
>> gcc/
>>
>> 2016-11-14 Matthias Klose <doko@ubuntu.com>
>>
>> * doc/install.texi: Remove references to gcj/libjava.
>> * doc/invoke.texi: Likewise.
>>
> OK.
> jeff
- committed.
- restored the accidentally regenerated files in libiberty.
- forgot to commit some files, now committed.
2016-11-15 Matthias Klose <doko@ubuntu.com>
* Makefile.def: Remove references to GCJ.
* Makefile.tpl: Likewise.
* Makefile.in: Regenerate.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: remove-gcj.diff --]
[-- Type: text/x-diff; name="remove-gcj.diff", Size: 3220 bytes --]
2016-11-15 Matthias Klose <doko@ubuntu.com>
* Makefile.def: Remove references to GCJ.
* Makefile.tpl: Likewise.
* Makefile.in: Regenerate.
Index: Makefile.def
===================================================================
--- Makefile.def (revision 242433)
+++ Makefile.def (working copy)
@@ -280,7 +280,6 @@
flags_to_pass = { flag= CXXFLAGS_FOR_TARGET ; };
flags_to_pass = { flag= DLLTOOL_FOR_TARGET ; };
flags_to_pass = { flag= FLAGS_FOR_TARGET ; };
-flags_to_pass = { flag= GCJ_FOR_TARGET ; };
flags_to_pass = { flag= GFORTRAN_FOR_TARGET ; };
flags_to_pass = { flag= GOC_FOR_TARGET ; };
flags_to_pass = { flag= GOCFLAGS_FOR_TARGET ; };
Index: Makefile.tpl
===================================================================
--- Makefile.tpl (revision 242433)
+++ Makefile.tpl (working copy)
@@ -156,7 +156,6 @@
CONFIG_SHELL="$(SHELL)"; export CONFIG_SHELL; \
CXX="$(CXX_FOR_BUILD)"; export CXX; \
CXXFLAGS="$(CXXFLAGS_FOR_BUILD)"; export CXXFLAGS; \
- GCJ="$(GCJ_FOR_BUILD)"; export GCJ; \
GFORTRAN="$(GFORTRAN_FOR_BUILD)"; export GFORTRAN; \
GOC="$(GOC_FOR_BUILD)"; export GOC; \
GOCFLAGS="$(GOCFLAGS_FOR_BUILD)"; export GOCFLAGS; \
@@ -194,7 +193,6 @@
CONFIG_SHELL="$(SHELL)"; export CONFIG_SHELL; \
CXX="$(CXX)"; export CXX; \
CXXFLAGS="$(CXXFLAGS)"; export CXXFLAGS; \
- GCJ="$(GCJ)"; export GCJ; \
GFORTRAN="$(GFORTRAN)"; export GFORTRAN; \
GOC="$(GOC)"; export GOC; \
AR="$(AR)"; export AR; \
@@ -282,7 +280,6 @@
CONFIG_SHELL="$(SHELL)"; export CONFIG_SHELL; \
CPPFLAGS="$(CPPFLAGS_FOR_TARGET)"; export CPPFLAGS; \
CXXFLAGS="$(CXXFLAGS_FOR_TARGET)"; export CXXFLAGS; \
- GCJ="$(GCJ_FOR_TARGET) $(XGCC_FLAGS_FOR_TARGET) $$TFLAGS"; export GCJ; \
GFORTRAN="$(GFORTRAN_FOR_TARGET) $(XGCC_FLAGS_FOR_TARGET) $$TFLAGS"; export GFORTRAN; \
GOC="$(GOC_FOR_TARGET) $(XGCC_FLAGS_FOR_TARGET) $$TFLAGS"; export GOC; \
DLLTOOL="$(DLLTOOL_FOR_TARGET)"; export DLLTOOL; \
@@ -348,7 +345,6 @@
CXXFLAGS_FOR_BUILD = @CXXFLAGS_FOR_BUILD@
CXX_FOR_BUILD = @CXX_FOR_BUILD@
DLLTOOL_FOR_BUILD = @DLLTOOL_FOR_BUILD@
-GCJ_FOR_BUILD = @GCJ_FOR_BUILD@
GFORTRAN_FOR_BUILD = @GFORTRAN_FOR_BUILD@
GOC_FOR_BUILD = @GOC_FOR_BUILD@
LDFLAGS_FOR_BUILD = @LDFLAGS_FOR_BUILD@
@@ -488,7 +484,6 @@
GCC_FOR_TARGET=$(STAGE_CC_WRAPPER) @GCC_FOR_TARGET@
CXX_FOR_TARGET=$(STAGE_CC_WRAPPER) @CXX_FOR_TARGET@
RAW_CXX_FOR_TARGET=$(STAGE_CC_WRAPPER) @RAW_CXX_FOR_TARGET@
-GCJ_FOR_TARGET=$(STAGE_CC_WRAPPER) @GCJ_FOR_TARGET@
GFORTRAN_FOR_TARGET=$(STAGE_CC_WRAPPER) @GFORTRAN_FOR_TARGET@
GOC_FOR_TARGET=$(STAGE_CC_WRAPPER) @GOC_FOR_TARGET@
DLLTOOL_FOR_TARGET=@DLLTOOL_FOR_TARGET@
@@ -614,7 +609,6 @@
'CC=$(CC)' \
'CXX=$(CXX)' \
'DLLTOOL=$(DLLTOOL)' \
- 'GCJ=$(GCJ)' \
'GFORTRAN=$(GFORTRAN)' \
'GOC=$(GOC)' \
'LD=$(LD)' \
@@ -670,7 +664,6 @@
$$(XGCC_FLAGS_FOR_TARGET) $$(TFLAGS)' \
'CXXFLAGS=$$(CXXFLAGS_FOR_TARGET)' \
'DLLTOOL=$$(DLLTOOL_FOR_TARGET)' \
- 'GCJ=$$(GCJ_FOR_TARGET) $$(XGCC_FLAGS_FOR_TARGET) $$(TFLAGS)' \
'GFORTRAN=$$(GFORTRAN_FOR_TARGET) $$(XGCC_FLAGS_FOR_TARGET) $$(TFLAGS)' \
'GOC=$$(GOC_FOR_TARGET) $$(XGCC_FLAGS_FOR_TARGET) $$(TFLAGS)' \
'GOCFLAGS=$$(GOCFLAGS_FOR_TARGET)' \
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [patch] remove more GCJ references
2016-11-15 15:52 ` Jeff Law
2016-11-15 17:28 ` Matthias Klose
@ 2016-11-15 20:41 ` Matthias Klose
2016-11-15 21:00 ` Matthias Klose
1 sibling, 1 reply; 7+ messages in thread
From: Matthias Klose @ 2016-11-15 20:41 UTC (permalink / raw)
To: GCC Patches, GCJ-patches
[-- Attachment #1: Type: text/plain, Size: 1099 bytes --]
On 15.11.2016 16:52, Jeff Law wrote:
> On 11/15/2016 03:55 AM, Matthias Klose wrote:
>> This patch removes some references to gcj in the top level and config
>> directories and in the gcc documentation. The change to the config directory
>> requires regenerating aclocal.m4 and configure in each sub directory.
>>
>> Ok for the trunk?
>>
>> Matthias
>>
>> <toplevel>
>>
>> 2016-11-14 Matthias Klose <doko@ubuntu.com>
>>
>> * config-ml.in: Remove references to GCJ.
>> * configure.ac: Likewise.
>> * configure: Regenerate.
>>
>> config/
>>
>> 2016-11-14 Matthias Klose <doko@ubuntu.com>
>>
>> multi.m4: Don't set GCJ.
>>
>> gcc/
>>
>> 2016-11-14 Matthias Klose <doko@ubuntu.com>
>>
>> * doc/install.texi: Remove references to gcj/libjava.
>> * doc/invoke.texi: Likewise.
>>
> OK.
> jeff
I was missing more references in the documentation, committing the remaining
changes as obvious:
gcc/
2016-11-15 Matthias Klose <doko@ubuntu.com>
* doc/install.texi: Remove references to java/libjava.
* doc/sourcebuild.texi: Likewise.
[-- Attachment #2: remove-gcj-doc2.diff --]
[-- Type: text/x-diff, Size: 13088 bytes --]
gcc/
2016-11-15 Matthias Klose <doko@ubuntu.com>
* doc/install.texi: Remove references to java/libjava.
* doc/sourcebuild.texi: Likewise.
Index: gcc/doc/install.texi
===================================================================
--- gcc/doc/install.texi (revision 242453)
+++ gcc/doc/install.texi (working copy)
@@ -498,28 +498,6 @@
Necessary when applying patches, created with @command{diff}, to one's
own sources.
-@item ecj1
-@itemx gjavah
-
-If you wish to modify @file{.java} files in libjava, you will need to
-configure with @option{--enable-java-maintainer-mode}, and you will need
-to have executables named @command{ecj1} and @command{gjavah} in your path.
-The @command{ecj1} executable should run the Eclipse Java compiler via
-the GCC-specific entry point. You can download a suitable jar from
-@uref{ftp://sourceware.org/pub/java/}, or by running the script
-@command{contrib/download_ecj}.
-
-@item antlr.jar version 2.7.1 (or later)
-@itemx antlr binary
-
-If you wish to build the @command{gjdoc} binary in libjava, you will
-need to have an @file{antlr.jar} library available. The library is
-searched for in system locations but can be specified with
-@option{--with-antlr-jar=} instead. When configuring with
-@option{--enable-java-maintainer-mode}, you will need to have one of
-the executables named @command{cantlr}, @command{runantlr} or
-@command{antlr} in your path.
-
@end table
@html
@@ -550,9 +528,9 @@
Please refer to the @uref{http://gcc.gnu.org/releases.html,,releases web page}
for information on how to obtain GCC@.
-The source distribution includes the C, C++, Objective-C, Fortran, Java,
+The source distribution includes the C, C++, Objective-C, Fortran,
and Ada (in the case of GCC 3.1 and later) compilers, as well as
-runtime libraries for C++, Objective-C, Fortran, and Java.
+runtime libraries for C++, Objective-C, and Fortran.
For previous versions these were downloadable as separate components such
as the core GCC distribution, which included the C language front end and
shared components, and language-specific distributions including the
@@ -934,7 +912,7 @@
will be built. Package names currently recognized in the GCC tree are
@samp{libgcc} (also known as @samp{gcc}), @samp{libstdc++} (not
@samp{libstdc++-v3}), @samp{libffi}, @samp{zlib}, @samp{boehm-gc},
-@samp{ada}, @samp{libada}, @samp{libjava}, @samp{libgo}, and @samp{libobjc}.
+@samp{ada}, @samp{libada}, @samp{libgo}, and @samp{libobjc}.
Note @samp{libiberty} does not support shared libraries at all.
Use @option{--disable-shared} to build only static libraries. Note that
@@ -1178,7 +1156,7 @@
@item --enable-threads
Specify that the target
supports threads. This affects the Objective-C compiler and runtime
-library, and exception handling for other languages like C++ and Java.
+library, and exception handling for other languages like C++.
On some systems, this is the default.
In general, the best (and, in many cases, the only known) threading
@@ -1195,7 +1173,7 @@
Specify that
@var{lib} is the thread support library. This affects the Objective-C
compiler and runtime library, and exception handling for other languages
-like C++ and Java. The possibilities for @var{lib} are:
+like C++. The possibilities for @var{lib} are:
@table @code
@item aix
@@ -1443,7 +1421,7 @@
@option{--with-gxx-include-dir=@var{dirname}}. Using this option is
particularly useful if you intend to use several versions of GCC in
parallel. This is currently supported by @samp{libgfortran},
-@samp{libjava}, @samp{libstdc++}, and @samp{libobjc}.
+@samp{libstdc++}, and @samp{libobjc}.
@item @anchor{WithAixSoname}--with-aix-soname=@samp{aix}, @samp{svr4} or @samp{both}
Traditional AIX shared library versioning (versioned @code{Shared Object}
@@ -1563,7 +1541,7 @@
@end smallexample
Currently, you can use any of the following:
@code{all}, @code{ada}, @code{c}, @code{c++}, @code{fortran},
-@code{go}, @code{java}, @code{jit}, @code{lto}, @code{objc}, @code{obj-c++}.
+@code{go}, @code{jit}, @code{lto}, @code{objc}, @code{obj-c++}.
Building the Ada compiler has special requirements, see below.
If you do not pass this flag, or specify the option @code{all}, then all
default languages available in the @file{gcc} sub-tree will be configured.
@@ -2415,13 +2393,6 @@
cross compiler. The installed native compiler needs to be GCC version
2.95 or later.
-If the cross compiler is to be built with support for the Java
-programming language and the ability to compile .java source files is
-desired, the installed native compiler used to build the cross
-compiler needs to be the same GCC version as the cross compiler. In
-addition the cross compiler needs to be configured with
-@option{--with-ecj-jar=@dots{}}.
-
Assuming you have already installed a native copy of GCC and configured
your cross compiler, issue the command @command{make}, which performs the
following steps:
@@ -2624,7 +2595,7 @@
In order to run sets of tests selectively, there are targets
@samp{make check-gcc} and language specific @samp{make check-c},
-@samp{make check-c++}, @samp{make check-fortran}, @samp{make check-java},
+@samp{make check-c++}, @samp{make check-fortran},
@samp{make check-ada}, @samp{make check-objc}, @samp{make check-obj-c++},
@samp{make check-lto}
in the @file{gcc} subdirectory of the object directory. You can also
@@ -2722,19 +2693,6 @@
typing @command{echo} before the example given here.)
-@section Additional testing for Java Class Libraries
-
-The Java runtime tests can be executed via @samp{make check}
-in the @file{@var{target}/libjava/testsuite} directory in
-the build tree.
-
-The @uref{http://sourceware.org/mauve/,,Mauve Project} provides
-a suite of tests for the Java Class Libraries. This suite can be run
-as part of libgcj testing by placing the Mauve tree within the libjava
-testsuite at @file{libjava/testsuite/libjava.mauve/mauve}, or by
-specifying the location of that tree when invoking @samp{make}, as in
-@samp{make MAUVEDIR=~/mauve check}.
-
@section How to interpret test results
The result of running the testsuite are various @file{*.sum} and @file{*.log}
@@ -2819,7 +2777,7 @@
@file{/usr/local} by default). (If you specified @option{--bindir},
that directory will be used instead; otherwise, if you specified
@option{--exec-prefix}, @file{@var{exec-prefix}/bin} will be used.)
-Headers for the C++ and Java libraries are installed in
+Headers for the C++ library are installed in
@file{@var{prefix}/include}; libraries in @file{@var{libdir}}
(normally @file{@var{prefix}/lib}); internal parts of the compiler in
@file{@var{libdir}/gcc} and @file{@var{libexecdir}/gcc}; documentation
@@ -3468,9 +3426,9 @@
with this release of GCC@. Bootstrapping against the latest GNU
binutils and/or the version found in @file{/usr/ports/devel/binutils} has
been known to enable additional features and improve overall testsuite
-results. However, it is currently known that boehm-gc (which itself
-is required for java) may not configure properly on FreeBSD prior to
-the FreeBSD 7.0 release with GNU binutils after 2.16.1.
+results. However, it is currently known that boehm-gc may not configure
+properly on FreeBSD prior to the FreeBSD 7.0 release with GNU binutils
+after 2.16.1.
@html
<hr />
@@ -3568,8 +3526,7 @@
GCC 3.0 and up support HP-UX 11. GCC 2.95.x is not supported and cannot
be used to compile GCC 3.0 and up.
-The libffi and libjava libraries haven't been ported to 64-bit HP-UX@
-and don't build.
+The libffi library haven't been ported to 64-bit HP-UX@ and doesn't build.
Refer to @uref{binaries.html,,binaries} for information about obtaining
precompiled GCC binaries for HP-UX@. Precompiled binaries must be obtained
@@ -3582,11 +3539,7 @@
It is possible to build GCC 3.3 starting with the bundled HP compiler,
but the process requires several steps. GCC 3.3 can then be used to
-build later versions. The fastjar program contains ISO C code and
-can't be built with the HP bundled compiler. This problem can be
-avoided by not building the Java language. For example, use the
-@option{--enable-languages="c,c++,f77,objc"} option in your configure
-command.
+build later versions.
There are several possible approaches to building the distribution.
Binutils can be built first using the HP tools. Then, the GCC
@@ -4286,8 +4239,8 @@
@uref{binaries.html,,binaries page} for details.
The Solaris 2 @command{/bin/sh} will often fail to configure
-@samp{libstdc++-v3}, @samp{boehm-gc} or @samp{libjava}. We therefore
-recommend using the following initial sequence of commands
+@samp{libstdc++-v3}or @samp{boehm-gc}. We therefore recommend using the
+following initial sequence of commands
@smallexample
% CONFIG_SHELL=/bin/ksh
@@ -4351,9 +4304,6 @@
appropriate version is found. Solaris @command{c++filt} from the Solaris
Studio compilers does @emph{not} work.
-GNU @command{make} version 3.81 or later is required to build libjava
-with the Solaris linker.
-
Sun bug 4927647 sometimes causes random spurious testsuite failures
related to missing diagnostic output. This bug doesn't affect GCC
itself, rather it is a kernel bug triggered by the @command{expect}
Index: gcc/doc/sourcebuild.texi
===================================================================
--- gcc/doc/sourcebuild.texi (revision 242453)
+++ gcc/doc/sourcebuild.texi (working copy)
@@ -28,8 +28,8 @@
@table @file
@item boehm-gc
-The Boehm conservative garbage collector, used as part of the Java
-runtime library.
+The Boehm conservative garbage collector, optionally used as part of
+the ObjC runtime library when configured with @option{--enable-objc-gc}.
@item config
Autoconf macros and Makefile fragments used throughout the tree.
@@ -76,7 +76,7 @@
The Decimal Float support library.
@item libffi
-The @code{libffi} library, used as part of the Java runtime library.
+The @code{libffi} library, used as part of the Go runtime library.
@item libgcc
The GCC runtime library.
@@ -100,9 +100,6 @@
@item libitm
The runtime support library for transactional memory.
-@item libjava
-The Java runtime library.
-
@item libobjc
The Objective-C and Objective-C++ runtime library.
@@ -122,9 +119,8 @@
Scripts used by the @code{gccadmin} account on @code{gcc.gnu.org}.
@item zlib
-The @code{zlib} compression library, used by the Java front end, as
-part of the Java runtime library, and for compressing and uncompressing
-GCC's intermediate language in LTO object files.
+The @code{zlib} compression library, used for compressing and
+uncompressing GCC's intermediate language in LTO object files.
@end table
The build system in the top level directory, including how recursion
@@ -629,8 +625,8 @@
If defined, this variable lists (space-separated) language front ends
other than C that this front end requires to be enabled (with the
names given being their @code{language} settings). For example, the
-Java front end depends on the C++ front end, so sets
-@samp{lang_requires=c++}.
+Obj-C++ front end depends on the C++ and ObjC front ends, so sets
+@samp{lang_requires="objc c++"}.
@item subdir_requires
If defined, this variable lists (space-separated) front end directories
other than C that this front end requires to be present. For example,
@@ -862,7 +858,6 @@
* Test Directives:: Directives used within DejaGnu tests.
* Ada Tests:: The Ada language testsuites.
* C Tests:: The C language testsuites.
-* libgcj Tests:: The Java library testsuites.
* LTO Testing:: Support for testing link-time optimizations.
* gcov Testing:: Support for testing gcov.
* profopt Testing:: Support for testing profile-directed optimizations.
@@ -2600,29 +2595,6 @@
FIXME: merge in @file{testsuite/README.gcc} and discuss the format of
test cases and magic comments more.
-@node libgcj Tests
-@section The Java library testsuites.
-
-Runtime tests are executed via @samp{make check} in the
-@file{@var{target}/libjava/testsuite} directory in the build
-tree. Additional runtime tests can be checked into this testsuite.
-
-Regression testing of the core packages in libgcj is also covered by the
-Mauve testsuite. The @uref{http://sourceware.org/mauve/,,Mauve Project}
-develops tests for the Java Class Libraries. These tests are run as part
-of libgcj testing by placing the Mauve tree within the libjava testsuite
-sources at @file{libjava/testsuite/libjava.mauve/mauve}, or by specifying
-the location of that tree when invoking @samp{make}, as in
-@samp{make MAUVEDIR=~/mauve check}.
-
-To detect regressions, a mechanism in @file{mauve.exp} compares the
-failures for a test run against the list of expected failures in
-@file{libjava/testsuite/libjava.mauve/xfails} from the source hierarchy.
-Update this file when adding new failing tests to Mauve, or when fixing
-bugs in libgcj that had caused Mauve test failures.
-
-We encourage developers to contribute test cases to Mauve.
-
@node LTO Testing
@section Support for testing link-time optimizations
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [patch] remove more GCJ references
2016-11-15 20:41 ` Matthias Klose
@ 2016-11-15 21:00 ` Matthias Klose
2016-11-15 22:04 ` Eric Gallager
0 siblings, 1 reply; 7+ messages in thread
From: Matthias Klose @ 2016-11-15 21:00 UTC (permalink / raw)
To: GCC Patches, GCJ-patches
[-- Attachment #1: Type: text/plain, Size: 1461 bytes --]
On 15.11.2016 21:41, Matthias Klose wrote:
> On 15.11.2016 16:52, Jeff Law wrote:
>> On 11/15/2016 03:55 AM, Matthias Klose wrote:
>>> This patch removes some references to gcj in the top level and config
>>> directories and in the gcc documentation. The change to the config directory
>>> requires regenerating aclocal.m4 and configure in each sub directory.
>>>
>>> Ok for the trunk?
>>>
>>> Matthias
>>>
>>> <toplevel>
>>>
>>> 2016-11-14 Matthias Klose <doko@ubuntu.com>
>>>
>>> * config-ml.in: Remove references to GCJ.
>>> * configure.ac: Likewise.
>>> * configure: Regenerate.
>>>
>>> config/
>>>
>>> 2016-11-14 Matthias Klose <doko@ubuntu.com>
>>>
>>> multi.m4: Don't set GCJ.
>>>
>>> gcc/
>>>
>>> 2016-11-14 Matthias Klose <doko@ubuntu.com>
>>>
>>> * doc/install.texi: Remove references to gcj/libjava.
>>> * doc/invoke.texi: Likewise.
>>>
>> OK.
>> jeff
>
> I was missing more references in the documentation, committing the remaining
> changes as obvious:
>
> gcc/
> 2016-11-15 Matthias Klose <doko@ubuntu.com>
>
> * doc/install.texi: Remove references to java/libjava.
> * doc/sourcebuild.texi: Likewise.
and here are the remaining java reference in the user oriented documentation:
2016-11-15 Matthias Klose <doko@ubuntu.com>
* doc/install.texi: Remove references to java/libjava.
* doc/invoke.texi: Likewise.
* doc/standards.texi: Likewise.
[-- Attachment #2: remove-gcj-doc3.diff --]
[-- Type: text/x-diff, Size: 3423 bytes --]
gcc/
2016-11-15 Matthias Klose <doko@ubuntu.com>
* doc/install.texi: Remove references to java/libjava.
* doc/invoke.texi: Likewise.
* doc/standards.texi: Likewise.
Index: gcc/doc/install.texi
===================================================================
--- gcc/doc/install.texi (revision 242455)
+++ gcc/doc/install.texi (working copy)
@@ -4021,7 +4021,7 @@
it sorts relocations for REL targets (o32, o64, EABI). This can cause
bad code to be generated for simple C++ programs. Also the linker
from GNU binutils versions prior to 2.17 has a bug which causes the
-runtime linker stubs in very large programs, like @file{libgcj.so}, to
+runtime linker stubs in very large programs to
be incorrectly generated. GNU Binutils 2.18 and later (and snapshots
made after Nov. 9, 2006) should be free from both of these problems.
Index: gcc/doc/invoke.texi
===================================================================
--- gcc/doc/invoke.texi (revision 242455)
+++ gcc/doc/invoke.texi (working copy)
@@ -1316,12 +1316,6 @@
@item @var{file}.go
Go source code.
-@c FIXME: Descriptions of Java file types.
-@c @var{file}.java
-@c @var{file}.class
-@c @var{file}.zip
-@c @var{file}.jar
-
@item @var{file}.ads
Ada source code file that contains a library unit declaration (a
declaration of a package, subprogram, or generic, or a generic
@@ -1370,7 +1364,6 @@
ada
f77 f77-cpp-input f95 f95-cpp-input
go
-java
@end smallexample
@item -x none
@@ -3174,7 +3167,7 @@
@item -fobjc-exceptions
@opindex fobjc-exceptions
Enable syntactic support for structured exception handling in
-Objective-C, similar to what is offered by C++ and Java. This option
+Objective-C, similar to what is offered by C++. This option
is required to use the Objective-C keywords @code{@@try},
@code{@@throw}, @code{@@catch}, @code{@@finally} and
@code{@@synchronized}. This option is available with both the GNU
@@ -10800,7 +10793,7 @@
@opindex fbounds-check
For front ends that support it, generate additional code to check that
indices used to access arrays are within the declared range. This is
-currently only supported by the Java and Fortran front ends, where
+currently only supported by the Fortran front end, where
this option defaults to true and false respectively.
@item -fcheck-pointer-bounds
@@ -11861,8 +11854,7 @@
This option instructs the compiler to assume that signed arithmetic
overflow of addition, subtraction and multiplication wraps around
using twos-complement representation. This flag enables some optimizations
-and disables others. This option is enabled by default for the Java
-front end, as required by the Java language specification.
+and disables others.
The options @option{-ftrapv} and @option{-fwrapv} override each other, so using
@option{-ftrapv} @option{-fwrapv} on the command-line results in
@option{-fwrapv} being effective. Note that only active options override, so
Index: gcc/doc/standards.texi
===================================================================
--- gcc/doc/standards.texi (revision 242455)
+++ gcc/doc/standards.texi (working copy)
@@ -315,6 +315,3 @@
@xref{Standards,,Standards, gfortran, The GNU Fortran Compiler}, for details
of standards supported by GNU Fortran.
-
-@xref{Compatibility,,Compatibility with the Java Platform, gcj, GNU gcj},
-for details of compatibility between @command{gcj} and the Java Platform.
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [patch] remove more GCJ references
2016-11-15 21:00 ` Matthias Klose
@ 2016-11-15 22:04 ` Eric Gallager
2016-11-15 23:43 ` Matthias Klose
0 siblings, 1 reply; 7+ messages in thread
From: Eric Gallager @ 2016-11-15 22:04 UTC (permalink / raw)
To: Matthias Klose; +Cc: GCC Patches, GCJ-patches
On 11/15/16, Matthias Klose <doko@ubuntu.com> wrote:
> On 15.11.2016 21:41, Matthias Klose wrote:
>> On 15.11.2016 16:52, Jeff Law wrote:
>>> On 11/15/2016 03:55 AM, Matthias Klose wrote:
>>>> This patch removes some references to gcj in the top level and config
>>>> directories and in the gcc documentation. The change to the config
>>>> directory requires regenerating aclocal.m4 and configure in each sub
>>>> directory.
>>>>
>>>> Ok for the trunk?
>>>>
>>>> Matthias
>>>>
>>>> <toplevel>
>>>>
>>>> 2016-11-14 Matthias Klose <doko@ubuntu.com>
>>>>
>>>> * config-ml.in: Remove references to GCJ.
>>>> * configure.ac: Likewise.
>>>> * configure: Regenerate.
>>>>
>>>> config/
>>>>
>>>> 2016-11-14 Matthias Klose <doko@ubuntu.com>
>>>>
>>>> multi.m4: Don't set GCJ.
>>>>
>>>> gcc/
>>>>
>>>> 2016-11-14 Matthias Klose <doko@ubuntu.com>
>>>>
>>>> * doc/install.texi: Remove references to gcj/libjava.
>>>> * doc/invoke.texi: Likewise.
>>>>
>>> OK.
>>> jeff
>>
>> I was missing more references in the documentation, committing the
>> remaining changes as obvious:
>>
>> gcc/
>> 2016-11-15 Matthias Klose <doko@ubuntu.com>
>>
>> * doc/install.texi: Remove references to java/libjava.
>> * doc/sourcebuild.texi: Likewise.
>
> and here are the remaining java reference in the user oriented
> documentation:
>
> 2016-11-15 Matthias Klose <doko@ubuntu.com>
>
> * doc/install.texi: Remove references to java/libjava.
> * doc/invoke.texi: Likewise.
> * doc/standards.texi: Likewise.
>
> Index: gcc/doc/install.texi
> ===================================================================
> --- gcc/doc/install.texi (revision 242455)
> +++ gcc/doc/install.texi (working copy)
> @@ -4021,7 +4021,7 @@
> it sorts relocations for REL targets (o32, o64, EABI). This can cause
> bad code to be generated for simple C++ programs. Also the linker
> from GNU binutils versions prior to 2.17 has a bug which causes the
> -runtime linker stubs in very large programs, like @file{libgcj.so}, to
> +runtime linker stubs in very large programs to
> be incorrectly generated. GNU Binutils 2.18 and later (and snapshots
> made after Nov. 9, 2006) should be free from both of these problems.
>
> Index: gcc/doc/invoke.texi
> ===================================================================
> --- gcc/doc/invoke.texi (revision 242455)
> +++ gcc/doc/invoke.texi (working copy)
> @@ -1316,12 +1316,6 @@
> @item @var{file}.go
> Go source code.
>
> -@c FIXME: Descriptions of Java file types.
> -@c @var{file}.java
> -@c @var{file}.class
> -@c @var{file}.zip
> -@c @var{file}.jar
> -
> @item @var{file}.ads
> Ada source code file that contains a library unit declaration (a
> declaration of a package, subprogram, or generic, or a generic
>@@ -1370,7 +1364,6 @@
> ada
> f77 f77-cpp-input f95 f95-cpp-input
> go
> -java
> @end smallexample
>
> @item -x none
> @@ -3174,7 +3167,7 @@
> @item -fobjc-exceptions
> @opindex fobjc-exceptions
> Enable syntactic support for structured exception handling in
> -Objective-C, similar to what is offered by C++ and Java. This option
> +Objective-C, similar to what is offered by C++. This option
> is required to use the Objective-C keywords @code{@@try},
> @code{@@throw}, @code{@@catch}, @code{@@finally} and
> @code{@@synchronized}. This option is available with both the GNU
> @@ -10800,7 +10793,7 @@
> @opindex fbounds-check
> For front ends that support it, generate additional code to check that
> indices used to access arrays are within the declared range. This is
> -currently only supported by the Java and Fortran front ends, where
> +currently only supported by the Fortran front end, where
> this option defaults to true and false respectively.
The "defaults to true and false respectively" part no longer makes sense.
It should probably just be "defaults to false"
> @item -fcheck-pointer-bounds
> @@ -11861,8 +11854,7 @@
> This option instructs the compiler to assume that signed arithmetic
> overflow of addition, subtraction and multiplication wraps around
> using twos-complement representation. This flag enables some optimizations
> -and disables others. This option is enabled by default for the Java
> -front end, as required by the Java language specification.
> +and disables others.
> The options @option{-ftrapv} and @option{-fwrapv} override each other, so using
> @option{-ftrapv} @option{-fwrapv} on the command-line results in
> @option{-fwrapv} being effective. Note that only active options override, so
> Index: gcc/doc/standards.texi
> ===================================================================
> --- gcc/doc/standards.texi (revision 242455)
> +++ gcc/doc/standards.texi (working copy)
> @@ -315,6 +315,3 @@
>
> @xref{Standards,,Standards, gfortran, The GNU Fortran Compiler}, for details
> of standards supported by GNU Fortran.
> -
> -@xref{Compatibility,,Compatibility with the Java Platform, gcj, GNU gcj},
> -for details of compatibility between @command{gcj} and the Java Platform.
>
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [patch] remove more GCJ references
2016-11-15 22:04 ` Eric Gallager
@ 2016-11-15 23:43 ` Matthias Klose
0 siblings, 0 replies; 7+ messages in thread
From: Matthias Klose @ 2016-11-15 23:43 UTC (permalink / raw)
To: Eric Gallager; +Cc: GCC Patches, GCJ-patches
On 15.11.2016 23:03, Eric Gallager wrote:
> On 11/15/16, Matthias Klose <doko@ubuntu.com> wrote:
>> On 15.11.2016 21:41, Matthias Klose wrote:
>>> On 15.11.2016 16:52, Jeff Law wrote:
>>>> On 11/15/2016 03:55 AM, Matthias Klose wrote:
>>>>> This patch removes some references to gcj in the top level and config
>>>>> directories and in the gcc documentation. The change to the config
>>>>> directory requires regenerating aclocal.m4 and configure in each sub
>>>>> directory.
>>>>>
>>>>> Ok for the trunk?
>>>>>
>>>>> Matthias
>>>>>
>>>>> <toplevel>
>>>>>
>>>>> 2016-11-14 Matthias Klose <doko@ubuntu.com>
>>>>>
>>>>> * config-ml.in: Remove references to GCJ.
>>>>> * configure.ac: Likewise.
>>>>> * configure: Regenerate.
>>>>>
>>>>> config/
>>>>>
>>>>> 2016-11-14 Matthias Klose <doko@ubuntu.com>
>>>>>
>>>>> multi.m4: Don't set GCJ.
>>>>>
>>>>> gcc/
>>>>>
>>>>> 2016-11-14 Matthias Klose <doko@ubuntu.com>
>>>>>
>>>>> * doc/install.texi: Remove references to gcj/libjava.
>>>>> * doc/invoke.texi: Likewise.
>>>>>
>>>> OK.
>>>> jeff
>>>
>>> I was missing more references in the documentation, committing the
>>> remaining changes as obvious:
>>>
>>> gcc/
>>> 2016-11-15 Matthias Klose <doko@ubuntu.com>
>>>
>>> * doc/install.texi: Remove references to java/libjava.
>>> * doc/sourcebuild.texi: Likewise.
>>
>> and here are the remaining java reference in the user oriented
>> documentation:
>>
>> 2016-11-15 Matthias Klose <doko@ubuntu.com>
>>
>> * doc/install.texi: Remove references to java/libjava.
>> * doc/invoke.texi: Likewise.
>> * doc/standards.texi: Likewise.
>>
>> Index: gcc/doc/install.texi
>> ===================================================================
>> --- gcc/doc/install.texi (revision 242455)
>> +++ gcc/doc/install.texi (working copy)
>> @@ -4021,7 +4021,7 @@
>> it sorts relocations for REL targets (o32, o64, EABI). This can cause
>> bad code to be generated for simple C++ programs. Also the linker
>> from GNU binutils versions prior to 2.17 has a bug which causes the
>> -runtime linker stubs in very large programs, like @file{libgcj.so}, to
>> +runtime linker stubs in very large programs to
>> be incorrectly generated. GNU Binutils 2.18 and later (and snapshots
>> made after Nov. 9, 2006) should be free from both of these problems.
>>
>> Index: gcc/doc/invoke.texi
>> ===================================================================
>> --- gcc/doc/invoke.texi (revision 242455)
>> +++ gcc/doc/invoke.texi (working copy)
>> @@ -1316,12 +1316,6 @@
>> @item @var{file}.go
>> Go source code.
>>
>> -@c FIXME: Descriptions of Java file types.
>> -@c @var{file}.java
>> -@c @var{file}.class
>> -@c @var{file}.zip
>> -@c @var{file}.jar
>> -
>> @item @var{file}.ads
>> Ada source code file that contains a library unit declaration (a
>> declaration of a package, subprogram, or generic, or a generic
>> @@ -1370,7 +1364,6 @@
>> ada
>> f77 f77-cpp-input f95 f95-cpp-input
>> go
>> -java
>> @end smallexample
>>
>> @item -x none
>> @@ -3174,7 +3167,7 @@
>> @item -fobjc-exceptions
>> @opindex fobjc-exceptions
>> Enable syntactic support for structured exception handling in
>> -Objective-C, similar to what is offered by C++ and Java. This option
>> +Objective-C, similar to what is offered by C++. This option
>> is required to use the Objective-C keywords @code{@@try},
>> @code{@@throw}, @code{@@catch}, @code{@@finally} and
>> @code{@@synchronized}. This option is available with both the GNU
>> @@ -10800,7 +10793,7 @@
>> @opindex fbounds-check
>> For front ends that support it, generate additional code to check that
>> indices used to access arrays are within the declared range. This is
>> -currently only supported by the Java and Fortran front ends, where
>> +currently only supported by the Fortran front end, where
>> this option defaults to true and false respectively.
>
>
> The "defaults to true and false respectively" part no longer makes sense.
> It should probably just be "defaults to false"
thanks, committed.
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2016-11-15 23:43 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-11-15 10:55 [patch] remove more GCJ references Matthias Klose
2016-11-15 15:52 ` Jeff Law
2016-11-15 17:28 ` Matthias Klose
2016-11-15 20:41 ` Matthias Klose
2016-11-15 21:00 ` Matthias Klose
2016-11-15 22:04 ` Eric Gallager
2016-11-15 23:43 ` Matthias Klose
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).