public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Stef" <stef@email.address>
To: help-gcc@gnu.org
Subject: Re: GCC and Windows 98
Date: Thu, 30 Sep 1999 23:56:00 -0000	[thread overview]
Message-ID: <7r0s3c$919$1@news4.svr.pol.co.uk> (raw)
Message-ID: <19990930235600.elr4Sy5BZiytVblV99pvtW5iwuPuRwvTVkomyzYSCls@z> (raw)
In-Reply-To: <7r008g$bcg$1@news.mch.sbs.de>

In response to your query about the void __main(){} prototype and the exit()
function, these were at the suggestion of the readme file that came with the
native Hitachi SH2 development board.

Tried again with a simple for loop and no optimisation.  Guess what, same
Stack Fault.

In essence I am trying to compile the code for subsequent serial download to
an SH2 processor.  Unfortunately it doesn't compile at all (even as a simple
win32 'exe).  I've had it working in the past on other PC's and my colleague
has it working happily (exact same version) on his PC.  And I'm baffled.  I
can only conclude that there is a SW/HW conflict at a much lower level (I
sincerely hope not, and at the moment don't really count it as a viable
answer...).

I have again tried it with the previous response (as an -luser32 exe) but
again the exact same stack fault.

At a loose end here!

[Running Windows98, Gigabyte Motherboard, Celeron 400MHx, 10GB HDD and 64MB
RAM... shouldn't cause a problem I think?]

Thanks in advance,

Stef


Martin Kahlert <martin.kahlert@keksy.mchp.siemens.de> wrote in message
news: 7r008g$bcg$1@news.mch.sbs.de ...
> [Posted and mailed]
>
> In article < 7qovlu$j55$1@news7.svr.pol.co.uk >,
> "Stef" <stef@email.address> writes:
> > ################################
> >
> > void __main(){}
> >
> > void exit()
> > {
> >     while(1);
> > }
> >
> > main()
> > {
> >     return 0;
> > }
> >
> > ################################
> I don't know, what this should be.
> What's the void __main(){} line good for?
> Why do you replace the exit reoutine (which
> is called automatically at the end of any main routine)
> with a never ending loop?



  reply	other threads:[~1999-09-30 23:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-09-03 10:17 Stef
1999-09-06  1:22 ` Patrick Block
1999-09-30 23:56   ` Patrick Block
1999-10-01  0:00   ` Patrick Block
1999-09-06  2:10 ` Martin Kahlert
1999-09-06 10:05   ` Stef [this message]
1999-09-13  1:39     ` Kai Ruottu
1999-09-30 23:56       ` Kai Ruottu
1999-10-01  0:00       ` Kai Ruottu
1999-09-30 23:56     ` Stef
1999-10-01  0:00     ` Stef
1999-09-30 23:56   ` Martin Kahlert
1999-10-01  0:00   ` Martin Kahlert
1999-09-30 23:56 ` Stef
1999-10-01  0:00 ` Stef

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='7r0s3c$919$1@news4.svr.pol.co.uk' \
    --to=stef@email.address \
    --cc=help-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).