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: __main
Date: Mon, 02 Sep 2002 19:06:00 -0000	[thread overview]
Message-ID: <004d01c252ee$ba8ad530$5aa80844@fed1.sdca.home.com> (raw)
In-Reply-To: <20020902125147.GA2518@ceres.cs.mu.oz.au>

Hi,

I'm creating the port (working on my third month on this project).
I'm certainly learning a lot, so I'm hoping most of these issues/items
will be resolved by something I've overlooked.
(Kind of easy to miss things sometimes - there's a lot to learn).

Good point on the underscores. Unfortunately the assembler is not very
conforming,
but I'm trying to work with what I have. I have the USER_LABEL_PREFIX
defined to get around some problems. I'm doing what I can.

Thanks,
Mike

----- Original Message -----
From: "Fergus Henderson" <fjh@cs.mu.OZ.AU>
To: "Mike Laman" <mlaman@cox.net>
Cc: "GCC" <gcc@gcc.gnu.org>
Sent: Monday, September 02, 2002 5:51 AM
Subject: Re: __main


> On 02-Sep-2002, Mike Laman <mlaman@cox.net> wrote:
> > Maybe I'm missing the point, but I think these issues are with the
> > compiler - not the assembler. The assembler is already defined -
> > such can be the life with cross compiling.
>
> The issue could be a bug with a particular back-end port of the compiler.
> If the system as a whole doesn't support symbols starting with an
> underscore, then it is not a conforming C implementation.
>
> Which port is it?  Is it one that is included in the FSF version of GCC?
> Is it a port that you got from someone else?
> Or is it a port that you are implementing yourself?
>
> --
> Fergus Henderson <fjh@cs.mu.oz.au>  |  "I have always known that the
pursuit
> The University of Melbourne         |  of excellence is a lethal habit"
> WWW: <http://www.cs.mu.oz.au/~fjh>  |     -- the last words of T. S. Garp.

  reply	other threads:[~2002-09-03  2:06 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-29 11:25 __main Robert Spanton
2002-08-29 11:40 ` __main Fergus Henderson
2002-08-29 22:18   ` __main Mike Laman
2002-09-01  9:04     ` __main Fergus Henderson
2002-09-01 13:14       ` __main Mike Laman
2002-09-01 13:22         ` __main Mike Laman
2002-09-01 13:40           ` __main Robert Spanton
2002-09-02  4:26             ` __main Lars Brinkhoff
2002-09-02  5:29           ` __main Ian Dall
2002-09-02 19:08             ` __main Mike Laman
2002-09-01 22:56         ` __main Fergus Henderson
2002-09-02  3:36           ` __main Mike Laman
2002-09-02  5:51             ` __main Fergus Henderson
2002-09-02 19:06               ` Mike Laman [this message]
2002-09-03 14:03                 ` __main Fergus Henderson
2002-09-03 14:21                   ` __main Neil Booth
2002-09-04  4:03                     ` __main Richard Earnshaw
2002-09-02 19:37     ` __main Zack Weinberg

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='004d01c252ee$ba8ad530$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).