You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When compiling from assembly, the bcopy instruction either cannot be parsed or is parsed incorrectly.
Scenario 1:
If the instruction is written correctly, e.g. bcopy $26 = $25, 0, $p1, then compilation using patmos-clang throws the error:
error: too few operands for instruction
bcopy $r26 = $r25, 0, $p1
Scenario 2:
If we add a comma to the end of the operand list, e.g. bcopy $26 = $25, 0, $p1, then compilation won't fail, but the instruction is not output to the final object file. I.e. its is just ignored.
Both scenarios also manifest in inline assembly, e.g:
intmain(){
asm(
"bcopy $r26 = $r25, 0, $p1"
);
}
The text was updated successfully, but these errors were encountered:
Just noticed that if the predicate operand is negated (i.e. bcopy $r26 = $r25, 0, !$p1) an error will not be thrown and it seems to be included in the object file correctly.
When compiling from assembly, the
bcopy
instruction either cannot be parsed or is parsed incorrectly.Scenario 1:
If the instruction is written correctly, e.g.
bcopy $26 = $25, 0, $p1
, then compilation usingpatmos-clang
throws the error:Scenario 2:
If we add a comma to the end of the operand list, e.g.
bcopy $26 = $25, 0, $p1,
then compilation won't fail, but the instruction is not output to the final object file. I.e. its is just ignored.Both scenarios also manifest in inline assembly, e.g:
The text was updated successfully, but these errors were encountered: