This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug driver/69367] New: spec file documentation is incomplete
- From: "sandra at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 19 Jan 2016 21:26:58 +0000
- Subject: [Bug driver/69367] New: spec file documentation is incomplete
- Auto-submitted: auto-generated
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69367
Bug ID: 69367
Summary: spec file documentation is incomplete
Product: gcc
Version: 6.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: driver
Assignee: unassigned at gcc dot gnu.org
Reporter: sandra at gcc dot gnu.org
Target Milestone: ---
When I was trying to puzzle out the meaning of a spec string using the %n
escape, I noticed that the documentation of spec file syntax in the GCC manual
does not describe that syntax, and comparing it with the comments in gcc.c it
appears a number of other %-escapes are missing documentation as well. Are all
of the %-escapes intended to be user-visible?
I'm wondering if the spec file documentation really ought to be moved to the
internals or installation manual, for that matter. I've seen the --with-specs
configure option used, but do real users really use the -specs= option to
override the specs GCC was configured with?