public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Mike Laman" <mlaman@cox.net>
To: "GCC" <gcc@gcc.gnu.org>
Subject: Re: The __Main Question
Date: Mon, 02 Sep 2002 18:54:00 -0000	[thread overview]
Message-ID: <004701c252ed$13713bf0$5aa80844@fed1.sdca.home.com> (raw)
In-Reply-To: <02090210280304.00731@localhost.localdomain>

Hi Mike,

This is a port I am working on (and having fun).

I have had USER_LABEL_PREFIX defined as you desccribed
to get rid of other underscores, but "__main" seems to be a fixed string.

I cannot find anything for letting me specify the "white space" character.
GCC generates tabs. I'd like to be able to define a macro or something
to furnish a different white space character (the space character (' ') for
me)
instead of the tab.

I agree about being able to "define the form and format in the assembly
output
(in the header file)". That's my understanding of the philosophy of being
able to use GCC as a cross compiler. That's why I raise these issues.

I'm actually making good progress. I'm generating code, fixing lots
of bugs and having fun...

Mike


----- Original Message -----
From: "Michael S. Zick" <mszick@goquest.com>
To: "Mike Laman" <mlaman@cox.net>
Sent: Monday, September 02, 2002 8:28 AM
Subject: The __Main Question


> Since you didn't mention which processor you are assembling for,
> I can only tell you where to look.
> in gcc/config/YourProcessor/xyz.h
>
> Look for this sort of define (from the mcore micro-controller):
>
> /* The prefix to add to user-visible assembler symbols. */
> #undef  USER_LABEL_PREFIX
> #define USER_LABEL_PREFIX ""
>
> Whatever file you find that in; Should be everything about how you define
the
> form and format of what gcc passes to your assembler.
>
> Which I think is the question you asked to begin with.
>
> Mike
>

           reply	other threads:[~2002-09-03  1:54 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <02090210280304.00731@localhost.localdomain>]

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='004701c252ed$13713bf0$5aa80844@fed1.sdca.home.com' \
    --to=mlaman@cox.net \
    --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).