Displaying 20 results from an estimated 24 matches for "keyt".
Did you mean:
key
2013 Nov 04
2
[LLVMdev] compile error when using overloaded = operator of DenseMap
...luence operation */
};
}
with the following function definition:
void DataFlowValue::set(DMTy emap) {
ExprMap = *emap; //Line153:
}
When I compile, I get the following error:
/home/zeus/masterLLVM/llvm/include/llvm/ADT/DenseMap.h: In member function
‘void llvm::DenseMapBase<DerivedT, KeyT, ValueT, KeyInfoT>::destroyAll()
[with DerivedT = llvm::DenseMap<{anonymous}::Expression, unsigned int>,
KeyT = {anonymous}::Expression, ValueT = unsigned int, KeyInfoT =
llvm::DenseMapInfo<{anonymous}::Expression>]’:
/home/zeus/masterLLVM/llvm/include/llvm/ADT/DenseMap.h:600:5:
inst...
2013 Nov 04
0
[LLVMdev] compile error when using overloaded = operator of DenseMap
...owing function definition:
>
> void DataFlowValue::set(DMTy emap) {
> ExprMap = *emap; //Line153:
> }
>
> When I compile, I get the following error:
>
> /home/zeus/masterLLVM/llvm/include/llvm/ADT/DenseMap.h: In member function
> ‘void llvm::DenseMapBase<DerivedT, KeyT, ValueT, KeyInfoT>::destroyAll()
> [with DerivedT = llvm::DenseMap<{anonymous}::Expression, unsigned int>, KeyT
> = {anonymous}::Expression, ValueT = unsigned int, KeyInfoT =
> llvm::DenseMapInfo<{anonymous}::Expression>]’:
> /home/zeus/masterLLVM/llvm/include/llvm/ADT/De...
2012 Oct 26
2
[LLVMdev] changes to raw_fd_ostream
...t;\n";
and it'll write out to the file, "Hello Wor" and then seg fault without
assert.
Sadly, this only happens for certain C code, any idea why this might be
occuring?
Also, during build I get a lot of these warnings:llvm/ADT/DenseMap.h: In
copy constructor ‘llvm::DenseMap<KeyT, ValueT, KeyInfoT>::DenseMap(const
llvm::DenseMap<KeyT, ValueT, KeyInfoT>&) [with KeyT = unsigned int, ValueT
= llvm::PointerAlignElem, KeyInfoT = llvm::DenseMapInfo<unsigned int>]’:
I'm guessing I messed up when updating somehow? I just used gmake update.
Thanks.
---------...
2009 Oct 27
1
[LLVMdev] Remove class/struct DenseMapInfo mix
Hello
Visual Studio is complaining about the mix of struct and class.
2>C:\dev\llvm\include\llvm/ADT/ValueMap.h(202) : warning C4099:
'llvm::DenseMapInfo<llvm::ValueMapCallbackVH<KeyT,ValueT,Config,ValueInfoT>>'
: type name first seen using 'struct' now seen using 'class'
2> C:\dev\llvm\include\llvm/ADT/ValueMap.h(251) : see reference to
class template instantiation
'llvm::ValueMapCallbackVH<KeyT,ValueT,Config,ValueInfoT>' being...
2012 Oct 26
0
[LLVMdev] changes to raw_fd_ostream
...out to the file, "Hello Wor" and then seg fault without
> assert.
>
> Sadly, this only happens for certain C code, any idea why this might be
> occuring?
>
> Also, during build I get a lot of these warnings:llvm/ADT/DenseMap.h: In
> copy constructor ‘llvm::DenseMap<KeyT, ValueT, KeyInfoT>::DenseMap(const
> llvm::DenseMap<KeyT, ValueT, KeyInfoT>&) [with KeyT = unsigned int, ValueT
> = llvm::PointerAlignElem, KeyInfoT = llvm::DenseMapInfo<unsigned int>]’:
>
> I'm guessing I messed up when updating somehow? I just used gmake update....
2012 Oct 29
1
[LLVMdev] changes to raw_fd_ostream
...Wor" and then seg fault without
>> assert.
>>
>> Sadly, this only happens for certain C code, any idea why this might be
>> occuring?
>>
>> Also, during build I get a lot of these warnings:llvm/ADT/DenseMap.h: In
>> copy constructor ‘llvm::DenseMap<KeyT, ValueT, KeyInfoT>::DenseMap(const
>> llvm::DenseMap<KeyT, ValueT, KeyInfoT>&) [with KeyT = unsigned int, ValueT
>> = llvm::PointerAlignElem, KeyInfoT = llvm::DenseMapInfo<unsigned int>]’:
>>
>> I'm guessing I messed up when updating somehow? I just us...
2012 Aug 02
2
[LLVMdev] [NVPTX] Strange assertion around BlockToChain.clear(); in Release+Asserts build
Hi,
After building out project in release mode, caught an assertion, which
we have not seen before:
hello_f: /tmp/rpmbuild_debug/BUILD/llvm/build/include/llvm/ADT/DenseMap.h:126:
void llvm::DenseMap<KeyT, ValueT, KeyInfoT>::clear() [with KeyT =
llvm::MachineBasicBlock*, ValueT = <unnamed>::BlockChain*, KeyInfoT =
llvm::DenseMapInfo<llvm::MachineBasicBlock*>]: Assertion `NumEntries
== 0 && "Node count imbalance!"' failed.
Program received signal SIGABRT, Aborted...
2008 Oct 30
6
[LLVMdev] cygwin build problems
...p:3440: error: call of
overloaded `AddInteger(uint32_t)' is ambiguous
.../lib/CodeGen/SelectionDAG/SelectionDAG.cpp:1429: error: no matching
function for call to `max(long unsigned int, unsigned int&)'
.../include/llvm/ADT/DenseMap.h: In member function `void
llvm::DenseMapIterator<KeyT, ValueT, KeyInfoT,
ValueInfoT>::AdvancePastEmptyBuckets() [with KeyT = uint32_t, ValueT =
llvm::Value*, KeyInfoT = llvm::DenseMapInfo<uint32_t>, ValueInfoT =
llvm::DenseMapInfo<llvm::Value*>]':
.../include/llvm/ADT/DenseMap.h:479: instantiated from
`llvm::DenseMapIterator<Ke...
2013 Apr 02
1
[LLVMdev] cyclical dependence between caller and callee in JIT
..., but i get this assertion failure:
%"calling function" = call i32 @X.foo(i32 %read)
F is used in instruction:
%"calling function" = call i32 @X.foo(i32 %read)
mytests: /home/charlesq/third_party/llvm-3.1.src/include/llvm/ADT/ValueMap.h:220:
void llvm::ValueMapCallbackVH<KeyT, ValueT,
Config>::allUsesReplacedWith(llvm::Value*) [with KeyT = const
llvm::Function*; ValueT = {anonymous}::JITEmitter::EmittedCode; Config
= {anonymous}::JITEmitter::EmittedFunctionConfig]: Assertion
`isa<KeySansPointerT>(new_key) && "Invalid RAUW on key of ValueMap<>...
2009 Nov 03
2
[LLVMdev] DenseMap iterator constness fix
...e other way around is now allowed as one
may expect.
The template DenseMapConstIterator is removed and the template
parameter IsConst which specifies whether the iterator is constant is added
to DenseMapIterator.
Actually IsConst parameter is not necessary since the constness can be
determined from KeyT but this is not relevant to the fix and can be
addressed later.
The second patch (DenseMapIterator-clang.patch) corrects clang's usage of
DenseMap iterators.
Best regards,
Victor
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermai...
2009 Nov 04
2
[LLVMdev] DenseMap iterator constness fix
...};
>
> These should probably go into include/llvm/Support/type_traits.h. In
> C++0x, this is named "conditional" (section 20.6.7), so I think you
> should use the same name, despite the standard committee's bad taste.
>
> + DenseMapIterator(const DenseMapIterator<KeyT, ValueT,
> + KeyInfoT, ValueInfoT, false>& I)
>
> This looks like it will make it impossible to copy const_iterators. I
> guess it doesn't because the copy-constructor is auto-generated, but
> please comment that and add tests for i...
2009 Nov 04
2
[LLVMdev] DenseMap iterator constness fix
...o into include/llvm/Support/type_traits.h. In
> >> C++0x, this is named "conditional" (section 20.6.7), so I think you
> >> should use the same name, despite the standard committee's bad taste.
> >>
> >> + DenseMapIterator(const DenseMapIterator<KeyT, ValueT,
> >> + KeyInfoT, ValueInfoT, false>&
> >> I)
> >>
> >> This looks like it will make it impossible to copy const_iterators. I
> >> guess it doesn't because the copy-constructor is auto-generated...
2009 Nov 03
0
[LLVMdev] DenseMap iterator constness fix
...gt; { typedef False Result; };
These should probably go into include/llvm/Support/type_traits.h. In
C++0x, this is named "conditional" (section 20.6.7), so I think you
should use the same name, despite the standard committee's bad taste.
+ DenseMapIterator(const DenseMapIterator<KeyT, ValueT,
+ KeyInfoT, ValueInfoT, false>& I)
This looks like it will make it impossible to copy const_iterators. I
guess it doesn't because the copy-constructor is auto-generated, but
please comment that and add tests for it and for the non-const-...
2012 Aug 03
0
[LLVMdev] [NVPTX] Strange assertion around BlockToChain.clear(); in Release+Asserts build
....
2012/8/3 Dmitry N. Mikushin <maemarcus at gmail.com>:
> Hi,
>
> After building out project in release mode, caught an assertion, which
> we have not seen before:
>
> hello_f: /tmp/rpmbuild_debug/BUILD/llvm/build/include/llvm/ADT/DenseMap.h:126:
> void llvm::DenseMap<KeyT, ValueT, KeyInfoT>::clear() [with KeyT =
> llvm::MachineBasicBlock*, ValueT = <unnamed>::BlockChain*, KeyInfoT =
> llvm::DenseMapInfo<llvm::MachineBasicBlock*>]: Assertion `NumEntries
> == 0 && "Node count imbalance!"' failed.
>
> Program received...
2012 Aug 03
1
[LLVMdev] [NVPTX] Strange assertion around BlockToChain.clear(); in Release+Asserts build
...in <maemarcus at gmail.com>:
>> Hi,
>>
>> After building out project in release mode, caught an assertion, which
>> we have not seen before:
>>
>> hello_f: /tmp/rpmbuild_debug/BUILD/llvm/build/include/llvm/ADT/DenseMap.h:126:
>> void llvm::DenseMap<KeyT, ValueT, KeyInfoT>::clear() [with KeyT =
>> llvm::MachineBasicBlock*, ValueT = <unnamed>::BlockChain*, KeyInfoT =
>> llvm::DenseMapInfo<llvm::MachineBasicBlock*>]: Assertion `NumEntries
>> == 0 && "Node count imbalance!"' failed.
>>
>&...
2009 Nov 04
0
[LLVMdev] DenseMap iterator constness fix
...se should probably go into include/llvm/Support/type_traits.h. In
>> C++0x, this is named "conditional" (section 20.6.7), so I think you
>> should use the same name, despite the standard committee's bad taste.
>>
>> + DenseMapIterator(const DenseMapIterator<KeyT, ValueT,
>> + KeyInfoT, ValueInfoT, false>&
>> I)
>>
>> This looks like it will make it impossible to copy const_iterators. I
>> guess it doesn't because the copy-constructor is auto-generated, but
>> please com...
2009 Nov 09
0
[LLVMdev] DenseMap iterator constness fix
...lvm/Support/type_traits.h. In
>> >> C++0x, this is named "conditional" (section 20.6.7), so I think you
>> >> should use the same name, despite the standard committee's bad taste.
>> >>
>> >> + DenseMapIterator(const DenseMapIterator<KeyT, ValueT,
>> >> + KeyInfoT, ValueInfoT,
>> false>&
>> >> I)
>> >>
>> >> This looks like it will make it impossible to copy const_iterators. I
>> >> guess it doesn't because the copy-...
2019 Jun 21
2
Purpose of Epoch Trackers
...tor<const llvm::Value *,
llvm::StringMapEntry<llvm::Value *> *, llvm::DenseMapInfo<const llvm::Value
*>, llvm::detail::DenseMapPair<const llvm::Value *,
llvm::StringMapEntry<llvm::Value *> *>, false>::operator!=(const
llvm::DenseMapIterator::ConstIterator &) const [KeyT = const llvm::Value *,
ValueT = llvm::StringMapEntry<llvm::Value *> *, KeyInfoT =
llvm::DenseMapInfo<const llvm::Value *>, Bucket =
llvm::detail::DenseMapPair<const llvm::Value *,
llvm::StringMapEntry<llvm::Value *> *>, IsConst = false]: Assertion `(!Ptr
|| isHandleInSync())...
2013 Mar 27
0
[LLVMdev] Fwd: cyclical use between caller and callee
..., but i get this assertion failure:
%"calling function" = call i32 @X.foo(i32 %read)
F is used in instruction:
%"calling function" = call i32 @X.foo(i32 %read)
mytests: /home/charlesq/third_party/llvm-3.1.src/include/llvm/ADT/ValueMap.h:220:
void llvm::ValueMapCallbackVH<KeyT, ValueT,
Config>::allUsesReplacedWith(llvm::Value*) [with KeyT = const
llvm::Function*; ValueT = {anonymous}::JITEmitter::EmittedCode; Config
= {anonymous}::JITEmitter::EmittedFunctionConfig]: Assertion
`isa<KeySansPointerT>(new_key) && "Invalid RAUW on key of ValueMap<>...
2013 Mar 28
0
[LLVMdev] cyclical use between caller and callee
..., but i get this assertion failure:
%"calling function" = call i32 @X.foo(i32 %read)
F is used in instruction:
%"calling function" = call i32 @X.foo(i32 %read)
mytests: /home/charlesq/third_party/llvm-3.1.src/include/llvm/ADT/ValueMap.h:220:
void llvm::ValueMapCallbackVH<KeyT, ValueT,
Config>::allUsesReplacedWith(llvm::Value*) [with KeyT = const
llvm::Function*; ValueT = {anonymous}::JITEmitter::EmittedCode; Config
= {anonymous}::JITEmitter::EmittedFunctionConfig]: Assertion
`isa<KeySansPointerT>(new_key) && "Invalid RAUW on key of ValueMap<>...