movfuscator
Cura
Our great sponsors
movfuscator | Cura | |
---|---|---|
82 | 461 | |
9,013 | 5,824 | |
- | 3.8% | |
0.0 | 10.0 | |
about 1 year ago | 7 days ago | |
C | Python | |
GNU General Public License v3.0 or later | GNU Lesser General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
movfuscator
- M/o/Vfuscator: The single instruction C compiler (2020)
-
controversialOpinion
Everything can be reduced to assignments. https://github.com/xoreaxeaxeax/movfuscator
- M/o/Vfuscator: The single instruction C compiler
-
Subtraction Is Functionally Complete
However, the movfuscator as implemented does still require a sigaction(2) syscall to set up a signal handler, under the justifications that "it is not actually part of the program" and that "if we were in ring 0, we wouldn't need help from the kernel" [0]. However, the latter part seems a little dubious to me: without the help of the kernel running non-MOV instructions, you'd never be able to escape from 16-bit real mode into 32-bit protected mode, since you wouldn't be able to load a valid GDT with the LGDT instruction (as far as I am aware).
[0] https://github.com/xoreaxeaxeax/movfuscator/blob/90a49f31219...
-
The bigger the interface, the weaker the abstraction
I _think_ the idea is thinking of an "interface" as "something that you use as a way to interact with something from outside an abstraction". I'd summarize their argument as reasoning that if the goal of an abstraction is to avoid having to care about the internal details of something, an interface is a way to expose a subset of ways to interact with it, and the more you expand it, the more it exposes the internals of the thing being abstracted. I don't think they necessarily mean this only in terms of programming, but you could apply this argument to a programming language interface; if you use an interface for interacting with something instead of its direct functionality, each additional method you add to the interface exposes more details of the inner value, which makes it less of an abstraction.
Assuming my interpretation is correct, I'm not sure I totally buy this argument because there doesn't seem to be an obvious way to define the "size" of an interface where it holds true. The naive way to define the size would be number of methods, but I'd argue that methods can vary so much in terms of the amount of cognitive overhead they "expose" to the user that it's not very meaningful. Consider the Movfuscator compiler[0], which compiles code into binaries only using MOV x86 instructions because it happens to be Turing complete; as complex as it might be to learn x86 assembly as a whole and start writing programs directly in it, I'm dubious that trying to do so only with MOV would somehow be easier. Put another way, an x86 instruction set that only contains the MOV instruction is not a "stronger" abstraction than the actual one because it _introduces_ complexity that doesn't exist in the original. Does adding an ADD instruction alongside MOV increase the strength of the abstraction, or weaken it? I don't think there's an answer that we'd immediately all agree on for this sort of thing.
Ultimately, I think trying to measure interfaces through the number of methods they expose is similar to trying to measure code by the number of lines in it; while there are some extreme cases where we'd likely all agree (e.g. for a fizzbuzz implementation, having 10 lines of code is probably better than thousands of lines of code[1]), we can't really come up with a good objective metric because the "target" number is based on the complexity of what you're trying to define, and we don't have a way of quantifying that complexity. I think the ideas here are still super interesting though, not because they have definitive right or wrong answers, but because thinking about stuff like this overall improves one's ability to write good software for usage by other programmers.
[0]: https://github.com/xoreaxeaxeax/movfuscator
- The M/o/Vfuscator contains a complete mov-only floating point emulator. Since it is approximately 500,000 instructions, you must explicitly link to it if you need it
-
Can the RISC instruction set be simplified even further?
The mov instruction in x86-64 is Turing complete. Someone even made a C compiler using only mov.
-
This is definitely not the best way to initialize an array
Are you sure they didn't use the MOVFUSCATOR?
-
Can every function defined in popular libraries/frameworks be traced back to primitive data types, conditional statements and loops?
Yep. In fact you can reduce everything to just one simple assembly instruction.
- I am going to learn goto
Cura
-
What could be causing these artifacts?
Are you using Cura?
-
Confused by Start (and End) G-Code Macros
EDIT2: Turns out one of my problems was dodgy End code in Cura [5.4.0] Questionable end gcode in some default profiles for Anycubic printers · Issue #16621 · Ultimaker/Cura (github.com)
-
💫 Cura 5.5 💫 ~ With Gradual Flow settings and Grid Placement ⏹️
Full release notes and new Cura downloads can be found here https://github.com/Ultimaker/Cura/releases/tag/5.5.0
-
Creality Print vs Cura: Speed
So I'm using beta version of Cura (5.5.0) with V3 SE profile from https://github.com/Ultimaker/Cura/pull/16796 and I just figured out that Creality print is way faster than Cura. As far as I can see, settings are almost identical; print speed is set to 180mm/s in both programs. I'm using stock PLA profile in Creality print and eSun pla+ profile in Cura - same temperature, infill, walls and fan settings.
-
Cura not responding on Windows
github.com/Ultimaker/Cura/issues for a bug report including Windows version.
-
New Feature for Cura?
In this case, Cura is an open source project, so the most straightforward way of submitting a feature request would be by creating an Issue in the code repository, where you can explain your idea along with why it’s important to you, who else you think it could be valuable to, and what you want both minimally and ideally.
-
Updated to Cura 5.4 and it wiped everything, now I cannot select Ender 3 S1 Pro. Any suggestions?
If you're using the Startup Optimizer plugin, try disabling it temporarily - it can occasionally interfere with the list of available printers. Should that not help you could manually re-insert the profile by copying this JSON into the appropriate directory (eg C:\Program Files\UltiMaker Cura 5.4.0\share\cura\resource\definitions).
-
✨ Cura 5.4 ✨ ~ New Tree Supports and Smart Brim 🌳🐉
This reminds me of this known issue we mentioned in the changelog: Support Brim is missing if the Buildplate Adhesion is set to None. We are tracking reports here.
-
Straight lines on arcs xy axis
Yes..there's some sort of bug in 5.3..5.2 is ok, the developers are working on a patch for the new version: https://github.com/Ultimaker/Cura/issues/14811
- How do I improve my prints
What are some alternatives?
demovfuscator - A work-in-progress deobfuscator for movfuscated binaries [Moved to: https://github.com/leetonidas/demovfuscator]
mks-wifi-plugin - MKS wifi plugin for Cura
obfuscator
klipper - Klipper is a 3d-printer firmware
Molebox - MoleBox lets you convert your application into an all-sufficient stand-alone executable, containing everything needed: components, media assets, registry entries.
PrusaSlicer - G-code generator for 3D printers (RepRap, Makerbot, Ultimaker etc.)
onelinerizer - Shamelessly convert any Python 2 script into a terrible single line of code
Ellis-PIF-Profile - This repo has moved to https://github.com/AndrewEllis93/Ellis-SuperSlicer-Profiles
sectorlisp - Bootstrapping LISP in a Boot Sector
Calibration-Shapes - A Cura plugin that adds simple shapes (cube, cylinder, tube) and also 24 Calibration and test parts + 7 Postprocessing scripts
Unity-game-hacking - A guide for hacking unity games
Marlin - Marlin is an optimized firmware for RepRap 3D printers based on the Arduino platform. Many commercial 3D printers come with Marlin installed. Check with your vendor if you need source code for your specific machine.