| [eigen] Custom memory allocators with eigen |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/eigen Archives
]
- To: eigen <eigen@xxxxxxxxxxxxxxxxxxx>
- Subject: [eigen] Custom memory allocators with eigen
- From: eigen@xxxxxxxxxxxxxxxxxxxx
- Date: Sun, 14 Mar 2021 10:44:08 +0100
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastmail.com; h= from:to:subject:date:message-id:mime-version:content-type; s= fm2; bh=E9uAJn7dLd+SBCNu78RLsW/DDBkzI7KHJw6ytn7qMEM=; b=CO/rkIok iS+E2c6vZhKbTaBx0dwIemr3wbEUSsHRPjmJmf7BDa+jkfIc//Sn/YdFv5X3+VpG xwHTcsXF1gZrNdCmoxMEXHPUa4YIaSFNy9HhVEgIVJFjgQPjs2zbpwSy6xA/+rj1 Xg4xThcawM/JtGLp96MK5Bc9t/AbTIsZLY2f8IaCaDHKcBAfYsrrh9BIWusXgjqM hKF754O9qg9t3OfmYfdza90rhdBF9cohWm6Cy1jt+be3Uhy/k5hJbks9vM+pXbIK MdM300Gf4i3xv4V2fGIFuZ5dFIJfCtj5GqDRczr9Go6xKEEvqsvFZJJsr7ARmbmV ectsmns4sDEbGw==
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:message-id :mime-version:subject:to:x-me-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=E9uAJn7dLd+SBCNu78RLsW/DDBkzI 7KHJw6ytn7qMEM=; b=SXTSKgMh7wwNb7oLvqOwKQYvmXILzWiKOyUz48hUm4euv HmxR+nYXdahMeJnKNf2XDioK7+8Tq6/4zEdyBCbDEHv+G2CbrJKJ0USZR9b83XoJ 7jHQor1qmsea/jTbieRxrmcgHWCJpCfZRygFOX28RNcoCAeOrrgB3zV4PNsX13U3 IZ4ecdLSbhgBIJu2BWCufoc2iAG/xyeiSoNkQxxMKFBqyG22SDtt+F6JHhFXHFiQ +HYhJFdVgcKDYUh76wSzd7ot5jwAWbgyvnPWgjuF8yLokOrpFP+eyGGP7UHGCK1k nIC2e0RmXKAR2av+LBbhBbkvfZOd6w4U+LLBqITqA==
Hi, after inspecting the code I guess the answer is "no", but I wanted
to confirm if I can use a custom allocator with eigen.
I have a piece of code using sparse matrices in which the running time
is dominated by the same allocation/deallocation of some temporaries.
If I could intercept those calls (eigen_malloc, IIRC), I could return a
pointer always pointing to the same block of memory.
--
Alberto