From: "Martin v. Loewis" <martin@loewis.home.cs.tu-berlin.de>
To: olix2000@hotmail.com
Cc: gnu@gnu.org, help-gcc@gnu.org
Subject: Re: gcc
Date: Thu, 09 Mar 2000 16:43:00 -0000 [thread overview]
Message-ID: <200003100037.BAA10358@loewis.home.cs.tu-berlin.de> (raw)
In-Reply-To: <200003091932.OAA06974@delysid.gnu.org>
> I am interested in writing a boot sector. I would like to use C and asm to
> do this. The majority of the code for a boot sector is 16 bit code. However,
> gcc (under linux) produces 32 bit code. Could you please tell me how to
> force the gcc compiler to produce 16 bit code?
GCC currently does not support a 16 bit target, at least not for the
x86 architecture. So you cannot use GCC for your boot sector.
Martin
WARNING: multiple messages have this Message-ID
From: "Martin v. Loewis" <martin@loewis.home.cs.tu-berlin.de>
To: olix2000@hotmail.com
Cc: gnu@gnu.org, help-gcc@gnu.org
Subject: Re: gcc
Date: Sat, 01 Apr 2000 00:00:00 -0000 [thread overview]
Message-ID: <200003100037.BAA10358@loewis.home.cs.tu-berlin.de> (raw)
Message-ID: <20000401000000.wJDRJSJHYR3fz93fKaed4TFvuvrmX18GnU0cb_myVTs@z> (raw)
In-Reply-To: <200003091932.OAA06974@delysid.gnu.org>
> I am interested in writing a boot sector. I would like to use C and asm to
> do this. The majority of the code for a boot sector is 16 bit code. However,
> gcc (under linux) produces 32 bit code. Could you please tell me how to
> force the gcc compiler to produce 16 bit code?
GCC currently does not support a 16 bit target, at least not for the
x86 architecture. So you cannot use GCC for your boot sector.
Martin
next prev parent reply other threads:[~2000-03-09 16:43 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-09 11:33 gcc Olaf Miller
2000-03-09 16:43 ` Martin v. Loewis [this message]
2000-04-01 0:00 ` gcc Martin v. Loewis
2000-04-01 0:00 ` gcc Olaf Miller
2000-05-29 8:16 gcc Blythe Dickman
2000-05-29 10:15 ` gcc Martin v. Loewis
2001-01-21 19:26 gcc Simon Ouellet
2001-01-21 19:48 ` gcc Alexandre Oliva
2001-02-12 17:17 gcc Paramjit Cheema
2001-02-12 18:38 ` gcc Alexandre Oliva
2001-02-15 7:50 gcc Robert Neal
2001-02-15 9:16 ` gcc Alexandre Oliva
2002-01-10 9:30 gcc Tom Fetterer
2002-08-19 19:23 gcc Samuel Lee Kwek Ming
2002-08-29 19:23 gcc Samuel Lee Kwek Ming
2002-08-29 19:27 ` gcc Ish Rattan
2002-08-30 3:42 ` gcc Claudio Bley
2002-10-11 4:44 GCC Bruno Aulagner
[not found] <616BE6A276E3714788D2AC35C40CD18D86F76D@whale.softwire.co.uk>
2002-10-11 5:13 ` GCC Rupert Wood
2003-03-30 7:24 gcc Arash Farmand
2003-03-30 15:50 ` gcc Bharathi S
2003-03-31 0:58 ` gcc LLeweLLyn Reese
2003-03-31 1:45 gcc Arash Farmand
2003-03-31 2:28 ` gcc Andre Kirchner
2003-03-31 7:31 ` gcc Matthieu Moy
2003-03-31 8:09 ` gcc Stuart Longland
2003-03-31 13:28 ` gcc Matthieu Moy
2003-04-02 0:42 ` gcc Segher Boessenkool
2003-03-31 7:19 gcc Dockeen
2003-09-04 20:55 gcc Rich Franczak
2003-09-04 23:42 ` gcc Eljay Love-Jensen
2003-12-16 14:14 GCC Jerry Lyle
2004-03-24 2:44 GCC faltat
2004-03-24 4:23 ` GCC Eljay Love-Jensen
2004-03-24 15:05 gcc faltat
2004-03-24 22:32 ` gcc Ken Foskey
2004-03-25 19:12 gcc frostflare
2004-03-25 19:13 ` gcc llewelly
2004-03-25 23:13 gcc frostflare
2004-03-26 1:12 ` gcc Eljay Love-Jensen
2004-09-22 4:27 GCC Drew Gray
2004-09-22 12:48 ` GCC Ishwar Rattan
2006-06-03 10:24 gcc Gunnar Sjoo
2008-10-09 21:38 gcc Jair Santos
2008-10-10 10:24 ` gcc Andrew Haley
2011-08-29 8:44 GCC emil johansson
2011-08-29 9:29 ` GCC David Brown
2011-08-29 16:32 ` GCC Philip Herron
2012-06-07 9:36 gcc jai singh
2012-06-07 12:27 ` gcc Jonathan Wakely
2019-12-16 8:50 Gcc Isabella Kathryn
2020-11-07 18:08 gcc Simon Liu
2021-07-14 19:25 Gcc Wendy Bonner
2021-07-22 4:31 Gcc Alice Matthews
2021-11-26 9:24 gcc Claire Carter
2022-11-03 14:56 gcc Jason Bloom
2023-02-28 12:55 gcc Octavia Bennett
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=200003100037.BAA10358@loewis.home.cs.tu-berlin.de \
--to=martin@loewis.home.cs.tu-berlin.de \
--cc=gnu@gnu.org \
--cc=help-gcc@gnu.org \
--cc=olix2000@hotmail.com \
/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).