Displaying 20 results from an estimated 10000 matches similar to: "[LLVMdev] OpenCL with device fission to LLVM-IR"
2013 Dec 09
0
[LLVMdev] DebugInfo: DW_AT_GNU_ranges_base in non-fission
On Mon, Dec 9, 2013 at 9:47 AM, David Blaikie <dblaikie at gmail.com> wrote:
> It looks like we only attach the GNU_ranges_base to skeleton CUs, and
> never use the attribute under non-fission. Is that right? It's not
> obvious to me why we'd want to only include this under fission, but I
> admittedly don't fully understand it anyway.
>
So we're not
2013 Dec 09
1
[LLVMdev] DebugInfo: DW_AT_GNU_ranges_base in non-fission
On Mon, Dec 9, 2013 at 11:48 AM, Eric Christopher <echristo at gmail.com> wrote:
> On Mon, Dec 9, 2013 at 9:47 AM, David Blaikie <dblaikie at gmail.com> wrote:
>> It looks like we only attach the GNU_ranges_base to skeleton CUs, and
>> never use the attribute under non-fission. Is that right? It's not
>> obvious to me why we'd want to only include this
2013 Dec 09
2
[LLVMdev] DebugInfo: DW_AT_GNU_ranges_base in non-fission
It looks like we only attach the GNU_ranges_base to skeleton CUs, and
never use the attribute under non-fission. Is that right? It's not
obvious to me why we'd want to only include this under fission, but I
admittedly don't fully understand it anyway.
- Dave
2012 Mar 24
0
The review of Earth fission - Task design Dave'Fargo'Kosak
As the the first review series of "WoW: the earth fission", we invited the chief task of WoW: theesigner Dave "Fargo" Kosak to discuss with you about his views on the mission design about earth fission.
Q: And we will talk about the advantages and disadvantages in the region of 80-85 level?
We aim to create the global catastrophe atmosphere; we apportioned the top region to
2017 May 04
2
DWARF Fission + ThinLTO
On Thu, May 4, 2017 at 7:22 AM, Rafael Avila de Espindola via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> David Blaikie via llvm-dev <llvm-dev at lists.llvm.org> writes:
>
> > So Dehao and I have been dealing with some of the nitty gritty details of
> > debug info with ThinLTO, specifically with Fission(Split DWARF).
> >
> > This applies to LTO as
2012 Sep 06
0
[LLVMdev] "SPIR" ? A Standard Portable IR for OpenCL Kernel Language
> -----Original Message-----
> From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu]
> On Behalf Of Vikram Adve
> Sent: Thursday, September 06, 2012 3:52 PM
> To: llvmdev at cs.uiuc.edu
> Subject: Re: [LLVMdev] "SPIR" ? A Standard Portable IR for OpenCL
> Kernel Language
>
> On Sep 6, 2012, at 4:33 PM, "Ouriel, Boaz"
2017 May 05
2
DWARF Fission + ThinLTO
> On May 4, 2017, at 4:53 PM, David Blaikie <dblaikie at gmail.com> wrote:
>
> Alrighty, a little fuzzy on how best to implement this - Adrian, you've probably got the most context here as to how to wrangle this.
>
> My first attempt was in IRMover.cpp, IRLinker::linkFunctionBody - after metadata is copied over, create a new subprogram derived from Dst.getSubprogram,
2017 May 03
4
DWARF Fission + ThinLTO
So Dehao and I have been dealing with some of the nitty gritty details of
debug info with ThinLTO, specifically with Fission(Split DWARF).
This applies to LTO as well, so I won't single out ThinLTO here.
1) Multiple CUs in a .dwo file
Clang/LLVM produces a CU for each original source file - these CUs are kept
through IR linking (thin or full) and produced as distinct CUs in the
resulting
2012 Mar 05
0
[LLVMdev] problem in implementing loop fission using ModulePass
Hi,
I am trying to implement my own Loop fission transformations in llvm.
But to find circular dependency, i think i have to use
LoopDependenceAnalysis.
I am using ModulePass.
In this pass I am getting LoopInfo and Loops. but when I try to use
LoopDependenceAnalysis
It throws segmentation fault.
the example shows what i want to do :
for(int i = 0; i< n ; i++){
s1 : a[i]
2012 Sep 06
2
[LLVMdev] "SPIR" ? A Standard Portable IR for OpenCL Kernel Language
On Sep 6, 2012, at 4:33 PM, "Ouriel, Boaz" <boaz.ouriel at intel.com> wrote:
> **** Introduction ****
> Lately, Khronos has ratified a new provisional specification which is called SPIR.
> This specification standardizes an intermediate representation for the OpenCL kernel language.
> It is based on LLVM infrastructure and this is why I am sending this mail to the
2012 Sep 06
2
[LLVMdev] "SPIR" – A Standard Portable IR for OpenCL Kernel Language
Greetings All,
I am sending this mail on behalf of the OpenCL Khronos members.
**** Introduction ****
Lately, Khronos has ratified a new provisional specification which is called SPIR.
This specification standardizes an intermediate representation for the OpenCL kernel language.
It is based on LLVM infrastructure and this is why I am sending this mail to the LLVM mailing list.
Khronos members
2017 May 04
2
DWARF Fission + ThinLTO
> On May 3, 2017, at 7:43 PM, Adrian Prantl via llvm-dev <llvm-dev at lists.llvm.org> wrote:
>
>>
>> On May 3, 2017, at 2:59 PM, David Blaikie <dblaikie at gmail.com <mailto:dblaikie at gmail.com>> wrote:
>>
>>
>>
>> On Wed, May 3, 2017 at 2:09 PM Adrian Prantl <aprantl at apple.com <mailto:aprantl at apple.com>> wrote:
2017 May 03
3
DWARF Fission + ThinLTO
On Wed, May 3, 2017 at 2:09 PM Adrian Prantl <aprantl at apple.com> wrote:
>
> > On May 3, 2017, at 2:00 PM, David Blaikie <dblaikie at gmail.com> wrote:
> >
> > So Dehao and I have been dealing with some of the nitty gritty details
> of debug info with ThinLTO, specifically with Fission(Split DWARF).
> >
> > This applies to LTO as well, so I
2013 Jan 18
2
[LLVMdev] How to run SPEC200 benhmark in LLVM
Hello,
I want to run SPEC2000 benchmark in LLVM to check correctness of a llvm
module which I wrote. How to run SPEC2000 benchmark in LLVM?
Unnikrishnan C
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
2012 May 07
1
Value of Hurst exponent (R/S) method > 1
Hello,
I'm using fArma package to estimate the value of Hurst exponent using R/S
method. However, for a certain set of data I get H ~ 1.8. How do I
interpret this?
Following are the output that I get for this set:
> mean(data[,2])
[1] 400.5433
> sd(data[,2])
[1] 1139.786
>
> rsFit(data[,2], levels = 64)
Title:
Hurst Exponent from R/S Method
Call:
rsFit(x = data[, 2], levels
2012 Apr 25
1
Help on time series & Hurst exponent
Hello,
I'm an absolute beginner with R. I'm hoping to do some time-series analysis
on my data. The data looks like
#time value
18 153
20 426
70 7
83 130
84 7
and so on where time could be in seconds or hours or days (not all at the
same time). How could I import such a file to R and do some simple stuff
(say plot the values)? As per the tutorials on time series, I could use the
ts()
2008 Dec 16
0
[LLVMdev] OpenCL Frontend
On Tuesday 16 December 2008 12:21:24 Timothy Baldridge wrote:
> There seems to be some interest these days in OpenCL. However for some
> projects, a issue they face to adopting OpenCL is requirements of
> maintaining two source trees: one for normal C code (for use on
> systems without OpenCL support or poor OpenCL performance) and another
> for OpenCL.
>
> I am interested in
2008 Dec 16
2
[LLVMdev] OpenCL Frontend
Awesome, is the development of this being tracked somewhere? And is
there a way I can get involved?
Timothy
On Tue, Dec 16, 2008 at 11:52 AM, Zack Rusin <zack at tungstengraphics.com> wrote:
> On Tuesday 16 December 2008 12:21:24 Timothy Baldridge wrote:
>> There seems to be some interest these days in OpenCL. However for some
>> projects, a issue they face to adopting
2008 Dec 16
2
[LLVMdev] OpenCL Frontend
There seems to be some interest these days in OpenCL. However for some
projects, a issue they face to adopting OpenCL is requirements of
maintaining two source trees: one for normal C code (for use on
systems without OpenCL support or poor OpenCL performance) and another
for OpenCL.
I am interested in using LLVM to create a OpenCL frontend for
multicore CPUs. Now that the spec is out, we have a
2013 Jan 09
0
[LLVMdev] Portable OpenCL (pocl) v0.7 released
Portable OpenCL aims to be an efficient open source (MIT-licensed)
implementation of the OpenCL 1.2 standard.
In addition to producing an easily portable open source OpenCL
implementation, another major goal of the project is improving
performance portability of OpenCL programs with compiler
optimizations, reducing the need for target-dependent manual
optimizations.
At the core of pocl is the