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
Not an urgent issue, but something that seems like it may be an easy fix.
Source Code:
constgal8min_poly=0b11101, // Minimal polynomial x^8 + x^4 + x^3 + x^2 + 1generator=0b10; // Generator of Galois field
movcc output:
galois.c:14: `0b11101' is a preprocessing number but an invalid integer constant
galois.c:15: `0b10' is a preprocessing number but an invalid integer constant
I'm just a cryptography student trying to obfuscate my algorithms for a ctf I'm working on. The problem is easily fixed when I make the change to decimal representation, but... it'd be nice to have more readable source code that is compatible with movcc.
working source:
constgal8min_poly=39, // Minimal polynomial x^8 + x^4 + x^3 + x^2 + 1generator=2; // Generator of Galois field
I have never contributed to a github project before, but I would be happy to take a look at the source, attempt an edit, and submit a pull request if you do that sort of thing..
The text was updated successfully, but these errors were encountered:
The front end lcc follows ANSI C, whereas binary constants (0b prefix) are non-standard and certainly not ANSI.
These will become part of the C standard only in C23; meanwhile they only exist as extensions in gcc or llvm.
Not an urgent issue, but something that seems like it may be an easy fix.
Source Code:
movcc output:
I'm just a cryptography student trying to obfuscate my algorithms for a ctf I'm working on. The problem is easily fixed when I make the change to decimal representation, but... it'd be nice to have more readable source code that is compatible with movcc.
working source:
I have never contributed to a github project before, but I would be happy to take a look at the source, attempt an edit, and submit a pull request if you do that sort of thing..
The text was updated successfully, but these errors were encountered: