Displaying 4 results from an estimated 4 matches for "zhikhar".
Did you mean:
shikhar
2020 Feb 20
2
Given one restrict pointer based on another, should they never alias?
...*pA, long N) {
> int *restrict x = pA;
>
> int tmp;
> {
> int *restrict y = x + N;
> tmp = *y;
> }
>
> *x = tmp; // may alias with *y
> }
>
> Greetings,
>
>
>
> Jeroen Dobbelaere
>
>
>
>
>
>
>
> *From:* Alexey Zhikhartsev <alexey.zhikhar at gmail.com>
> *Sent:* Friday, February 14, 2020 22:52
> *To:* via Llvm-dev <llvm-dev at lists.llvm.org>
> *Cc:* Jeroen Dobbelaere <dobbel at synopsys.com>; hfinkel at anl.gov
> *Subject:* Given one restrict pointer based on another, should they ne...
2019 Nov 03
2
Full restrict support - status update
...look at the number of
operands to see if they are present or not
- or maybe it is sufficient to look at the number of operands, and the noalias_sidechannel operand should
be added with an extra bit, indicating if it is really there or not...
Greetings,
Jeroen Dobbelaere
From: Alexey Zhikhartsev <alexey.zhikhar at gmail.com>
Sent: Thursday, October 31, 2019 16:21
To: Jeroen Dobbelaere <dobbel at synopsys.com>
Cc: llvm-dev at lists.llvm.org
Subject: Re: [llvm-dev] Full restrict support - status update
Hi Jeroen,
Thank you very much for the great work, it is much appreciate...
2020 Feb 14
2
Given one restrict pointer based on another, should they never alias?
We recently found an issue when using the full restrict implementation
developed by Jeroen; it surfaces when compiling an obscure combination of
std::valarray and std::indirect_array but I don't want to bore you with all
the details. What it boils down to is this basic question about restrict:
Given one restrict pointer based on another, should they never alias?
As far as I understand the
2019 Oct 29
7
Full restrict support - status update
Hi all,
## Status:
During the past weeks I have updated the restrict patches with various improvements:
- the ScopedNoAliasAA now also works together with the new pass manager
- the SLPVectorizer now works nice with the noalias support.
- there were some issues with some of the options enabling/disabling full restrict. These have been fixed.
- various smaller enhancements.
Today, I rebased the