Bug 732 - non-essential optimisation of Partitioned SimdSignal to reduce gate count
Summary: non-essential optimisation of Partitioned SimdSignal to reduce gate count
Status: CONFIRMED
Alias: None
Product: Libre-SOC's first SoC
Classification: Unclassified
Component: Source Code (show other bugs)
Version: unspecified
Hardware: PC Linux
: Lowest critical
Assignee: Jacob Lifshay
URL:
Depends on: 458 713 716 731
Blocks:
  Show dependency treegraph
 
Reported: 2021-10-22 00:28 BST by Luke Kenneth Casson Leighton
Modified: 2021-10-22 00:38 BST (History)
1 user (show)

See Also:
NLnet milestone: ---
total budget (EUR) for completion of task and all subtasks: 0
budget (EUR) for this task, excluding subtasks' budget: 0
parent task for budget allocation:
child tasks for budget allocation:
The table of payments (in EUR) for this task; TOML format:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Luke Kenneth Casson Leighton 2021-10-22 00:28:18 BST
see https://bugs.libre-soc.org/show_bug.cgi?id=731#c23 for context

SwizzledSimdValue has emerged as an optimisation that, once SimdSignal
version 1 has moved off of critical path and allowed multiple other
developers to proceed with converting ALUs over to it, will become
a high priority for reducing gate count.

however as an optimisation it is currently classified as non-essential
due to SimdSignal being a far higher priority critical path task.

therefore this bugreport is being created with a series of high priority
blockers that is it absolutely essential to complete first in order to
move SimdSignal off off critical path, at which point this task's
priority can be altered.

this task will also be a "critical blocker" for the 2nd ASIC to make
sure that it does get done, but done at an appropriately-scheduled
time.
Comment 1 Luke Kenneth Casson Leighton 2021-10-22 00:38:51 BST
setting a very weird combination of "critical" importance but LOW priority,
to recognise the fact that completing a version 1 SimdSignal is a much
higher (critical path) priority.

(edit: i also need to work out where the heck to get some budget from,
for this.  i know. NGI POINTER will do.  solve that one later)