From: Ian Lance Taylor <iant@google.com>
To: "Craig Dedo" <craig@ctdedo.com>
Cc: "GCC Fortran" <fortran@gcc.gnu.org>,
"GCC General" <gcc@gcc.gnu.org>,
"GCC Help" <gcc-help@gcc.gnu.org>
Subject: Re: Can You Put Comments Into GCC Compiler Options Files?
Date: Wed, 23 Feb 2011 09:56:00 -0000 [thread overview]
Message-ID: <mcrtyfv4i3f.fsf@google.com> (raw)
In-Reply-To: <!&!AAAAAAAAAAAYAAAAAAAAADwWT6ZWSIFJsr5qVFz+64/CgAAAEAAAAO1WTmtReHFMjzdDEp79oKUBAAAAAA==@ctdedo.com> (Craig Dedo's message of "Tue, 22 Feb 2011 13:18:28 -0600")
"Craig Dedo" <craig@ctdedo.com> writes:
> I would like to start using the GNU Compiler Collection (GCC), particularly
> GFortran. Given the number of compiler and linker options that there are, it makes a lot
> of sense to put the commonly used compiler options into an options file.
>
> I read the description of the @file options file on page 28 of the manual,
> Using the GNU Compiler Collection 4.6.0. However, I could not find any information on
> whether comments are allowed in options files and, if so, how comments are designated so
> that the compiler does not attempt to treat them as compiler or linker options.
>
> Please let me know whether or not programmers can put comments into compiler
> options files. If so, please let me know how to designate comments.
This question is not appropriate for the mailing lists gcc@gcc.gnu.org
or fortran@gcc.gnu.org. Please take any followups only to
gcc-help@gcc.gnu.org. In the future, please avoid cross-posting to both
gcc@gcc.gnu.org and gcc-help@gcc.gnu.org. Thanks.
No comments are permitted in the contents of options files read using
the @file syntax. The contents of the file are simply interpreted as
command line arguments separated by whitespace. Double quotes, single
quotes, and backslashes may be used in the usual way to add whitespace
to arguments.
Ian
prev parent reply other threads:[~2011-02-23 2:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-22 19:57 Craig Dedo
2011-02-23 9:56 ` Ian Lance Taylor [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=mcrtyfv4i3f.fsf@google.com \
--to=iant@google.com \
--cc=craig@ctdedo.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-help@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).