After adding a WITHOUT_SDL option to the FreeBSD qemu port (see
http://docs.freebsd.org/cgi/mid.cgi?20061028183618.GA46200
, and hi joshe! :) I got a crash that looks like monitor output
going to an uninitialized vty:
$ gdb work/qemu-snapshot-2006-10-26_05/i386-softmmu/qemu qemu.core
GNU g
CVSROOT:/sources/qemu
Module name:qemu
Changes by: Fabrice Bellard06/10/28 19:27:11
Modified files:
fpu: softfloat-native.c softfloat-native.h
softfloat-specialize.h softfloat.c softfloat.h
Log message:
avoid using cha
On Saturday 28 October 2006 6:46 am, Martin Guy wrote:
> > gcc on ARM systems default to unsigned. The C standard specifically
> > states that char is either signed or unsigned at the whim of the
> > implementor
>
> Or, more to the point, at the behest of the machine architecture.
> Having to gen
On Saturday 28 October 2006 5:36 am, Alessandro Corradi wrote:
> Hello,
> Can someone give me detailed information (or a link where it is described)
> how qemu manage hw interrupts?
> I can't find any usefull info about it in QEMU doc.
http://www.qemu.org/qemu-tech.html#SEC18
> ps: Obviously, if
On Friday 27 October 2006 7:09 pm, Paul Brook wrote:
> > > > It has been a really long time I have been working on a broken system
> > > > that did not default to "signed".
> > >
> > > The only thing that is broken is your knowlege of C.
> >
> > Okay.
> >
> > And what system did you encounter this
CVSROOT:/sources/qemu
Module name:qemu
Changes by: Fabrice Bellard06/10/28 12:19:07
Modified files:
. : Makefile.target
Log message:
avoid regression on sparc-user and ppc-user
CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/qemu/Makefile.ta
CVSROOT:/sources/qemu
Module name:qemu
Changes by: Fabrice Bellard06/10/28 12:09:16
Modified files:
linux-user : signal.c
Log message:
removed invalid code
CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/qemu/linux-user/signal.c?cvsroot=qemu&r1=1.33&
gcc on ARM systems default to unsigned. The C standard specifically
states that char is either signed or unsigned at the whim of the
implementor
Or, more to the point, at the behest of the machine architecture.
Having to generate code to sign-extend the hard way every time you do
char-integer p
Johannes Schindelin a écrit :
And what system did you encounter this behaviour on?
Do a:
grep -wr DEFAULT_SIGNED_CHAR gcc/config
in a gcc source tree and you will get a list for gcc targets :)
Laurent
___
Qemu-devel m
Hello,Can someone give me detailed information (or a link where it is described) how qemu manage hw interrupts?I can't find any usefull info about it in QEMU doc.For example, how does work Interrupts for the parallel port? (I see in the code that it is the easier device to understand how qemu works
10 matches
Mail list logo
