------- Comment #4 from edwintorok at gmail dot com 2009-04-25 14:12 ------- (In reply to comment #3) > > The above is properly optimized. Why do you think that an inline > function taking void * would fix anything?
I can't know if memcpy will be inlined, it may just be a function call on certain systems, with certain compilers. The inline function should be a more portable way of expressing what I need, and it shouldn't cause any bugs with -fstrict-aliasing, since gcc already knows I gave my pointer to a function taking void*, so anything could happen with it, right? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39895
