This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH/Merge Request] Vtable Verification feature.
- From: Caroline Tice <cmtice at google dot com>
- To: Rainer Orth <ro at cebitec dot uni-bielefeld dot de>
- Cc: GCC Patches <gcc-patches at gcc dot gnu dot org>, Benjamin Kosnik <bkoz at redhat dot com>, Benjamin De Kosnik <b dot dekosnik at gmail dot com>, Bhaskar Janakiraman <bjanakiraman at google dot com>, Diego Novillo <dnovillo at google dot com>, Jason Merrill <jason at redhat dot com>
- Date: Mon, 12 Aug 2013 13:01:41 -0700
- Subject: Re: [PATCH/Merge Request] Vtable Verification feature.
- References: <CABtf2+Q47X0Ld6byo8R96TTKuYPkOsKO7tADRRWVpFqHHTsfuw at mail dot gmail dot com> <yddbo58pjex dot fsf at lokon dot CeBiTec dot Uni-Bielefeld dot DE> <CABtf2+SrVT+CyO9+UOdO8X_eggTK2SnkNkyyRAL-nRR1CpOVEA at mail dot gmail dot com>
On Thu, Aug 8, 2013 at 9:34 AM, Caroline Tice <cmtice@google.com> wrote:
> On Thu, Aug 8, 2013 at 3:27 AM, Rainer Orth <ro@cebitec.uni-bielefeld.de> wrote:
>> Caroline,
>>
>
>> As an aside, I had a very quick look at libvtv to determine what's
>> required for a port to a non-Linux platform. It would be good if the
>> requirements (currently, ELF, dl_iterate_phdr, __fortify_fail, certainly
>> several more) could be documented to ease porters' task.
>>
>
>
> I will be working on some documentation for this.
>
>> Thanks.
>>
>> Rainer
>>
I have finished my first pass at the porting documentation. It is now
available on the vtable verification feature web site:
http://gcc.gnu.org/wiki/vtv
I've never attempted to write porting documentation before, so I'm
hoping that what I wrote is what was needed. If I missed anything
important, please let me know.
-- Caroline Tice
cmtice@google.com