From: James E Wilson <wilson@specifixinc.com>
To: Daniel Berlin <dberlin@dberlin.org>
Cc: Marc Gonzalez-Sigler <marc.gonzalez-sigler@inria.fr>, gcc@gcc.gnu.org
Subject: Re: Pro64-based GPLed compiler
Date: Thu, 30 Jun 2005 21:46:00 -0000 [thread overview]
Message-ID: <42C4683C.3080909@specifixinc.com> (raw)
In-Reply-To: <1120094349.8950.15.camel@linux-009002219098>
Daniel Berlin wrote:
> A bunch of random code #ifdef KEY'd
FYI Pathscale was formerly known as Key Research. So the KEY probably
wouldn't mean anything special here, it is likely just a marker for
local changes.
--
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com
next prev parent reply other threads:[~2005-06-30 21:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-29 15:46 Marc Gonzalez-Sigler
2005-06-29 18:01 ` Vladimir Makarov
2005-06-29 21:28 ` Marc
2005-06-30 1:19 ` Daniel Berlin
2005-06-30 21:46 ` James E Wilson [this message]
2005-06-30 22:23 ` Vladimir Makarov
2005-06-30 22:30 ` Daniel Berlin
2005-07-01 0:17 ` James E Wilson
2005-07-01 2:02 ` Daniel Berlin
2005-07-01 9:24 ` Marc Gonzalez-Sigler
2005-07-01 8:48 ` Marc Gonzalez-Sigler
2005-07-01 6:58 Joost VandeVondele
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=42C4683C.3080909@specifixinc.com \
--to=wilson@specifixinc.com \
--cc=dberlin@dberlin.org \
--cc=gcc@gcc.gnu.org \
--cc=marc.gonzalez-sigler@inria.fr \
/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).