Displaying 7 results from an estimated 7 matches for "pykhtin".
2016 Mar 09
3
"Do not use Static Constructors" LLVM Coding Standard rule question
...g thursday) , as
there is no (trivial) way to know that this stringmap exists, or that it
may need cleaning out between two compilations, for example. The risk with
such constructs is that they build up over time, and appear to be "memory
leaks".
--
Mats
On 9 March 2016 at 09:45, valery pykhtin via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> Right, but it produces a mem leak, I'm not sure what is worse :-)
>
> On Wed, Mar 9, 2016 at 10:49 AM, David Blaikie <dblaikie at gmail.com> wrote:
>
>> a static local still produces a static dtor, though
>>...
2016 Mar 09
2
"Do not use Static Constructors" LLVM Coding Standard rule question
...rst sentence in the section says.
>
> "Static constructors and destructors (e.g. global variables whose types
> have a constructor or destructor) should not be added to the code base, and
> should be removed wherever possible."
>
> On Tue, Mar 8, 2016 at 10:52 PM, valery pykhtin via llvm-dev <
> llvm-dev at lists.llvm.org> wrote:
>
>> Hi,
>>
>> I'm new here and have a question about the rule in title. Is the
>> following use case also prohibited?
>>
>> int findNameId(StringRef Name)
>> {
>> static StringMap...
2016 Mar 09
2
"Do not use Static Constructors" LLVM Coding Standard rule question
Hi,
I'm new here and have a question about the rule in title. Is the following
use case also prohibited?
int findNameId(StringRef Name)
{
static StringMap<int> Map = createSomeIDMap();
return Map.lookup(Name);
};
It seems it isn't influence startup time and doesn't create initialization
order problems. Clang isn't complaining about it with -Wglobal-constructor
flag.
2017 Jun 14
0
Implementing cross-thread reduction in the AMDGPU backend
...ed, use a 0 instead
So the problematic case is where bound_cntl is 0, not when it is 1.
-----Original Message-----
From: Tom Stellard [mailto:tstellar at redhat.com]
Sent: Tuesday, June 13, 2017 6:13 PM
To: Matt Arsenault
Cc: Connor Abbott; llvm-dev at lists.llvm.org; Kolton, Sam; Sumner, Brian; Pykhtin, Valery
Subject: Re: [llvm-dev] Implementing cross-thread reduction in the AMDGPU backend
On 06/13/2017 07:33 PM, Matt Arsenault wrote:
>
>> On Jun 12, 2017, at 17:23, Tom Stellard <tstellar at redhat.com <mailto:tstellar at redhat.com>> wrote:
>>
>> On 06/12/2017...
2017 Jun 15
1
Implementing cross-thread reduction in the AMDGPU backend
...it in the row_mask or bank_mask will also disable updating the result.
Brian
-----Original Message-----
From: Connor Abbott [mailto:cwabbott0 at gmail.com]
Sent: Wednesday, June 14, 2017 6:13 PM
To: tstellar at redhat.com
Cc: Matt Arsenault; llvm-dev at lists.llvm.org; Kolton, Sam; Sumner, Brian; Pykhtin, Valery
Subject: Re: [llvm-dev] Implementing cross-thread reduction in the AMDGPU backend
On Wed, Jun 14, 2017 at 5:23 PM, Tom Stellard <tstellar at redhat.com> wrote:
> On 06/14/2017 05:05 PM, Connor Abbott wrote:
>> On Tue, Jun 13, 2017 at 6:13 PM, Tom Stellard <tstellar at red...
2017 Jun 14
5
Implementing cross-thread reduction in the AMDGPU backend
On 06/13/2017 07:33 PM, Matt Arsenault wrote:
>
>> On Jun 12, 2017, at 17:23, Tom Stellard <tstellar at redhat.com <mailto:tstellar at redhat.com>> wrote:
>>
>> On 06/12/2017 08:03 PM, Connor Abbott wrote:
>>> On Mon, Jun 12, 2017 at 4:56 PM, Tom Stellard <tstellar at redhat.com <mailto:tstellar at redhat.com>> wrote:
>>>> On
2017 Jun 15
2
Implementing cross-thread reduction in the AMDGPU backend
On 06/14/2017 05:05 PM, Connor Abbott wrote:
> On Tue, Jun 13, 2017 at 6:13 PM, Tom Stellard <tstellar at redhat.com> wrote:
>> On 06/13/2017 07:33 PM, Matt Arsenault wrote:
>>>
>>>> On Jun 12, 2017, at 17:23, Tom Stellard <tstellar at redhat.com <mailto:tstellar at redhat.com>> wrote:
>>>>
>>>> On 06/12/2017 08:03 PM, Connor