From: Hans-Peter Nilsson <hp@bitrange.com>
To: Daniel Berlin <dan@cgsoftware.com>
Cc: <gcc@gcc.gnu.org>
Subject: Re: Start of guide to writing optimizations for gcc
Date: Sat, 15 Dec 2001 21:30:00 -0000 [thread overview]
Message-ID: <Pine.BSF.4.30.0112152310450.20407-100000@dair.pair.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0112151622130.4671-100000@www.cgsoftware.com>
On Sat, 15 Dec 2001, Daniel Berlin wrote:
> I put the start of a guide to writing optimizations for gcc at
>
> http://www.dberlin.org/gccopt
How about doing this as part of the GCC project, i.e. as part of
gcc documentation? If you think "well, maybe later", then later
you'd have problems getting assignments and whatnot. ... which
might be part of the reason you're not doing this as part of
GCC. (That and docbook vs. texinfo.) The copyright issue is of
course still there, but nobody will notice until it blows up
(perhaps when you want to publish it in paper format). Then
again, IANAL and I'm not even the one of us studying law. :-)
brgds, H-P
next prev parent reply other threads:[~2001-12-16 5:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-15 13:31 Daniel Berlin
2001-12-15 15:03 ` Joseph S. Myers
2001-12-15 21:30 ` Hans-Peter Nilsson [this message]
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.BSF.4.30.0112152310450.20407-100000@dair.pair.com \
--to=hp@bitrange.com \
--cc=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).