public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Etienne Fortin" <etienne.fortin@sympatico.ca>
To: <gcc@gcc.gnu.org>
Subject: Porting GCC without a working assembler and need for libgcc and other libraries
Date: Tue, 30 Jul 2002 09:08:00 -0000	[thread overview]
Message-ID: <MPENLHFCKBCKLLHDFICDKECLCEAA.etienne.fortin@sympatico.ca> (raw)

I developped an ISA (Instruction Set Architecture) from the ground up. I
have a working VM for that architecture. I also have an assembler and
various other utilities. I would like to add a C/C++/Fortran/Other compiler
for that architecture, and nothing is better than GCC in that respect.

Here's some problems:
1) The executable files have a format that is part ascii, part binary and is
not compatible with binutils.
2) The source are presented to the assembler in a format that is not
compatible with as (gnu assembler).
3) The assembler I developped can't be used with GCC for various reasons.

So in other words, there's no assembler for the architecture I can use with
GCC.

Here's what I want to do:
1) Create a cross compiler for the architecture that ONLY produce ASSEMBLER
source. No runtime, no crt, no other problems.
2) Postprocess the assembler source with Perl so that the format is OK for
the assembler I developped.
3) Assemble the file with my assembler.
4) ENJOY!

So the big question is........

Can someone tell me how I can build GCC so that NO runtime libraries are
build (not even libgcc) and in a way that the assembler is NOT needed (since
there's no assembler for the architecture). And next how can I create that
same GCC with the option -S always ON?

Anyone good enough here to answer that difficult question?

Etienne Fortin

             reply	other threads:[~2002-07-30 11:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-30  9:08 Etienne Fortin [this message]
2002-07-30  9:13 ` Michael Matz

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=MPENLHFCKBCKLLHDFICDKECLCEAA.etienne.fortin@sympatico.ca \
    --to=etienne.fortin@sympatico.ca \
    --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).