public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrea 'Fyre Wyzard' Bocci <fwyzard@inwind.it>
To: "Pannaga Bhushan" <bhushan@multitech.co.in>,<gcc-help@gcc.gnu.org>
Subject: Re: 16 bit code for 186 processor
Date: Fri, 11 Jan 2002 15:44:00 -0000	[thread overview]
Message-ID: <5.1.0.14.0.20020112004405.02c69b68@popmail.inwind.it> (raw)
In-Reply-To: <001101c199dc$ca3350a0$9603a8c0@panna>

At 19.13 10/01/2002 (GMT +0530), Pannaga Bhushan wrote:
>Dear Sir/Madam,
>                           I am using bin utils 2.11.2, which is the latest
>available. I wrote a simple hello world program and compiled with gcc using
>the -S option to get the .s (assembly file).  I inserted .code16 directive
>in the line after the label main:
>
>Then I assembled this with the command   -----    gcc file_name.s
>
>The a.out file that I get from this process gives segmentation fault error
>and dumps the core.
>
>What are the steps to get a code that can execute on 186 processor( that is
>16 bit processor).
>
>Hope the procedure is simple and also hope that I get a reply soon.

I don't know if it is at all possible - anyway, you at least need to build 
all the library you are going to use (including those that come with gcc, 
eg. libgcc, libstdc++, etc.) as 16 bit.
Note that this is just a requirement, I don't think it'll be enough to 
generate 16 bit code at all.

fwyzard

      reply	other threads:[~2002-01-11 23:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-10  5:42 Pannaga Bhushan
2002-01-11 15:44 ` Andrea 'Fyre Wyzard' Bocci [this message]

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=5.1.0.14.0.20020112004405.02c69b68@popmail.inwind.it \
    --to=fwyzard@inwind.it \
    --cc=bhushan@multitech.co.in \
    --cc=gcc-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).