public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Daniel Berlin <dberlin@dberlin.org>
To: Vladimir Makarov <vmakarov@redhat.com>
Cc: Marc Gonzalez-Sigler <marc.gonzalez-sigler@inria.fr>, gcc@gcc.gnu.org
Subject: Re: Pro64-based GPLed compiler
Date: Thu, 30 Jun 2005 01:19:00 -0000	[thread overview]
Message-ID: <1120094349.8950.15.camel@linux-009002219098> (raw)
In-Reply-To: <42C2E1DD.9090508@redhat.com>

On Wed, 2005-06-29 at 14:01 -0400, Vladimir Makarov wrote:
> Marc Gonzalez-Sigler wrote:
> 
> > Hello everyone,
> >
> >
> > I've taken PathScale's source tree (they've removed the IA-64 code 
> > generator, and added an x86/AMD64 code generator), and tweaked the 
> > Makefiles.
> >
> > I thought some of you might want to take a look at the compiler.
> >
> > http://www-rocq.inria.fr/~gonzalez/vrac/open64-alchemy-src.tar.bz2
> >
> This reference doesn't work.   The directory vrac looks empty.
> 

The only other interesting thing they've done is add a simdizer.

I diff'd the pathscale compiler and the open64 compiler source, and the
main differences are:

A bunch of random code #ifdef KEY'd
A SIMDizer, which doesn't look like it's as good as ours, it just has
better dependence and alias info to work with  ATM.




  parent reply	other threads:[~2005-06-30  1:19 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 [this message]
2005-06-30 21:46     ` James E Wilson
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=1120094349.8950.15.camel@linux-009002219098 \
    --to=dberlin@dberlin.org \
    --cc=gcc@gcc.gnu.org \
    --cc=marc.gonzalez-sigler@inria.fr \
    --cc=vmakarov@redhat.com \
    /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).