[Bug middle-end/83022] malloc & memset -> calloc is not always an optimization

2017-11-17 Thread nathan at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83022 Nathan Sidwell changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Last reconfirmed|

[Bug middle-end/83022] malloc & memset -> calloc is not always an optimization

2017-11-16 Thread nathan at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83022 --- Comment #2 from Nathan Sidwell --- Yes, this is a measurable degradation in going from gcc 4.9 -> 5.0 with myrocks DB. Apparently 25% more queries/sec with gcc 4.9 (I think it's from a benchmark). Profiling (by others) has fingered this

[Bug middle-end/83022] malloc & memset -> calloc is not always an optimization

2017-11-16 Thread glisse at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83022 --- Comment #1 from Marc Glisse --- I am pretty sure this was discussed when the patch was reviewed. IIRC the original patch was specifically pattern-matching if(p!=0) (with p the result of malloc) as the only acceptable condition between malloc