[Bug c++/82818] New: Bad Codegen, delete does not check for nullptrs

2017-11-02 Thread dark_sylinc at yahoo dot com.ar
: c++ Assignee: unassigned at gcc dot gnu.org Reporter: dark_sylinc at yahoo dot com.ar Target Milestone: --- Created attachment 42539 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=42539&action=edit Simple repro of the problem The attached file, when compiled

[Bug c++/82818] Bad Codegen, delete does not check for nullptrs

2017-11-02 Thread dark_sylinc at yahoo dot com.ar
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82818 --- Comment #1 from dark_sylinc at yahoo dot com.ar --- Update: 1. Confirmed to be broken with gcc 7.2 2. When I said fsanitize; I meant fsanitize=undefined 3. When code is slightly modified as in the new attachment, the crash is gone. But it

[Bug c++/82818] Bad Codegen, delete does not check for nullptrs

2017-11-02 Thread dark_sylinc at yahoo dot com.ar
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82818 --- Comment #2 from dark_sylinc at yahoo dot com.ar --- Created attachment 42540 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=42540&action=edit Workaround. Uncomment "//a.~FastArray();" to make the crash come back