From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31504 invoked by alias); 23 Feb 2011 02:09:55 -0000 Received: (qmail 31482 invoked by uid 22791); 23 Feb 2011 02:09:54 -0000 X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from smtp-out.google.com (HELO smtp-out.google.com) (216.239.44.51) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 23 Feb 2011 02:09:49 +0000 Received: from hpaq6.eem.corp.google.com (hpaq6.eem.corp.google.com [172.25.149.6]) by smtp-out.google.com with ESMTP id p1N29laN022346 for ; Tue, 22 Feb 2011 18:09:47 -0800 Received: from vws10 (vws10.prod.google.com [10.241.21.138]) by hpaq6.eem.corp.google.com with ESMTP id p1N28kEX011612 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for ; Tue, 22 Feb 2011 18:09:46 -0800 Received: by vws10 with SMTP id 10so3631304vws.15 for ; Tue, 22 Feb 2011 18:09:45 -0800 (PST) Received: by 10.52.168.229 with SMTP id zz5mr5266735vdb.139.1298426985402; Tue, 22 Feb 2011 18:09:45 -0800 (PST) Received: from coign.google.com ([72.14.228.1]) by mx.google.com with ESMTPS id e37sm5065997vbm.15.2011.02.22.18.09.43 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 22 Feb 2011 18:09:45 -0800 (PST) From: Ian Lance Taylor To: "Craig Dedo" Cc: "GCC Fortran" , "GCC General" , "GCC Help" Subject: Re: Can You Put Comments Into GCC Compiler Options Files? References: Mail-Followup-To: gcc-help@gcc.gnu.org Date: Wed, 23 Feb 2011 09:56:00 -0000 In-Reply-To: (Craig Dedo's message of "Tue, 22 Feb 2011 13:18:28 -0600") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-System-Of-Record: true X-IsSubscribed: yes Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org X-SW-Source: 2011-02/txt/msg00380.txt.bz2 "Craig Dedo" writes: > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 I woul= d like to start using the GNU Compiler Collection (GCC), particularly > GFortran.=C2=A0 Given the number of compiler and linker options that ther= e are, it makes a lot > of sense to put the commonly used compiler options into an options file. > > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 I read= the description of the @file options file on page 28 of the manual, > Using the GNU Compiler Collection 4.6.0.=C2=A0 However, I could not find = any information on > whether comments are allowed in options files and, if so, how comments ar= e designated so > that the compiler does not attempt to treat them as compiler or linker op= tions. > > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Please= let me know whether or not programmers can put comments into compiler > options files.=C2=A0 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