From: Matthias Klose <doko@ubuntu.com>
To: GCC Patches <gcc-patches@gcc.gnu.org>,
GCJ-patches <java-patches@gcc.gnu.org>
Subject: Re: [patch] remove more GCJ references
Date: Tue, 15 Nov 2016 21:00:00 -0000 [thread overview]
Message-ID: <e433dc5f-eac6-3f9f-3e60-8447f008a811@ubuntu.com> (raw)
In-Reply-To: <3a92f93f-0043-a296-0bfb-890cf33f0d83@ubuntu.com>
[-- 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.
next prev parent reply other threads:[~2016-11-15 21:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-15 10:55 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 [this message]
2016-11-15 22:04 ` Eric Gallager
2016-11-15 23:43 ` Matthias Klose
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=e433dc5f-eac6-3f9f-3e60-8447f008a811@ubuntu.com \
--to=doko@ubuntu.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=java-patches@gcc.gnu.org \
/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).