This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
Re: [patch] More DWARF-4 support
- From: Cary Coutant <ccoutant at google dot com>
- To: Tom Tromey <tromey at redhat dot com>
- Cc: Binutils <binutils at sourceware dot org>
- Date: Thu, 3 Sep 2009 17:57:43 -0700
- Subject: Re: [patch] More DWARF-4 support
- References: <c17be2b30908191719u51ac2dcak45e376ab3aa544f7@mail.gmail.com> <m3eiqvor1l.fsf@fleche.redhat.com> <c17be2b30908281232sfa25bbbl2d5ce6194dc9c158@mail.gmail.com> <m3y6p361pa.fsf@fleche.redhat.com> <c17be2b30908281508v3e113bd5r7612e97efe5f6403@mail.gmail.com> <m3k50jznr5.fsf@fleche.redhat.com>
> Cary> http://gcc.gnu.org/wiki/ThreadSafetyAnnotation
>
> Cary> How's this? It gives an overview of the whole thread-safety annotation
> Cary> design, and points to the DWARF proposal in Google Docs.
>
> I think that for a GNU extension it would be best for the document to be
> hosted on a GNU site. ?That way we have some amount of control over the
> existence and contents of the document.
OK.
I tried translating the document into the wiki markup language, but
gave up (there's too much non-semantic markup, and the wiki doesn't
seem to take any HTML markup), so it looks like the best solution will
be to export the doc as HTML and check it in under wwwdocs/htdocs.
(a) Should this go at the top level or should I create a debug or
dwarf directory?
(b) Should I link to it from anywhere other than the dwarf2.h header?
(c) Do I need to send the HTML file in the form of a patch for review?
-cary