On 3/29/19 6:31 AM, zhroma wrote:
> Martin Sebor wrote 2019-03-28 22:44:
>> On 3/28/19 11:49 AM, Roman Zhuykov wrote:
>>> Ping
>>>
>>> A week ago I decided it is so minor that I can report here with a
>>> patch without creating bugzilla PR.
>>> Technically it is a "9 regression" in new functionalit
Martin Sebor wrote 2019-03-28 22:44:
On 3/28/19 11:49 AM, Roman Zhuykov wrote:
Ping
A week ago I decided it is so minor that I can report here with a
patch without creating bugzilla PR.
Technically it is a "9 regression" in new functionality added back in
summer.
Patch was succesfully bootst
On 3/28/19 11:49 AM, Roman Zhuykov wrote:
Ping
A week ago I decided it is so minor that I can report here with a
patch without creating bugzilla PR.
Technically it is a "9 regression" in new functionality added back in summer.
Patch was succesfully bootstrapped and regtested on x86_64.
Ok for
Ping
A week ago I decided it is so minor that I can report here with a
patch without creating bugzilla PR.
Technically it is a "9 regression" in new functionality added back in summer.
Patch was succesfully bootstrapped and regtested on x86_64.
Ok for trunk?
чт, 21 мар. 2019 г. в 18:53, Roman Z
Hello, I have found a minor diagnostic issue.
Since r262910 we got a little odd error messages in cases like this:
$ gcc -flto-compression-level=2-O2 -c empty.c
gcc: error: argument to '-flto-compression-level=' is not between 0 and 9
$ g++ -fabi-version=2-O2 -c empty.cpp
cc1plus: error: '-fabi-ve
