public inbox for linux-8086@vger.kernel.org
 help / color / mirror / Atom feed
From: "Vikas N Kumar" <vikasnkumar@users.sourceforge.net>
To: Eddy <eddyx89@gmail.com>
Cc: ELKS <linux-8086@vger.kernel.org>
Subject: Re: GCC port for Intel 8086, 80186 and 80286
Date: Fri, 31 Aug 2007 08:58:53 -0400	[thread overview]
Message-ID: <792c60620708310558o2153050cga8be4e02a9dcf4f5@mail.gmail.com> (raw)
In-Reply-To: <46D7D343.6060201@gmail.com>

You forget that assembler directives are different for Gnu Assembler
(gas) and the bcc assembler. Not to forget the fact that gas accepts
instructions like movl, movd etc and many other assemblers do not.
they only accept mov, and figure out the size of the data based on the
registers used as operands. It will have to be done manually and
checked thoroughly.

On 8/31/07, Eddy <eddyx89@gmail.com> wrote:
> Alan Cox wrote:
> > On Thu, 30 Aug 2007 13:43:52 -0300
> > "Alan Carvalho de Assis" <acassis@gmail.com> wrote:
> >
> >
> >
> > Well the first step to sanity would be moving the kernel code to the 8086
> > gcc, getting ansi prototypes and sane C. That means sorting the asm out
> > with gcc asm which frankly scares me 8)
> > -
> >
>
>
> I don't know very well what are the differences between the 2 codes, but
> I think that is possible to use a recursive bash script to automatically
> replace lines that have to be replaced and go.
> I thought at something like this:
> #!/bin/bash
>
> for i in `grep -R "text that is in files to be replaced" elks/* | cut
> -f1-1 -d ":"`
> do
> sed -i -e 's,old code,new code,g' $i
> sed -i -e 's,old code,new code,g' $i
> ...
> done
>
> It is a good idea?
> I hope yes.
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-8086" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>


-- 
http://www.vikaskumar.org/

      reply	other threads:[~2007-08-31 12:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-09 20:56 GCC port for Intel 8086, 80186 and 80286 Rask Ingemann Lambertsen
2007-08-09 22:36 ` Royce Williams
2007-08-10  7:27 ` Hans
2007-08-10  8:41   ` Rask Ingemann Lambertsen
2007-08-30 15:16 ` Rask Ingemann Lambertsen
2007-08-30 16:43   ` Alan Carvalho de Assis
2007-08-30 16:54     ` Chad
2007-08-30 23:42     ` Alan Cox
2007-08-31  8:37       ` Eddy
2007-08-31 12:58         ` Vikas N Kumar [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=792c60620708310558o2153050cga8be4e02a9dcf4f5@mail.gmail.com \
    --to=vikasnkumar@users.sourceforge.net \
    --cc=eddyx89@gmail.com \
    --cc=linux-8086@vger.kernel.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