Re: [driver, doc] Support escaping special characters in specs

2017-05-02 Thread Joseph Myers
On Tue, 21 Feb 2017, Rainer Orth wrote: > 2017-01-10 Jeff Downs > Rainer Orth > > * gcc.c (handle_braces): Support escaping in switch matching > text. > * doc/invoke.texi (Spec Files): Document it. > Remove superfluous @code markup in items. OK. -- Joseph

Re: [driver, doc] Support escaping special characters in specs

2017-02-21 Thread Sandra Loosemore
On 02/21/2017 06:54 AM, Rainer Orth wrote: Hi Joseph, On Fri, 13 Jan 2017, Rainer Orth wrote: I'm unsure if the patch is large enough to need a copyright assignment (in which case it's almost certainly too late for GCC 7), and even if not if it's appropriate at this point in the release cycle

Re: [driver, doc] Support escaping special characters in specs

2017-02-21 Thread Rainer Orth
Hi Sandra, > On 01/16/2017 03:54 AM, Rainer Orth wrote: >> Hi Sandra, >> >>> On 01/13/2017 05:59 AM, Rainer Orth wrote: diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi --- a/gcc/doc/invoke.texi +++ b/gcc/doc/invoke.texi @@ -26391,6 +26391,13 @@ be as many clauses as you

Re: [driver, doc] Support escaping special characters in specs

2017-02-21 Thread Rainer Orth
Hi Joseph, > On Fri, 13 Jan 2017, Rainer Orth wrote: > >> I'm unsure if the patch is large enough to need a copyright assignment >> (in which case it's almost certainly too late for GCC 7), and even if >> not if it's appropriate at this point in the release cycle. > > I think it's big enough to ne

Re: [driver, doc] Support escaping special characters in specs

2017-01-16 Thread Sandra Loosemore
On 01/16/2017 03:54 AM, Rainer Orth wrote: Hi Sandra, On 01/13/2017 05:59 AM, Rainer Orth wrote: diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi --- a/gcc/doc/invoke.texi +++ b/gcc/doc/invoke.texi @@ -26391,6 +26391,13 @@ be as many clauses as you need. This ma @end table +The swit

Re: [driver, doc] Support escaping special characters in specs

2017-01-16 Thread Rainer Orth
Hi Sandra, > On 01/13/2017 05:59 AM, Rainer Orth wrote: >> diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi >> --- a/gcc/doc/invoke.texi >> +++ b/gcc/doc/invoke.texi >> @@ -26391,6 +26391,13 @@ be as many clauses as you need. This ma >> >> @end table >> >> +The switch matching text @code{S

Re: [driver, doc] Support escaping special characters in specs

2017-01-15 Thread Sandra Loosemore
On 01/13/2017 05:59 AM, Rainer Orth wrote: diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi --- a/gcc/doc/invoke.texi +++ b/gcc/doc/invoke.texi @@ -26391,6 +26391,13 @@ be as many clauses as you need. This ma @end table +The switch matching text @code{S} in a %@{@code{S}@}, +%@{@code{S}

Re: [driver, doc] Support escaping special characters in specs

2017-01-13 Thread Joseph Myers
On Fri, 13 Jan 2017, Rainer Orth wrote: > ok, then I'll get the ball rolling. Are the forms on > > https://www.gnu.org/software/gnulib/Copyright/ > > current? I didn't have to deal with the copyright assignment process so > far. As far as I know they are (the place I refer people to is

Re: [driver, doc] Support escaping special characters in specs

2017-01-13 Thread Rainer Orth
Hi Joseph, > On Fri, 13 Jan 2017, Rainer Orth wrote: > >> I'm unsure if the patch is large enough to need a copyright assignment >> (in which case it's almost certainly too late for GCC 7), and even if >> not if it's appropriate at this point in the release cycle. > > I think it's big enough to ne

Re: [driver, doc] Support escaping special characters in specs

2017-01-13 Thread Joseph Myers
On Fri, 13 Jan 2017, Rainer Orth wrote: > I'm unsure if the patch is large enough to need a copyright assignment > (in which case it's almost certainly too late for GCC 7), and even if > not if it's appropriate at this point in the release cycle. I think it's big enough to need an assignment. No

[driver, doc] Support escaping special characters in specs

2017-01-13 Thread Rainer Orth
As a prerequisite for (a corner case in) fixing PR target/40411, we need the ability to escape special characters in specs. Case at hand: we want to match -std=iso9899:199409 which doesn't work right now. The option isn't an alias but the canonical form (though in theory one could introduce -std=