public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <iant@google.com>
To: "Aurélien Buhrig" <Aurelien.Buhrig@tiempo-ic.com>
Cc: <gcc@gcc.gnu.org>
Subject: Re: porting gcc
Date: Mon, 20 Oct 2008 19:34:00 -0000	[thread overview]
Message-ID: <m363nn83jy.fsf@google.com> (raw)
In-Reply-To: <003e01c9329d$62e997e0$28bcc7a0$@Buhrig@tiempo-ic.com>  (=?utf-8?Q?=22Aur=C3=A9lien?= Buhrig"'s message of "Mon\, 20 Oct 2008  12\:19\:50 +0200")

Aurélien Buhrig <Aurelien.Buhrig@tiempo-ic.com> writes:

> We are designing a 16-bit asynchronous microcontroller. I’ve already ported
> bfd, binutils (including sid simulator) using cgen, and part of gdb (for asm
> debug only) and we are now investigating the best way to have C compiler.
> So my questions are:
>
> 1- How much time do you think it will take to port gcc for this platform
> with a quite simple instruction set, with a good porting guide?

My answer the last time I answered this question:

http://gcc.gnu.org/ml/gcc-help/2008-04/msg00117.html


> 2- What about optimizations? I suppose most of them are platform-independent
> and performed at RTL level, aren't they? But, generally speaking, are there
> many platform-dependent optimizations (I would have to do)? And is it
> possible or how is it complex to have a level of optimization (code
> compactness...) as good as commercial compiler ones (such as IAR, Keil,
> ACE...)?

Most optimizations are platform independent.  The hardest platform
specific one to implement is scheduling; you will have to write a
description of your pipeline.  Some peepholes may be appropriate.
Other than that, you will only need platform specific code if your
processor is unusual in some respect.  Unfortunately, my experience is
that every processor has some unusual aspects.

gcc is a commercial compiler.  If you mean: how does gcc compare to a
proprietary compiler, the answer is that it is very competitive for
conventional processors.


> 3- Finally, some companies may port gcc for us (perhaps in this mailing
> list?). An idea of how much it could be?

I have no idea what the rates are these days, sorry.  In any case the
precise details of your processor make a big difference to the price.

Ian

  reply	other threads:[~2008-10-20 19:34 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-20 10:20 Aurélien Buhrig
2008-10-20 19:34 ` Ian Lance Taylor [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-03-12  6:11 Porting gcc Schmave
2008-03-12  6:15 ` Ben Elliston
2004-06-04 15:24 Porting GCC Gyle Yearsley
2004-06-02 16:49 Gyle Yearsley
2004-06-03 15:38 ` Richard Sandiford
2004-05-21 13:09 Porting gcc Mile Davidovic
2004-05-21 13:43 ` Dave Korn
2003-08-13 11:15 Petar Penchev
2003-08-13 16:07 ` Ben Elliston
2002-10-22  9:53 porting gcc Grégoire Dooms
2002-10-22  9:56 ` Grégoire Dooms
2002-10-22 14:40 ` Mike Stump
2002-10-22 14:43 ` Andrew Haley
2002-10-22 15:16   ` Michael Matz
2002-10-22 15:27   ` Svein E. Seldal
2002-10-22 18:02   ` Mike Stump
2002-10-23 10:05     ` Andrew Haley
2002-10-22 15:50 ` Denis Chertykov
2001-02-15  8:41 Filippo Basso
2001-02-15  9:50 ` Fergus Henderson
2001-02-01  2:37 porting GCC Krzysztof Matula
2001-02-01  3:10 ` Richard Earnshaw
2001-02-02  3:43   ` Krzysztof Matula
2001-02-02  4:00     ` Richard Earnshaw
2001-02-02  6:07       ` Krzysztof Matula
2001-02-02  7:08         ` Richard Earnshaw

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=m363nn83jy.fsf@google.com \
    --to=iant@google.com \
    --cc=Aurelien.Buhrig@tiempo-ic.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).