Displaying 3 results from an estimated 3 matches for "ilist_node_base".
Did you mean:
_list_node_base
2015 Oct 21
3
ilist/iplist are broken (maybe I'll fix them?)
...s
that you need to check that I's valid. OTOH, N->getIterator() is very
clear (and is probably usually written as `auto I = N->getIterator()`,
which looks pretty nice).
> Note that after my ilist changes, this implicit conversion will look
> basically like this:
> --
> struct ilist_node_base {
> ilist_node_base *Prev;
> ilist_node_base *Next;
> };
> struct ilist_iterator_base {
> ilist_node_base *N;
> };
> template <typename NodeTy>
> class ilist_iterator : private ilist_iterator_base {
> operator pointer() const { return static_cast<NodeTy *...
2015 Oct 20
2
ilist/iplist are broken (maybe I'll fix them?)
I think the implicit iterator conversions are much less important now that
we have range based for loops, but I still like having them.
On Tue, Oct 20, 2015 at 11:13 AM, Duncan P. N. Exon Smith via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
>
> > On 2015-Oct-07, at 17:57, Duncan P. N. Exon Smith <dexonsmith at apple.com>
> wrote:
> >
> > I've been
2019 May 25
3
llvm pass
Hi list,
I have several questions about LLVM pass.
1) Is building a custom LLVM pass out-of-source not recommended?
The official document only contains instructions about in-source build (http://llvm.org/docs/WritingAnLLVMPass.html <http://llvm.org/docs/WritingAnLLVMPass.html>).
2) opt (ver >= 4) with custom pass libraries does not work as before. When I have a simple custom LLVM pass