Re: -fgraphite docs

2009-01-20 Thread Sebastian Pop
On Mon, Jan 19, 2009 at 11:27 PM, Ben Elliston wrote: > On Mon, 2009-01-19 at 23:20 -0600, Sebastian Pop wrote: > >> > Perhaps we should add a comment to common.opt to explain this? >> >> Yes, we could apply this patch. > > Looks good to me (and I think it qualifies as obvious) :-). I've committe

Re: -fgraphite docs

2009-01-19 Thread Ben Elliston
On Mon, 2009-01-19 at 23:20 -0600, Sebastian Pop wrote: > > Perhaps we should add a comment to common.opt to explain this? > > Yes, we could apply this patch. Looks good to me (and I think it qualifies as obvious) :-). Thanks, Ben

Re: -fgraphite docs

2009-01-19 Thread Sebastian Pop
On Mon, Jan 19, 2009 at 11:11 PM, Ben Elliston wrote: >> > Is this an oversight, or are these options deprecated? >> >> These options are intentionally not documented: they should not be >> used by programmers. > > Perhaps we should add a comment to common.opt to explain this? Yes, we could apply

Re: -fgraphite docs

2009-01-19 Thread Ben Elliston
> > Is this an oversight, or are these options deprecated? > > These options are intentionally not documented: they should not be > used by programmers. Perhaps we should add a comment to common.opt to explain this? Ben

Re: -fgraphite docs

2009-01-19 Thread Sebastian Pop
On Mon, Jan 19, 2009 at 10:45 PM, Ben Elliston wrote: > Hi Sebastian > > While reading through the Graphite code on the trunk, I noticed that > -fgraphite and -fgraphite-identity are no documented in doc/invoke.texi. > Is this an oversight, or are these options deprecated? These options are inten