Re: [C++ PATCH] -Wclass-memaccess fixes and improvements (PR c++/81327)

On Wed, Jan 10, 2018 at 11:25 AM, Jakub Jelinek wrote: > On Wed, Jan 10, 2018 at 10:46:06AM -0500, Jason Merrill wrote: >> >> This patch moves the warning tiny bit earlier (from build_cxx_call to the >> >> caller) where we still have information about the original parsed >> >>

Re: [C++ PATCH] -Wclass-memaccess fixes and improvements (PR c++/81327)

On Wed, Jan 10, 2018 at 10:46:06AM -0500, Jason Merrill wrote: > >> This patch moves the warning tiny bit earlier (from build_cxx_call to the > >> caller) where we still have information about the original parsed > >> arguments before conversions to the builtin argument types. > > OK. Is that an

Re: [C++ PATCH] -Wclass-memaccess fixes and improvements (PR c++/81327)

On Fri, Jan 5, 2018 at 6:37 PM, Martin Sebor wrote: > On 01/05/2018 03:02 PM, Jakub Jelinek wrote: >> >> Hi! >> >> Apparently LLVM allows similar warning to -Wclass-memaccess (is it just >> similar or same?; if the latter, perhaps we should use the same option for >> that) to be

Re: [C++ PATCH] -Wclass-memaccess fixes and improvements (PR c++/81327)

On 01/05/2018 03:02 PM, Jakub Jelinek wrote: Hi! Apparently LLVM allows similar warning to -Wclass-memaccess (is it just similar or same?; if the latter, perhaps we should use the same option for that) to be disabled not just by casting the destination pointer to e.g. (char *) or some other

[C++ PATCH] -Wclass-memaccess fixes and improvements (PR c++/81327)

Hi! Apparently LLVM allows similar warning to -Wclass-memaccess (is it just similar or same?; if the latter, perhaps we should use the same option for that) to be disabled not just by casting the destination pointer to e.g. (char *) or some other pointer to non-class, but also to (void *), which