[Bug driver/30091] specs file: [EMAIL PROTECTED]' not documented

2007-01-20 Thread tromey at gcc dot gnu dot org 


--- Comment #3 from tromey at gcc dot gnu dot org  2007-01-21 03:08 ---
I have a patch to document '#' and '@'.
I'll submit it shortly.

Currently gcc.c and invoke.texi are mostly kept in sync.
However I haven't audited to make sure they are fully in sync.

Adding support for \f is probably more complicated than just
changing skip_whitespace.  I think it is fine to just leave
the code as is; users can use multiple blank lines and also
comments to separate chunks of spec files.


-- 

tromey at gcc dot gnu dot org changed:

   What|Removed |Added

 AssignedTo|unassigned at gcc dot gnu   |tromey at gcc dot gnu dot
   |dot org |org
 Status|UNCONFIRMED |ASSIGNED
 Ever Confirmed|0   |1
   Last reconfirmed|-00-00 00:00:00 |2007-01-21 03:08:03
   date||


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30091

[Bug driver/30091] specs file: [EMAIL PROTECTED]' not documented

2006-12-08 Thread pinskia at gcc dot gnu dot org 


--- Comment #2 from pinskia at gcc dot gnu dot org  2006-12-08 09:25 ---
specs are an internal format really.  It is very subject to change each
release.  Also some time in the future we might decide to get rid of the specs.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30091

[Bug driver/30091] specs file: [EMAIL PROTECTED]' not documented

2006-12-06 Thread tschwinge at gnu dot org 


--- Comment #1 from tschwinge at gnu dot org  2006-12-06 18:22 ---
It is also not documented that `#COMMENT' can be used to embed comments.


And `\f' (form feed, `^L') could be added to list of white space (in the
skip_whitespace function): it's convenient to separate units in hand-made specs
files by form feed characters.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30091