From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-return-117780-listarch-gcc=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 27994 invoked by alias); 27 Jul 2005 18:25:24 -0000
Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Archive: <http://gcc.gnu.org/ml/gcc/>
List-Post: <mailto:gcc@gcc.gnu.org>
List-Help: <http://gcc.gnu.org/ml/>
Sender: gcc-owner@gcc.gnu.org
Received: (qmail 27974 invoked by uid 22791); 27 Jul 2005 18:25:19 -0000
Received: from zproxy.gmail.com (HELO zproxy.gmail.com) (64.233.162.202)
    by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Wed, 27 Jul 2005 18:25:18 +0000
Received: by zproxy.gmail.com with SMTP id s1so137850nze
        for <gcc@gcc.gnu.org>; Wed, 27 Jul 2005 11:25:17 -0700 (PDT)
Received: by 10.36.252.28 with SMTP id z28mr516928nzh;
        Wed, 27 Jul 2005 11:25:17 -0700 (PDT)
Received: by 10.36.103.12 with HTTP; Wed, 27 Jul 2005 11:25:17 -0700 (PDT)
Message-ID: <f7ec0a650507271125672499e1@mail.gmail.com>
Date: Wed, 27 Jul 2005 18:25:00 -0000
From: glagnar <glagnar@gmail.com>
Reply-To: glagnar <glagnar@gmail.com>
To: gcc@gcc.gnu.org
Subject: Questions about the new M32C target
Cc: dj@redhat.com
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-SW-Source: 2005-07/txt/msg01144.txt.bz2

Hi everyone,

I was excited to find out that gcc now supports the Renesas M16C/M32C
architecture. I have compiled binutils and gcc from the CVS sources.
However, there are several questions that I have:

1. Does anyone know if or when there will be a libc supporting this
target, and which one that will be (newlib?)?

2. After building the compiler, I can create object files but not
executables. ld claims there are linker scripts missing (the files ld
wants are r8c.ld, m16c.ld and m32c.ld, depending on CPU). Will these
be added to gcc or are you supposed to write your own?

3. There has been a project to add M16C support to gcc, but it was
apparently abandoned because the M16C architecture has two different
addressing modes, while gcc presumably does not support different
pointer sizes. See this discussion for details:
http://lists.gnu.org/archive/html/m16c-dev/2003-11/msg00001.html

How has this issue been addressed in the current version?

Thanks