This bugzilla service is closed. All entries have been migrated to https://gitlab.com/libeigen/eigen
Bug 1759 - Check whether blocking is worthwhile for custom types
Summary: Check whether blocking is worthwhile for custom types
Status: CONFIRMED
Alias: None
Product: Eigen
Classification: Unclassified
Component: Core - matrix products (show other bugs)
Version: 3.4 (development)
Hardware: All All
: Normal Optimization
Assignee: Nobody
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 3.x
  Show dependency tree / graph
 
Reported: 2019-10-14 12:44 UTC by Christoph Hertzberg
Modified: 2019-12-04 18:50 UTC (History)
2 users (show)


Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Christoph Hertzberg 2019-10-14 12:44:12 UTC 
Related to Bug 1758 (and https://stackoverflow.com/questions/58366939/eigen3-boost-mpfr-segfault-when-alignment-is-disabled), it may actually not worth to use blocking algorithms for custom types, especially if sub-optimal cache access is less expensive than copying.

This not only applies to GEMM/GEMV products but also, e.g., triangular solvers.
Comment 1 Gael Guennebaud 2019-10-14 20:32:25 UTC 
Yes that's one of the many items I have had in my mind for years...
Comment 2 Nobody 2019-12-04 18:50:24 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to gitlab.com's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.com/libeigen/eigen/issues/1759.
Note You need to log in before you can comment on or make changes to this bug.