Hi Martin,
Thanks! It's good to learn some GCC internal details :)
Cheers,
Alex
On 12/18/20 5:51 PM, Martin Sebor wrote:
> On 12/18/20 3:42 AM, Alejandro Colomar (man-pages) wrote:
>> Hi Martin,
>>
>> I sent you an email, but I received a "delivery failure".
>> If you're reading this from a li
On 12/18/20 3:42 AM, Alejandro Colomar (man-pages) wrote:
Hi Martin,
I sent you an email, but I received a "delivery failure".
If you're reading this from a list, could you answer, please?
Thanks,
Alex
On 12/14/20 11:34 PM, Alejandro Colomar (man-pages) wrote:
Hello Martin,
Thanks for the c
Hi Martin,
I sent you an email, but I received a "delivery failure".
If you're reading this from a list, could you answer, please?
Thanks,
Alex
On 12/14/20 11:34 PM, Alejandro Colomar (man-pages) wrote:
> Hello Martin,
>
> Thanks for the correction!
> Then the prototypes that changes from 'cha
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,
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
I forgot to add a junk to the text.
v4:
NOTES
Unless you need the finer grained control that this system
call provides, you probably want to use the GCC built-in
function __builtin___clear_cache(), which provides a portable
interface across platforms supported
Hi all,
Please review this text:
[
NOTES
Unless you need the finer grained control that this system
call provides, you probably want to use the GCC built-in
function __builtin___clear_cache(), which provides a more
portable interface:
void __bui
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
Hi Michael,
On 12/11/20 9:15 AM, Michael Kerrisk (man-pages) wrote:
> i Alex,
>
> On 12/10/20 9:56 PM, Alejandro Colomar (man-pages) wrote:
>> Hi all,
>>
>> v2:
>>
>> [
>> NOTES
>>Unless you need the finer grained control that this system
>>call provides, you probably want to
i Alex,
On 12/10/20 9:56 PM, Alejandro Colomar (man-pages) wrote:
> Hi all,
>
> v2:
>
> [
> NOTES
>Unless you need the finer grained control that this system
>call provides, you probably want to use the GCC built-in
>function __builtin___clear_cache(), which pr
(void *begin, void *end);
]
If you like it, I'll send the patch.
BTW, I'll also have a look and document the different prototypes for
cacheflush(2).
Thanks,
Alex
On 12/10/20 8:20 PM, Heinrich Schuchardt wrote:
> On 12/10/20 7:17 PM, Dave Martin wrote:
>> On Wed, Dec 09, 2020
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
12 matches
Mail list logo
