From: Matthias Klose <doko@ubuntu.com>
To: Eric Gallager <egall@gwmail.gwu.edu>
Cc: 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 23:43:00 -0000 [thread overview]
Message-ID: <32b29ab0-e482-ff7d-72a7-3daac82e22ae@ubuntu.com> (raw)
In-Reply-To: <CAMfHzOvu7v-QB8D+amprZMD0u9VWTN-uQR66OuzbT4s5eCC22Q@mail.gmail.com>
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.
prev parent reply other threads:[~2016-11-15 23:43 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
2016-11-15 22:04 ` Eric Gallager
2016-11-15 23:43 ` Matthias Klose [this message]
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=32b29ab0-e482-ff7d-72a7-3daac82e22ae@ubuntu.com \
--to=doko@ubuntu.com \
--cc=egall@gwmail.gwu.edu \
--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).