Hi,
I'm writing an 8086 backend.
Short info about backend:
Basicly I converted m32c backend for 8086.
For the moment, it can compile 16-32 bits integer &
16-32 bits pointer codes.
16 bits pointer codes can be assembled with as but for
32 bits I convert at&t assembly output to intel and
use nasm to
On 20 July 2006 07:03, Wolfgang Mües wrote:
> Hello Rask,
>
> On Wednesday 19 July 2006 13:24, Rask Ingemann Lambertsen wrote:
>> I've spotted a function named emit_set_insn() in arm.c. It might be
>> the problem, because it uses gen_rtx_SET() directly.
>
> But it's not the only function which u
On Thu, 2006-07-20 at 12:04, Dave Korn wrote:
> On 20 July 2006 07:03, Wolfgang Mües wrote:
>
> > Hello Rask,
> >
> > On Wednesday 19 July 2006 13:24, Rask Ingemann Lambertsen wrote:
> >> I've spotted a function named emit_set_insn() in arm.c. It might be
> >> the problem, because it uses gen_rtx
On Thu, Jul 20, 2006 at 08:02:45AM +0200, Wolfgang Mües wrote:
> But it's not the only function which uses gen_rtx_SET. There are also
> much places with
>
> > emit_constant_insn (cond,
> > gen_rtx_SET (VOIDmode, target, source));
>
> Isn't it better to replace gen_rtx_SET?
gen_rtx_SET()
On Wed, Jun 07, 2006 at 07:22:31AM +0200, Wolfgang Mües wrote:
> On Tuesday 06 June 2006 21:33, Rask Ingemann Lambertsen wrote:
>
> > Yet another register which stands a good chance of being reusable is
> > the register containing the address.
>
> Yes, but that is not allowed according to the spe
Erdem Guven <[EMAIL PROTECTED]> writes:
> I'm using the backend in a project. I want to compile
> some codes in 16 bits int mode and others in 32 bits
> int. I figured out that gcc uses int sized blocks to
> store arguments, passed to a function, in stack. I
> mean if function get a short (16 bits
"Dave Korn" <[EMAIL PROTECTED]> writes:
> Is there any generic advice available as to when and why one should use
> emit_insn (gen_rtx_SET ()) as opposed to emit_move_insn (...)?
It depends on where you are in the compiler. You can only use
gen_rtx_SET if you know that the resulting insn w
On 20 July 2006 16:25, Ian Lance Taylor wrote:
> "Dave Korn" <[EMAIL PROTECTED]> writes:
>
>> Is there any generic advice available as to when and why one should use
>> emit_insn (gen_rtx_SET ()) as opposed to emit_move_insn (...)?
>
> It depends on where you are in the compiler. You can
===
[EMAIL PROTECTED]:/usr/local/src/gcc-4.1.1> ./config.guess
sparc-sun-solaris2.9
===
[EMAIL PROTECTED]:~> gcc -v
Using built-in specs.
Target: sparc-sun-solaris2.9
Configured with: /usr/local/src/gcc-4.1.1/configur
Hey, guyz.
I have a C program that I need to compile using gcc.
The problem is that there are many callback-functions in the code.
And when I try to do that, the code compiles Ok, but it doesn't link
crashing with 'undefined refence' exception.
Any ideas how to avoid that?
Tnx.
On Jul 20, 2006, at 2:55 PM, [EMAIL PROTECTED] wrote:
I have a C program that I need to compile
This is the wrong list for such question.
Snapshot gcc-4.0-20060720 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/4.0-20060720/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 4.0 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches
12 matches
Mail list logo
