Re: [PATCH] Fix undefined behavior in ira-build.c

2014-06-27 Thread Vladimir Makarov
On 2014-06-27, 3:16 AM, Jakub Jelinek wrote: Hi! This fixes the most common source of the new runtime diagnostics during bootstrap-ubsan, if num is 0, ira_object_id_map is often 0 as well. Ok for trunk/4.9? Sure, Jakub. You can use num > 1 as Richard pointed out. Thanks. 2014-06-27 Jaku

Re: [PATCH] Fix undefined behavior in ira-build.c

2014-06-27 Thread Jakub Jelinek
On Fri, Jun 27, 2014 at 11:34:48AM +0200, Richard Biener wrote: > On Fri, Jun 27, 2014 at 9:16 AM, Jakub Jelinek wrote: > > Hi! > > > > This fixes the most common source of the new runtime diagnostics > > during bootstrap-ubsan, if num is 0, ira_object_id_map is often > > 0 as well. > > > > Ok for

Re: [PATCH] Fix undefined behavior in ira-build.c

2014-06-27 Thread Richard Biener
On Fri, Jun 27, 2014 at 9:16 AM, Jakub Jelinek wrote: > Hi! > > This fixes the most common source of the new runtime diagnostics > during bootstrap-ubsan, if num is 0, ira_object_id_map is often > 0 as well. > > Ok for trunk/4.9? If it's also sometimes 1 then why not if (num > 1) - just as optimi

[PATCH] Fix undefined behavior in ira-build.c

2014-06-27 Thread Jakub Jelinek
Hi! This fixes the most common source of the new runtime diagnostics during bootstrap-ubsan, if num is 0, ira_object_id_map is often 0 as well. Ok for trunk/4.9? 2014-06-27 Jakub Jelinek * ira-build.c (sort_conflict_id_map): Don't call qsort if num is 0, as ira_object_id_map