Re: dual line backtraces for i386.

>Please...
>
>	char space = '\t';
>	[...]
>	printk("%c", space);
>	space = ('\t' + '\n') - space;
>
>Even fewer instructions and actually somewhat understandable.

I see the days of kernelgolf coming...



Jan Engelhardt
-- 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • Re: dual line backtraces for i386.
    • From: Chuck Ebbert <[email protected]>
  • Re: dual line backtraces for i386.
    • From: Jan Engelhardt <[email protected]>
  • Re: dual line backtraces for i386.
    • From: Bob Copeland <[email protected]>
  • Re: dual line backtraces for i386.
    • From: Mitchell Blank Jr <[email protected]>

• Prev by Date: sparse triggers OOM killer
• Next by Date: Re: [PATCH] protect remove_proc_entry
• Previous by thread: Re: dual line backtraces for i386.
• Next by thread: heads up: Ubuntu Breezy GCC 4.0.2-prerelease miscompiles 2.6.15 with -Os
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]