From: Ian Lance Taylor <iant@google.com>
To: IainS <developer@sandoe-acoustics.co.uk>
Cc: GCC Development <gcc@gcc.gnu.org>
Subject: Re: specs question.
Date: Mon, 12 Apr 2010 22:30:00 -0000 [thread overview]
Message-ID: <mcrsk701f7u.fsf@dhcp-172-17-9-151.mtv.corp.google.com> (raw)
In-Reply-To: <6807833B-8AB9-468B-9936-09025C700DF7@sandoe-acoustics.co.uk> (IainS's message of "Sun\, 11 Apr 2010 18\:46\:54 +0100")
IainS <developer@sandoe-acoustics.co.uk> writes:
> what is the expected behavior of ?
>
> %{.c|.cc|.for|.F90: foo }
>
> .. as I read gcc/gcc.c I would expect to get "foo" for command lines
> with files with these suffixes:
> .c
> .cc
> .for
> .F90
>
> but not otherwise (since it says . binds more strongly than |) ;
That sounds right to me. Do you see something different?
Ian
next prev parent reply other threads:[~2010-04-12 22:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-11 17:49 IainS
2010-04-12 22:30 ` Ian Lance Taylor [this message]
2010-04-12 22:41 ` IainS
2010-04-12 23:26 ` Ian Lance Taylor
2010-04-12 23:44 ` IainS
2010-04-13 0:01 ` Ian Lance Taylor
2010-04-13 8:55 ` IainS
2010-04-13 18:14 ` Peter O'Gorman
2010-04-13 19:21 ` IainS
2022-05-27 10:25 Iain Sandoe
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=mcrsk701f7u.fsf@dhcp-172-17-9-151.mtv.corp.google.com \
--to=iant@google.com \
--cc=developer@sandoe-acoustics.co.uk \
--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).