Timeline for Default for Code Golf: Input/Output methods
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 21, 2023 at 11:39 | comment | added | Peter Cordes | Update on calling conventions: you don't have to use a standard C calling convention. Your language is assembly / machine code, so presumably that's the caller's language as well. They can pass args and take return value(s) in any registers including FLAGS on machines with condition codes, as discussed in Tips for golfing in x86/x64 machine code | |
| Jun 11, 2017 at 4:14 | comment | added | user62131 | This needs clarification: can we use any register, or only the ones that would be specified to be used by the ABI? | |
| Jan 1, 2017 at 7:06 | comment | added | Peter Cordes | If you golf with x86-64, the standard calling conventions already pass args in registers. So you can just write a normal function that's callable from compiler-generated code. | |
| Dec 31, 2016 at 21:19 | comment | added | yyny | @lirtosiast I believe the programming language used has to be defined before the challenge starts. | |
| Jul 6, 2016 at 0:31 | comment | added | cat | @lirtosiast Good for code colf then. I don't see how that's different from golfing languages with prefilled vars | |
| Mar 15, 2016 at 17:10 | comment | added | lirtosiast | There's potential for abuse. What if someone creates a machine with a million different special-purpose registers? | |
| Feb 20, 2016 at 22:33 | history | answered | lynn | CC BY-SA 3.0 |