public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Zack Weinberg <zack@codesourcery.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: other/633: In specs, %{<XXX*} does NOT remove switches from c ommand line Date: Tue, 26 Nov 2002 12:16:00 -0000 [thread overview] Message-ID: <20021119183604.7864.qmail@sources.redhat.com> (raw) The following reply was made to PR other/633; it has been noted by GNATS. From: Zack Weinberg <zack@codesourcery.com> To: Bosscher Steven Civ USAFA/DFAN <Steven.Bosscher@usafa.af.mil> Cc: "'gcc-gnats@gcc.gnu.org'" <gcc-gnats@gcc.gnu.org>, "'gcc-bugs@gcc.gnu.org'"<gcc-bugs@gcc.gnu.org>, "'rsandifo@redhat.com'" <rsandifo@redhat.com> Subject: Re: other/633: In specs, %{<XXX*} does NOT remove switches from c ommand line Date: Tue, 19 Nov 2002 10:29:02 -0800 Bosscher Steven Civ USAFA/DFAN <Steven.Bosscher@usafa.af.mil> writes: > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&p > r=633 > > It seems that PR other/633 ("In specs, %{<XXX*} does NOT remove switches > from command line") was fixed long ago by: > > 2000-12-13 Tom Tromey <tromey@redhat.com> > > * gcc.c (handle_braces): Handle %{<S*} spec correctly. > > Maybe somebody with GNATS write access can close the bug? Done. > But it seems that all occurrences of %{<S*} should be replaced with %<S* > since the changes on 2002-09-19 by Zack Weinberg. > > The %{<S*} spec is still used (or again, actually, was introduced > 2002-10-15) in config/mips/vr.h: "%{mabi=32:%{<mgp32}}". Is this a bug? My change is only present on the basic-improvements branch. config/mips/vr.h does need to be changed there. I have a lot of delicate changes in my copy of that branch right now -- would you mind submitting a patch? zw
reply other threads:[~2002-11-19 18:36 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20021119183604.7864.qmail@sources.redhat.com \ --to=zack@codesourcery.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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: linkBe 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).