From: Adrian von Bidder <avbidder@fortytwo.ch>
To: linux-kernel@vger.kernel.org
Subject: Re: How to write elegant C coding (certainly OT)
Date: Wed, 5 Jan 2005 16:17:52 +0100 [thread overview]
Message-ID: <200501051617.58150@fortytwo.ch> (raw)
In-Reply-To: <20050105081415.GH26051@parcelfarce.linux.theplanet.co.uk>
[-- Attachment #1: Type: text/plain, Size: 713 bytes --]
On Wednesday 05 January 2005 09.14, Al Viro wrote:
> On Wed, Jan 05, 2005 at 03:49:07PM +0800, Coywolf Qi Hunt wrote:
> > I'd say better to study compile theory and a kind of compiler source
> > code.
>
> Yes, gcc source definitely makes a great cautionary tale about the need
> of writing elegant code and dreadful results of not doing so.
LOL
I specifically recommend the ARM backend. It was copied from some other
RISC target, then a ARM thumb (16bit instruction width) backend was split
from that, and finally the thumb and 32bit backends were merged again,
apparently without removing much of the duplicated code.
Fun.
-- vbi
--
featured link: http://fortytwo.ch/gpg/subkeys
[-- Attachment #2: Type: application/pgp-signature, Size: 388 bytes --]
prev parent reply other threads:[~2005-01-05 15:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-05 6:44 How to write elegant C coding krishna
2005-01-05 7:49 ` Coywolf Qi Hunt
2005-01-05 8:14 ` Al Viro
2005-01-05 15:17 ` Adrian von Bidder [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200501051617.58150@fortytwo.ch \
--to=avbidder@fortytwo.ch \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome