Skip to main content
We’ve updated our Terms of Service. A new AI Addendum clarifies how Stack Overflow utilizes AI interactions.
Code Golf

Timeline for Shortest code to throw SIGILL

Current License: CC BY-SA 3.0

43 events
when toggle format what by license comment
Jul 1 at 1:28 answer added macOSisthebestOS timeline score: 2
May 22, 2021 at 21:59 comment added Criggie @BenjaminWang there isn't one here, yet. That language really does deserve it's name.
May 22, 2021 at 21:09 comment added Benjamin Wang @Criggie where is the brainfuck entry? I don’t see it.
May 22, 2021 at 19:27 answer added NoLongerBreathedIn timeline score: 1
Jan 29, 2021 at 16:20 answer added Teodor Maxim timeline score: 4
Mar 31, 2018 at 4:49 answer added l4m2 timeline score: 4
Mar 11, 2018 at 18:50 answer added MD XF timeline score: 2
Feb 27, 2018 at 3:10 answer added MD XF timeline score: 4
Feb 27, 2018 at 2:47 answer added MD XF timeline score: 3
May 1, 2017 at 9:19 vote accept univalence
Apr 13, 2017 at 12:38 history edited Community Bot
replaced http://codegolf.stackexchange.com/ with https://codegolf.stackexchange.com/
Feb 25, 2017 at 22:22 comment added Criggie Sometimes I look for the brainfuck entry, just to marvel at how it lives up to its name. Honestly I was expecting someone would have come up with a negative-length brainfuck submission, just cos.
Dec 1, 2016 at 20:56 answer added habs timeline score: 5
Nov 27, 2016 at 0:03 answer added user42682 timeline score: 9
Nov 23, 2016 at 16:04 comment added user60199 *people posting old programs they had that didn't work*
Nov 23, 2016 at 4:07 answer added apricot boy timeline score: 5
Nov 22, 2016 at 18:30 comment added univalence Now please explain me why I have even more votes then the SIGSEGV question? XD
Nov 22, 2016 at 18:26 history edited univalence CC BY-SA 3.0
added 12 characters in body
Nov 22, 2016 at 18:26 comment added univalence @CarstenS Uh. Yes, of course I mean that.
Nov 21, 2016 at 23:01 answer added user8397947 timeline score: 13
Nov 21, 2016 at 22:57 answer added fluffy timeline score: 6
Nov 21, 2016 at 21:54 history edited Oliver Ni CC BY-SA 3.0
added 3 characters in body
Nov 21, 2016 at 17:13 answer added Torkel Bjørnson-Langen timeline score: 22
Nov 21, 2016 at 17:11 comment added OrangeDog For any hardware that can raise SIGILL, the answer will be the same as the instruction length. Just put an illegal instruction somewhere and try to execute it. The only interesting thing will be the convoluted toolchain involved.
Nov 21, 2016 at 14:44 answer added Eric Towers timeline score: 22
Nov 21, 2016 at 13:50 answer added Florian Castellane timeline score: 7
Nov 21, 2016 at 12:21 answer added Torkel Bjørnson-Langen timeline score: 5
Nov 20, 2016 at 22:32 history tweeted twitter.com/StackCodeGolf/status/800466976657260544
Nov 20, 2016 at 18:36 answer added NobodyNada timeline score: 49
Nov 20, 2016 at 16:05 answer added Dennis timeline score: 93
Nov 20, 2016 at 15:47 answer added maservant timeline score: 19
Nov 20, 2016 at 15:33 answer added anatolyg timeline score: 15
Nov 20, 2016 at 13:39 answer added daniero timeline score: 7
Nov 20, 2016 at 13:35 answer added user42643 timeline score: 6
Nov 20, 2016 at 11:37 answer added user62131 timeline score: 119
Nov 20, 2016 at 11:04 answer added user62131 timeline score: 11
Nov 20, 2016 at 11:00 answer added user62131 timeline score: 25
Nov 20, 2016 at 10:56 comment added univalence @ais523 Everything is allowed.
Nov 20, 2016 at 10:04 comment added Erik the Outgolfer It really does say Illegal instruction (core dumped).
Nov 20, 2016 at 9:59 answer added user62131 timeline score: 8
Nov 20, 2016 at 9:56 answer added user62131 timeline score: 28
Nov 20, 2016 at 9:43 comment added user62131 You might want to clarify whether the instruction has to be generated by the kernel or not. In particular, do you want to allow the program just generating it directly using the libc call raise(SIGILL)?
Nov 20, 2016 at 9:31 history asked univalence CC BY-SA 3.0
toggle format

AltStyle によって変換されたページ (->オリジナル) /