On 02/11/2016 08:43 AM, David Malcolm wrote:
On Thu, 2016-02-11 at 10:16 +0100, Richard Biener wrote:
On Wed, Feb 10, 2016 at 5:25 PM, Bernd Schmidt
wrote:
On 02/09/2016 09:44 PM, David Malcolm wrote:
This is a bug in a new feature, so it isn't a regression as such,
but
On Wed, Feb 10, 2016 at 5:25 PM, Bernd Schmidt wrote:
> On 02/09/2016 09:44 PM, David Malcolm wrote:
>>
>> This is a bug in a new feature, so it isn't a regression as such, but
>> it's fairly visible, and I believe the fix is relatively low-risk
>> (error-handling of typos of
On Thu, 2016-02-11 at 10:16 +0100, Richard Biener wrote:
> On Wed, Feb 10, 2016 at 5:25 PM, Bernd Schmidt
> wrote:
> > On 02/09/2016 09:44 PM, David Malcolm wrote:
> > >
> > > This is a bug in a new feature, so it isn't a regression as such,
> > > but
> > > it's fairly
On 02/09/2016 09:44 PM, David Malcolm wrote:
This is a bug in a new feature, so it isn't a regression as such, but
it's fairly visible, and I believe the fix is relatively low-risk
(error-handling of typos of command-line options).
This also now covers PR driver/69453 (and its duplicate PR
Ping.
This is a bug in a new feature, so it isn't a regression as such, but
it's fairly visible, and I believe the fix is relatively low-risk
(error-handling of typos of command-line options).
This also now covers PR driver/69453 (and its duplicate PR
driver/69642), so people *are* running
As of r230285 (b279775faf3c56b554ecd38159b70ea7f2d37e0b; PR driver/67613)
the driver provides suggestions for misspelled options.
This works well for some options e.g.
$ gcc -static-libfortran test.f95
gcc: error: unrecognized command line option '-static-libfortran';
did you mean