public inbox for linux-8086@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert de Bath <robert$@mayday.cix.co.uk>
To: claudio@conectiva.com,
	Eduardo Pereira Habkost <ehabkost@conectiva.com.br>,
	Miguel Bolanos <mike@linuxlabs.com>
Cc: Linux-8086 <linux-8086@vger.kernel.org>
Subject: Re: bcc code generation issues
Date: Fri, 4 Jun 2004 19:41:05 +0100 (BST)	[thread overview]
Message-ID: <9b4a87aaebf91a0a@mayday.cix.co.uk> (raw)
In-Reply-To: <1086283502.3227.28.camel@talena.hsol.net>

Hi all,

I've added some changes for dev86 and uploaded to the normal place.

> Added __BCC_VERSION__ macro, defined by bcc.c contains hex version no.
>
> Bugfix for offsets generated by #asm when using -O option to bcc-cc1.
> Extra compile option ASM_USES_CALLEE_REGS.
>
> Extra checking and bugfix for mixing char values with long shifts.

Have fun.

-- 
Rob.                          (Robert de Bath <robert$ @ debath.co.uk>)
                                       <http://www.cix.co.uk/~mayday>



           reply	other threads:[~2004-06-04 18:41 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1086283502.3227.28.camel@talena.hsol.net>]

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=9b4a87aaebf91a0a@mayday.cix.co.uk \
    --to=robert$@mayday.cix.co.uk \
    --cc=claudio@conectiva.com \
    --cc=ehabkost@conectiva.com.br \
    --cc=linux-8086@vger.kernel.org \
    --cc=mike@linuxlabs.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