Displaying 9 results from an estimated 9 matches for "valueinfot".
2017 Apr 10
2
clang build failures using Visual Studio
...\program files (x86)\microsoft visual
studio\2017\community\VC\Tools\MSVC\14.10.25017\include\xmemory(126): error
C2678: binary '*': no operator found which takes a left-hand operand of
type 'const
llvm::detail::DenseSetImpl<ValueT,llvm::DenseMap<ValueT,llvm::detail::DenseSetEmpty,ValueInfoT,llvm::detail::DenseSetPair<ValueT>>,ValueInfoT>::Iterator'
(or there is no acceptable conversion)
with
[
ValueT=const llvm::Record *,
ValueInfoT=llvm::DenseMapInfo<const llvm::Record *>
]
C:\deps\llvm-4.0....
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 compiled
Below you can...
2008 Oct 30
6
[LLVMdev] cygwin build problems
...verloaded `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<KeyT, ValueT, KeyInfoT, ValueInf...
2009 Nov 04
2
[LLVMdev] DenseMap iterator constness fix
...its.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->const
> conversion to unittests/ADT/DenseMapTes...
2009 Nov 04
2
[LLVMdev] DenseMap iterator constness fix
..."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->...
2009 Nov 03
0
[LLVMdev] DenseMap iterator constness fix
...de/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->const
conversion to unittests/ADT/DenseMapTest.cpp.
Otherwise, the p...
2009 Nov 04
0
[LLVMdev] DenseMap iterator constness fix
...++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->const
>> conversion...
2009 Nov 03
2
[LLVMdev] DenseMap iterator constness fix
Dear all,
The first of the proposed patches (DenseMapIterator.patch) forbids implicit
conversion of DenseMap::const_iterator to DenseMap::iterator which was
possible because DenseMapIterator inherited (publicly) from
DenseMapConstIterator. Conversion the other way around is now allowed as one
may expect.
The template DenseMapConstIterator is removed and the template
parameter IsConst which
2009 Nov 09
0
[LLVMdev] DenseMap iterator constness fix
...l" (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...