On 03/01/2018 04:53 AM, Martin Liška wrote:
> On 03/01/2018 12:45 PM, Jakub Jelinek wrote:
>> On Thu, Mar 01, 2018 at 12:41:37PM +0100, Martin Liška wrote:
>>> I've been running periodically UBSAN bootstrap and as the runtime errors are
>>> not causing failure of compiler I haven't noticed the erro
PING^2
On 03/08/2018 10:27 AM, Martin Liška wrote:
PING^1
On 03/01/2018 12:53 PM, Martin Liška wrote:
On 03/01/2018 12:45 PM, Jakub Jelinek wrote:
On Thu, Mar 01, 2018 at 12:41:37PM +0100, Martin Liška wrote:
I've been running periodically UBSAN bootstrap and as the runtime errors are
not ca
PING^1
On 03/01/2018 12:53 PM, Martin Liška wrote:
> On 03/01/2018 12:45 PM, Jakub Jelinek wrote:
>> On Thu, Mar 01, 2018 at 12:41:37PM +0100, Martin Liška wrote:
>>> I've been running periodically UBSAN bootstrap and as the runtime errors are
>>> not causing failure of compiler I haven't noticed
On 03/01/2018 12:45 PM, Jakub Jelinek wrote:
> On Thu, Mar 01, 2018 at 12:41:37PM +0100, Martin Liška wrote:
>> I've been running periodically UBSAN bootstrap and as the runtime errors are
>> not causing failure of compiler I haven't noticed the errors.
>> Thus I would like to disable UBSAN recover
On Thu, Mar 01, 2018 at 12:41:37PM +0100, Martin Liška wrote:
> Hi.
>
> I've been running periodically UBSAN bootstrap and as the runtime errors are
> not causing failure of compiler I haven't noticed the errors.
> Thus I would like to disable UBSAN recovery. Apart from that I'm handling
Uh, I do
On Thu, Mar 01, 2018 at 12:41:37PM +0100, Martin Liška wrote:
> I've been running periodically UBSAN bootstrap and as the runtime errors are
> not causing failure of compiler I haven't noticed the errors.
> Thus I would like to disable UBSAN recovery. Apart from that I'm handling
> issue in md5.c w
