-
This issue is either:
a) a missed optimization in the x86-64 backend; or
b) a wrong optimization in the aarch64 backend.
Consider the following code:
```c
#include
#include
bool is_i8(d…
-
Currently, the oscillators in the SB optimizer have the same dtype as the IsingCore model which itself inherits its dtype from the polynomial model defined by the user. Although it makes sense to crea…
-
When generating code the indicated value in complex enums is ignored. In the example `UNIT_UNDEFINED` should be of value 1, but this is missing from the generated code, causing it to have a value of 0…
-
The code contains undefined behavior, such as integer overflows: https://github.com/tigranh/lr_printer/blob/a85bfbc218d410d0cbfb4be14fb3fd10cfd27bc7/lr_printer.hpp#L180 https://github.com/tigranh/lr_p…
-
I don't think it is a bottleneck, we can get to it during an MQ.
If it is a single comparison, even a string comparison, it is most likely ok to leave it as `return m_stringValue == other.m_stringV…
-
| | |
|--------------------|----|
| Bugzilla Link | [PR23887](https://bugs.llvm.org/show_bug.cgi?id=23887) |
| Status | NEW |
| Importance | P normal |
|…
-
This might fall under the category of premature optimization, but I believe that enum fields should be changed from CharFields to IntegerFields. An example of this is the Membership_type on the Member…
-
I tried out the 'CTVsuggest' package, as requested by Achim Zeileis.
For the Optimization task view, it suggested the following packages:
CTVsuggest(taskview = "Optimization", n = 40)
When…
-
AFAIU, repeatedly parsing integers is one of the parts of Microsoft 6502 that saved codespace while costing cycles.
Experience indicates that a large number of literal constants are represented by …
-
#### Feature
The condition codes for performing the `>` and `>=` comparisons on integers should be removed from the Cranelift IR
#### Benefit
Makes the IR more strongly normalizing. At the momen…