Committed documentation as r206161. Sorry about the delay. Thanks, Sharad
On Thu, Nov 28, 2013 at 10:03 AM, Martin Jambor <mjam...@suse.cz> wrote: > Hi, > > On Tue, Aug 06, 2013 at 10:18:05AM -0700, Sharad Singhai wrote: >> On Tue, Aug 6, 2013 at 10:10 AM, Martin Jambor <mjam...@suse.cz> wrote: >> > On Tue, Aug 06, 2013 at 09:22:02AM -0700, Sharad Singhai wrote: >> >> On Tue, Aug 6, 2013 at 8:57 AM, Xinliang David Li <davi...@google.com> >> >> wrote: >> >> > On Tue, Aug 6, 2013 at 5:37 AM, Martin Jambor <mjam...@suse.cz> wrote: >> >> >> Hi, >> >> >> >> >> >> On Mon, Aug 05, 2013 at 10:37:00PM -0700, Teresa Johnson wrote: >> >> >>> This patch ports messages to the new dump framework, >> >> >> >> >> >> It would be great this new framework was documented somewhere. I lost >> >> >> track of what was agreed it would be and from the uses in the >> >> >> vectorizer I was never quite sure how to utilize it in other passes. >> >> > >> >> > Sharad, can you put the documentation in GCC wiki. >> >> >> >> Sure. I had user documentation in form of gcc info. But I will add >> >> more developer details to a GCC wiki. >> >> >> > >> > I have built trunk gccint.info yesterday but could not find any string >> > dump_enabled_p there, for example. And when I quickly searched just >> > for the string "dump," I did not find any thing that looked like >> > dumping infrastructure either. OTOH, I agree that fie would be the >> > best place for the documentation. >> > >> > Or did I just miss it? What section is it in then? >> >> Actually, the user-facing documentation is in doc/invoke.texi. >> However, that doesn't describe dump_enabled_p. Do you think >> gccint.info would be a good place? I can add documentation there >> instead of creating a GCC wiki. >> > > please do not forget about this, otherwise few people will use your > framework. > > Thanks, > > Martin