From: Daniel Berlin <dan@cgsoftware.com>
To: <gcc@gcc.gnu.org>
Subject: Start of guide to writing optimizations for gcc
Date: Sat, 15 Dec 2001 13:31:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.33.0112151622130.4671-100000@www.cgsoftware.com> (raw)
I put the start of a guide to writing optimizations for gcc at
http://www.dberlin.org/gccopt
I know it's currently trivial, but i only work on it during very spare
time.
It is not intended to be an intro for beginners to compiler optimization.
It is intended to describe to someone who understands compiler
optimizations, and works on other compilers, how to do things they want to
do, in gcc.
The docbook source for it is at
http://www.dberlin.org/gccopt/optimize.sgml (it's really an xml file,
however).
Feel free to write a few lines, or whatever, and send it to me. I'll
happily integrate it and add your name to the list of contributors. If
you don't do docbook, that's okay, just send me the text, and i'll mark it
up for you.
While i'm happy to take contributions, please don't send me gripes or
complaints. I'm quite aware it sucks right now. It's a start.
Contribute, and maybe it won't suck anymore.
--Dan
next reply other threads:[~2001-12-15 21:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-15 13:31 Daniel Berlin [this message]
2001-12-15 15:03 ` Joseph S. Myers
2001-12-15 21:30 ` Hans-Peter Nilsson
2001-12-16 10:42 ` Daniel Berlin
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=Pine.LNX.4.33.0112151622130.4671-100000@www.cgsoftware.com \
--to=dan@cgsoftware.com \
--cc=gcc@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).