Displaying 6 results from an estimated 6 matches for "nvptxintrinsics".
2013 Feb 06
4
[LLVMdev] [llvm-tblgen] Two issues: crash case and mysterious double-inclusion case
...0x00000000004071f9
Stack dump:
0. Program arguments: ./llvm-tblgen -gen-tgt-intrinsic NVPTX1.td
Segmentation fault (core dumped)
====
2) Second test case: double inclusion of file, that is definitely included
once:
====
$ ./llvm-tblgen -gen-tgt-intrinsic NVPTX2.td
Included from NVPTX2.td:20:
NVPTXIntrinsics.td:10:1: error: def 'immFloat0' already defined
def immFloat0 : PatLeaf<(fpimm), [{
^
NVPTX1.td differs from NVPTX2.td just in one line:
include "NVPTXIntrinsics.td"
====
Expected behavior
====
1) In first case, where .td file has empty list of intrinsics, the tool
should n...
2013 Feb 07
0
[LLVMdev] [llvm-tblgen] Two issues: crash case and mysterious double-inclusion case
...isterInfo.td:32:14: error: expected declaration in for
foreach i = 0-395 in {
^
> ====
> 2) Second test case: double inclusion of file, that is definitely included
> once:
> ====
>
> $ ./llvm-tblgen -gen-tgt-intrinsic NVPTX2.td
> Included from NVPTX2.td:20:
> NVPTXIntrinsics.td:10:1: error: def 'immFloat0' already defined
> def immFloat0 : PatLeaf<(fpimm), [{
> ^
$ llvm-tblgen -gen-tgt-intrinsic NVPTX2.td
Included from NVPTX2.td:18:
NVPTXRegisterInfo.td:32:14: error: Value list is not of list type
foreach i = 0-395 in {
^
Included from NV...
2012 Nov 01
3
[LLVMdev] [llvm-commits] RFC: Merge branches/R600 into TOT for 3.2 release
...ches
> > for changes I make outside of Target/AMDGPU. Isn't that how Open Source
> > is supposed to work? ;)
>
> Well yeah, but sometimes you still have to ask :). Can the intrinsics be pulled into the target directory ala Targets/MBlaze/MBlazeIntrinsics.td or Targets/NVPTX/NVPTXIntrinsics.td?
>
> > What's the best way to break up the patch? In the past I have divided it up
> > into 4 patches:
> >
> > 1. Core Target files (*TargetMachine, *InstInfo, etc.)
> > 2. Target specific passes
> > 3. .td files
> > 4. Configuration / Intrinsi...
2012 Nov 17
0
[LLVMdev] [llvm-commits] RFC: Merge branches/R600 into TOT for 3.2 release
...gt; for changes I make outside of Target/AMDGPU. Isn't that how Open Source
>>> is supposed to work? ;)
>>
>> Well yeah, but sometimes you still have to ask :). Can the intrinsics be pulled into the target directory ala Targets/MBlaze/MBlazeIntrinsics.td or Targets/NVPTX/NVPTXIntrinsics.td?
>>
>>> What's the best way to break up the patch? In the past I have divided it up
>>> into 4 patches:
>>>
>>> 1. Core Target files (*TargetMachine, *InstInfo, etc.)
>>> 2. Target specific passes
>>> 3. .td files
>>> 4....
2012 Nov 26
5
[LLVMdev] [llvm-commits] RFC: Merge branches/R600 into TOT for 3.2 release
...I make outside of Target/AMDGPU. Isn't that how Open Source
> >>> is supposed to work? ;)
> >>
> >> Well yeah, but sometimes you still have to ask :). Can the intrinsics be pulled into the target directory ala Targets/MBlaze/MBlazeIntrinsics.td or Targets/NVPTX/NVPTXIntrinsics.td?
> >>
> >>> What's the best way to break up the patch? In the past I have divided it up
> >>> into 4 patches:
> >>>
> >>> 1. Core Target files (*TargetMachine, *InstInfo, etc.)
> >>> 2. Target specific passes
> >&g...
2012 Nov 29
0
[LLVMdev] [llvm-commits] RFC: Merge branches/R600 into TOT for 3.2 release
...utside of Target/AMDGPU. Isn't that how Open Source
>>>>> is supposed to work? ;)
>>>>
>>>> Well yeah, but sometimes you still have to ask :). Can the intrinsics be pulled into the target directory ala Targets/MBlaze/MBlazeIntrinsics.td or Targets/NVPTX/NVPTXIntrinsics.td?
>>>>
>>>>> What's the best way to break up the patch? In the past I have divided it up
>>>>> into 4 patches:
>>>>>
>>>>> 1. Core Target files (*TargetMachine, *InstInfo, etc.)
>>>>> 2. Target specific...