public inbox for java-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: David Daney <ddaney@avtrex.com>
To: Andrew Haley <aph@redhat.com>
Cc: Gerald Pfeifer <gerald@pfeifer.com>,
		Tom Tromey <tromey@redhat.com>,
	java-patches@gcc.gnu.org, 	gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] libjava: Add option to disable BC ABI in libgcj.
Date: Sat, 26 Jan 2008 21:50:00 -0000	[thread overview]
Message-ID: <479BAB00.2000202@avtrex.com> (raw)
In-Reply-To: <479B1090.9090307@redhat.com>

Andrew Haley wrote:
> David Daney wrote:
>> Gerald Pfeifer wrote:
>>> +@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}
>>> +@option{-fno-indirect-classes}.  This allows them to be overridden at
>>> +runtime.
>>>
>>> When first reading this, I got a bit confused by two aspects.  
>>> Perhaps this is something to address in a follow-up patch, David?
>>>
>>> One was that "BC API compilation" (including myself ;-) isn't 
>>> something most readers of doc/install.texi would be familiar with.  
>>> How about
>>> expanding this or adding a reference/cross-reference?
>>>
>>> The second one was that I wasn't sure what "This" referred to: the 
>>> configure option, or the previous sentence explaining BC ABI 
>>> compilation.
>>> Perhaps replacing this by ", which" might be more clear?
>>>
>>> +If @option{--disable-libgcj-bc} is specified, libgcj is built without
>>> +these options.  This makes it impossible to override portions of
>>> +libgcj at runtime, but can make it easier to statically link to 
>>> libgcj.
>>>
>>> Why does this read "can make" and not just "makes"?  I'm sure there is
>>> some technical background here which I'm missing. :-)  Perhaps a 
>>> (cross)
>>> reference to more detailed information somewhere else could clarify 
>>> that?
>>>   
>> How about this version instead?  I think it gets rid of some of the
>> ambiguity and explains things a bit better.
>>
>> There really is nothing other than e-mail archives that could be cross
>> referenced to provide deeper information about this option.
>
> See ftp://gcc.gnu.org/pub/gcc/summit/2004/GCJ%20New%20ABI.pdf

While I could certainly reference this paper, I am not sure that 
install.texi is the best place for such a reference.

I was thinking that if someone wanted to know the gory details, they 
could look up -findirect-dispatch.  I was trying to keep the install 
documentation as small as possible while still describing what the new 
option does.

>
>> Tested with make info and make html with no errors.
>>
>> 2008-01-25  David Daney  <ddaney@avtrex.com>
>>
>>     * doc/install.texi (--disable-libgcj-bc):  Reword documentation.
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>> Index: doc/install.texi
>> ===================================================================
>> --- doc/install.texi    (revision 131856)
>> +++ doc/install.texi    (working copy)
>> @@ -1557,12 +1557,13 @@ 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}
>> -@option{-fno-indirect-classes}.  This allows them to be overridden at
>> -runtime.
>> +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 makes it impossible to override portions of
>> -libgcj at runtime, but can make it easier to statically link to libgcj.
>> +these options.  This allows the compile-time linker to resolve
>> +dependencies when statically linking to libgcj.  However it makes it
>> +impossible to override the effected portions of libgcj at run-time.
>
> Is that *a*ffected rather than *e*ffected?
>
I don't think so, but I have a limited grasp of the English language.  I 
will defer to others on which of 'affected' or 'effected' should be used 
here.

David Daney

  reply	other threads:[~2008-01-26 21:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-21 22:25 David Daney
2007-12-21 23:40 ` Tom Tromey
2007-12-22 11:19 ` Andrew Haley
2007-12-30 14:31 ` Gerald Pfeifer
2008-01-26  5:18   ` David Daney
2008-01-26 10:51     ` Andrew Haley
2008-01-26 21:50       ` David Daney [this message]
2008-01-27 10:34         ` Andrew Haley
2008-01-28  0:09           ` Gerald Pfeifer
2008-01-28  4:38             ` David Daney
2008-01-28 10:23               ` Andrew Haley

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=479BAB00.2000202@avtrex.com \
    --to=ddaney@avtrex.com \
    --cc=aph@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gerald@pfeifer.com \
    --cc=java-patches@gcc.gnu.org \
    --cc=tromey@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).