Timeline for CodeWars - Assembly Language - Check List For Value
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 4, 2020 at 19:41 | history | edited | Sep Roland | CC BY-SA 4.0 |
added one missing word
|
| Oct 1, 2020 at 0:07 | comment | added | Jose Fernando Lopez Fernandez | @RedDragonWebDesign The best resource is always going to be an old hand, but if one isn't available, or when you're researching a question before posting on a site like this, compiler output is going to be a great resource because it's literally what would be getting run. I like to compare the output and performance from different optimization levels (particularly size vs. speed), but definitely make sure the C/C++/Rust/etc. code you're compiling is correct (syntactically, semantically, and idiomatically) so you get the best output. In other words, enable all warnings, checks, etc. | |
| Sep 30, 2020 at 22:59 | comment | added | RedDragonWebDesign | Thanks for the detailed reply. I am familiar with godbolt and I've taken a look at its output before.Great tool. So you basically recommend that I run all my C code through that to get an idea of best practices in assembly? Are default settings OK? | |
| Sep 30, 2020 at 16:45 | history | answered | Jose Fernando Lopez Fernandez | CC BY-SA 4.0 |