Re: target hooks / plugins

2010-01-13 Thread Joseph S. Myers
On Wed, 13 Jan 2010, Joern Rennecke wrote: > Duplicating all these changes separately by hand seems nigh impossible. > I think the best approach is then to take the auto-generated tm.texi as > the new tm.texi, and packages it up as a patch together with the > struct member / hook name changes that

Re: target hooks / plugins

2010-01-13 Thread Joern Rennecke
Quoting "Joseph S. Myers" : Please note that your initial change to implement automatic doc extraction should not result in any changes to the Texinfo content of the manual. Such fixes should all go in either before or after the automatic doc extraction change, but not at the same time; the doc

Re: target hooks / plugins

2010-01-13 Thread Joseph S. Myers
On Wed, 13 Jan 2010, Joern Rennecke wrote: > Quoting "Joseph S. Myers" : > > If you want to have documentation extracted from source files, you need to > > engage with the SC and FSF at an early stage to get suitable license > > exception wording to permit the relevant text to be used in the manua

Re: target hooks / plugins

2010-01-13 Thread Joern Rennecke
Quoting "Joseph S. Myers" : If you want to have documentation extracted from source files, you need to engage with the SC and FSF at an early stage to get suitable license exception wording to permit the relevant text to be used in the manuals as well as the main (GPL) sources. I haven't gotten

Re: target hooks / plugins

2010-01-05 Thread Joern Rennecke
Quoting "Joseph S. Myers" : On Wed, 23 Dec 2009, Joern Rennecke wrote: I've attached what I have so far. If you want to have documentation extracted from source files, you need to engage with the SC and FSF at an early stage to get suitable license exception wording to permit the relevant te

RE: target hooks / plugins

2009-12-30 Thread Grigori Fursin
cember 24, 2009 1:26 PM > To: Joern Rennecke > Cc: 'GCC Mailing List'; Grigori Fursin; 'Yuanjie Huang'; 'Liang Peng'; > 'Zbigniew Chamski'; > 'Yuri Kashnikoff'; 'Diego Novillo' > Subject: Re: target hooks / plugin

Re: target hooks / plugins

2009-12-30 Thread Richard Guenther
On Thu, Dec 24, 2009 at 1:32 AM, Joern Rennecke wrote: > Quoting Joern Rennecke : >> >> Right now, to make a new target hook, you have to add a new field in >> target.h, define a new default in target-def.h, place the new macro >> in exactly the right position there of the right initializer macro,

Re: target hooks / plugins

2009-12-24 Thread Joseph S. Myers
It appears you CC:ed your message to a closed mailing list ctuning-discussi...@googlegroups.com that bounces messages from non-subscribers. Please avoid doing this; messages to public lists should not be CC:ed to any list that will send bounces or other automatic replies to non-subscribers. Y

Re: target hooks / plugins

2009-12-24 Thread Joseph S. Myers
On Wed, 23 Dec 2009, Joern Rennecke wrote: > I've attached what I have so far. If you want to have documentation extracted from source files, you need to engage with the SC and FSF at an early stage to get suitable license exception wording to permit the relevant text to be used in the manuals

Re: target hooks / plugins

2009-12-23 Thread Joern Rennecke
Quoting Joern Rennecke : Right now, to make a new target hook, you have to add a new field in target.h, define a new default in target-def.h, place the new macro in exactly the right position there of the right initializer macro, describe the new hook in tm.texi, and if you need a new function wi