On Fri, Sep 6, 2013 at 6:47 AM, Diego Novillo <dnovi...@google.com> wrote:
> On 2013-08-28 17:15 , Caroline Tice wrote:
>
>> # Least ordering for dependencies mean linking w/o libstdc++ for as
>> # long as the development of libvtv does not absolutely require it.
>> Index: gcc/doc/install.texi
>> ===================================================================
>> --- gcc/doc/install.texi (revision 202060)
>> +++ gcc/doc/install.texi (working copy)
>> @@ -1032,6 +1032,16 @@ and for cross builds configured with @op
>> More documentation about multiarch can be found at
>> @uref{http://wiki.debian.org/Multiarch}.
>>
>> +@item --enable-vtable-verify
>> +Specify whether to enable or disable the vtable verification feature.
>> +Enabling this feature causes libstdc++ to be built with its virtual calls
>> +in verifiable mode. This means that, when linked with libvtv, every
>> +virtual call in libstdc++ will verify the vtable pointer through which
>> the
>> +call will be made before actually making the call. If not linked with
>> libvtv,
>> +the verifier will call stub functions (in libstdc++ itself) and do
>> nothing.
>> +If vtable verification is disabled, then libstdc++ is not built with its
>> +virutal calls in verifiable mode at all.
>
>
> s/virutal/virtual/
>
> Could you clarify in the docs whether --enable-vtable-verify is the default
> behaviour or not?
>
It will not be the default, but yes I will clarify.
> Why would I need --disable-vtv, if I can use --disable-vtable-verify?
>
--disable-vtable-verify prevents libstdc++ from being build with
verification turned on, but the libvtv library will still be built.
--disable-libvtv prevents the libvtv library from being built.
Obviously I need to add a comment like this to the documentation, so I
will.
>
> OK with those changes.
>
>
> Diego.
