|
Message
From: Dimitrios Orfanos<sirtimid@g...>
Date: Tue Nov 27 09:35:01 CET 2007
Subject: [openrisc] What is the DYNAMIC_EXECUTION , COMPLEX_EXECUTION,
and SIMPLE_EXECUTION?
On Monday 26 November 2007 18:19:47 Robert Cragie wrote:
> If you just want to link without any of the C runtime support in,
> put -nostartfiles and -nostdlib in the linker command line.
>
> Robert Cragie, Design Engineer
> _______________________________________________________________
> Jennic Ltd, Furnival Street, Sheffield, S1 4QT, UK
> http://www.jennic.com Tel: +44 (0) 114 281 2655
> _______________________________________________________________
>
> > -----Original Message-----
> > From: openrisc-bounces@o...
> > [mailto:openrisc-bounces@o...]On Behalf Of Dimitrios Orfanos
> > Sent: 26 November 2007 09:27
> > To: List about OpenRISC project
> > Subject: Re: [openrisc] What is the DYNAMIC_EXECUTION ,
> > COMPLEX_EXECUTION,and SIMPLE_EXECUTION?
> >
> >
> > Hi,
> > OK thanks about the answer. Another question now about your toolchain.
> > When I compile programs with the or32-elf-gcc, that have reference to the
> > library the program is compiled without problem. When, I try to compile
> > programs that don't have reference to the library the program doesn't
> > compile.
> > For example the following program:
> > ----------------------------
> > int f(int i)
> > {
> > return i+1;
> > }
> > int main()
> > {
> > return f(-1);
> > }
> > ----------------------------
> > When I try to compile it with the command:
> > "or32-elf-gcc -o another another.c "
> > I take the following message:
> > "/home/dimitrios/drp-0.6/toolchain/install/bin/../lib/gcc/or32-elf
> > /4.2.1/../../../../or32-elf/lib/libc.a(lib_a-sbrkr.o):
> > In function `_sbrk_r':
> > /home/dimitrios/drp-0.6/toolchain/build/newlib-1.15.0.elf/or32-elf
> > /newlib/libc/reent/../../../../../../src/newlib-1.15.0/newlib/libc
> > /reent/sbrkr.c:60:
> > undefined reference to `_sbrk'
> > collect2: ld returned 1 exit status
> > "
> >
> > On Friday 23 November 2007 18:20:50 Mark wrote:
> > > Dimitrios Orfanos wrote:
> > > > Hi,
> > > >
> > > > I am trying to modify or1ksim 0.2.0 in order to produce
> >
> > statistics about
> >
> > > > the cycles that are consumed per instruction. In the code are defined
> > > > three different modes of execution the DYNAMIC, the COMPLEX and the
> > > > SIMPLE. Can you explain me the difference?
> > > >
> > > > DO
> > >
> > > I don't actually know the difference, but here's what I would guess
> > > based on looking at the code.
> > >
> > > SIMPLE_EXECUTION: slow instruction decoding (the automata for matching
> > > opcodes are executed at runtime)
> > > COMPLEX_EXECUTION: fast instruction decoding (a fast decoder is
> > > generated from the automata and compiled into the simulator)
> > > DYNAMIC_EXECUTION: instructions are dynamically recompiled from or32
> > > opcodes to opcodes for the host architecture (i386-only, I think)
> > >
> > > The relevant source seems to be concentrated in cpu/or32/execute.c,
> > > cpu/or32/generate.c, cpu/or32/insnset.c, cpu/or32/dyngen*
> > > _______________________________________________
> > > http://www.opencores.org/mailman/listinfo/openrisc
> >
> > _______________________________________________
> > http://www.opencores.org/mailman/listinfo/openrisc
>
> _______________________________________________
> http://www.opencores.org/mailman/listinfo/openrisc
Hi,
I want to run my program on the simulator, so I need start file but I don't
need every time the whole lib. I've tried what you said but I took memory
error from the simulator. I think that I need some guidance on how to write
my own start file. I use Mark's elf toolchain and I want to run my programs
on the simulator.
DO
|
 |
Browse
