Re: [cfe-users] cacheflush.2

2020-12-21 Thread Alejandro Colomar (man-pages) via cfe-users
Hello Martin, Thanks for the correction! Then the prototypes that changes from 'char *' to 'void *' in r269082 were not exposed to the user, right? I guess then those are just internal implementation where GCC did use 'char *'. Where is the actual prototype exposed to the user declared? Thanks,

Re: [cfe-users] cacheflush.2

2020-12-21 Thread Martin Sebor via cfe-users
On 12/11/20 11:14 AM, Alejandro Colomar (man-pages) via Gcc wrote: It looks like GCC recently moved from 'char *' to 'void *'. This SO question[1] (4 years ago) quotes the GCC docs and they had 'char *'. __builtin___clear_cache in GCC has always been declared to take void*. The signature in th

Re: [cfe-users] cacheflush.2

2020-12-11 Thread Alejandro Colomar (man-pages) via cfe-users
It looks like GCC recently moved from 'char *' to 'void *'. This SO question[1] (4 years ago) quotes the GCC docs and they had 'char *'. Maybe Clang hasn't noticed the change. I'll report a bug. [1]: https://stackoverflow.com/q/35741814/6872717 On 12/9/20 8:15 PM, Alejandro Colomar (man-pages) wr

Re: [cfe-users] cacheflush.2

2020-12-11 Thread Alejandro Colomar (man-pages) via cfe-users
Hi Heinrich, It looks like a bug (or at least an undocumented divergence from GCC) in Clang/LLVM. Or I couldn't find the documentation for it. Clang uses 'char *': https://github.com/llvm/llvm-project/blob/7faf62a80bfc3a9dfe34133681fcc31f8e8d658b/clang/include/clang/Basic/Builtins.def#L583 GCC