Exactly which version of gcc is this? It appears to work fine with at
least some gcc 3 versions.
gcc (GCC) 3.2.2 20030222 (Red Hat Linux 3.2.2-5)
Standard Red Hat 9.
Robert Reif wrote:
> Thiemo Seufer wrote:
>
>> CVSROOT: /sources/qemu
>> Module name: qemu
>> Changes by: Thiemo Seufer 08/01/23 19:01:12
>>
>> Modified files:
>> . : cpu-all.h cpu-exec.c qemu-doc.texi vl.c
>>
>> Log message:
>> Add option to disable TB cache, by H
Thiemo Seufer wrote:
CVSROOT:/sources/qemu
Module name:qemu
Changes by: Thiemo Seufer08/01/23 19:01:12
Modified files:
. : cpu-all.h cpu-exec.c qemu-doc.texi vl.c
Log message:
Add option to disable TB cache, by Herve Poussineau.
CVSWeb URLs:
htt
> > The latter depends how general you want the solution to be. One
> > possibility is for the device DMA+registration routines map everything
> > onto CPU address space.
>
> Interesting idea, do you mean that all individual bus address spaces
> could exist in system view in the same large address
On 1/3/08, Paul Brook <[EMAIL PROTECTED]> wrote:
> > > As I said earlier, the only correct way to handle memory accesses is to
> > > be able to consider a memory range and its associated I/O callbacks as
> > > an object which can be installed _and_ removed. It implies that there is
> > > a priority
> > As I said earlier, the only correct way to handle memory accesses is to
> > be able to consider a memory range and its associated I/O callbacks as
> > an object which can be installed _and_ removed. It implies that there is
> > a priority system close to what you described. It is essential to
>
On 1/3/08, Fabrice Bellard <[EMAIL PROTECTED]> wrote:
> Blue Swirl wrote:
> > On 1/3/08, Paul Brook <[EMAIL PROTECTED]> wrote:
> >> On Wednesday 02 January 2008, Blue Swirl wrote:
> >>> On 1/2/08, Paul Brook <[EMAIL PROTECTED]> wrote:
> > Also the opaque parameter may need to be different for e
Blue Swirl wrote:
On 1/3/08, Paul Brook <[EMAIL PROTECTED]> wrote:
On Wednesday 02 January 2008, Blue Swirl wrote:
On 1/2/08, Paul Brook <[EMAIL PROTECTED]> wrote:
Also the opaque parameter may need to be different for each function,
it just didn't matter for the unassigned memory case.
Do yo
On Thursday 03 January 2008, Blue Swirl wrote:
> On 1/3/08, Paul Brook <[EMAIL PROTECTED]> wrote:
> > On Wednesday 02 January 2008, Blue Swirl wrote:
> > > On 1/2/08, Paul Brook <[EMAIL PROTECTED]> wrote:
> > > > > Also the opaque parameter may need to be different for each
> > > > > function, it j
On 1/3/08, Paul Brook <[EMAIL PROTECTED]> wrote:
> On Wednesday 02 January 2008, Blue Swirl wrote:
> > On 1/2/08, Paul Brook <[EMAIL PROTECTED]> wrote:
> > > > Also the opaque parameter may need to be different for each function,
> > > > it just didn't matter for the unassigned memory case.
> > >
>
On Wednesday 02 January 2008, Blue Swirl wrote:
> On 1/2/08, Paul Brook <[EMAIL PROTECTED]> wrote:
> > > Also the opaque parameter may need to be different for each function,
> > > it just didn't matter for the unassigned memory case.
> >
> > Do you really have systems where independent devices nee
On 1/2/08, Paul Brook <[EMAIL PROTECTED]> wrote:
> > Also the opaque parameter may need to be different for each function,
> > it just didn't matter for the unassigned memory case.
>
> Do you really have systems where independent devices need to respond to
> different sized accesses to the same add
> Also the opaque parameter may need to be different for each function,
> it just didn't matter for the unassigned memory case.
Do you really have systems where independent devices need to respond to
different sized accesses to the same address?
Paul
On 1/1/08, Fabrice Bellard <[EMAIL PROTECTED]> wrote:
> This patch breaks the behaviour of the memory callbacks if the callbacks
> are changed dynamically (see cirrus_update_memory_access() to see what I
> mean). You are lucky that no one does that in the subpage case !
I'll change the function po
Blue Swirl wrote:
> CVSROOT: /cvsroot/qemu
> Module name: qemu
> Changes by: Blue Swirl 08/01/01 16:57:19
>
> Modified files:
> . : cpu-all.h exec.c
>
> Log message:
>Support for registering address space only for some access widths
>
> CVSWeb URLs:
> http:/
Hi Fabrice,
thank you for commenting on this.
Fabrice Bellard wrote:
> Hi,
>
> The code would be simpler if some intercept tests were done at runtime
> in the corresponding helpers (for crN, drN and MSR registers, I/Os).
> This is especially true when the existing helpers can return an
> exceptio
Hi,
The code would be simpler if some intercept tests were done at runtime
in the corresponding helpers (for crN, drN and MSR registers, I/Os).
This is especially true when the existing helpers can return an
exception at runtime. Complicating the translator to handle SVM is
definitely not the
On Wed, Mar 07, 2007 at 10:40:41PM +0100, J. Mayer wrote:
> as far as I can see, prep target was broken before I send this patch: no
> PCI IRQ seem to be available anymore, so the target can not even be
> boot. There is the same problem with heathrow machine. Looks like the
> PCI and/or the IRQ con
On Wed, 2007-03-07 at 22:40 +0100, J. Mayer wrote:
> On Wed, 2007-03-07 at 14:14 +, Stuart Brady wrote:
> > On Wed, Mar 07, 2007 at 08:32:30AM +, Jocelyn Mayer wrote:
> > > CVSROOT: /sources/qemu
> > > Module name: qemu
> > > Changes by: Jocelyn Mayer 07/03/07 08:32:30
> > >
>
On Wed, 2007-03-07 at 14:14 +, Stuart Brady wrote:
> On Wed, Mar 07, 2007 at 08:32:30AM +, Jocelyn Mayer wrote:
> > CVSROOT:/sources/qemu
> > Module name:qemu
> > Changes by: Jocelyn Mayer 07/03/07 08:32:30
> >
> > Modified files:
> > . : cpu-all.h gdbstub.c m
On Wed, Mar 07, 2007 at 08:32:30AM +, Jocelyn Mayer wrote:
> CVSROOT: /sources/qemu
> Module name: qemu
> Changes by: Jocelyn Mayer 07/03/07 08:32:30
>
> Modified files:
> . : cpu-all.h gdbstub.c monitor.c
> hw : ppc.c
> linux-user : ma
On Thursday 09 February 2006 17:04, Mulyadi Santosa wrote:
> Dear Fabrice
>
> > Log message:
> > support for builtin profiler
>
> Does this mean, qemu will have native profiling support just like
> oprofile does? In other word, we can easily access cpu perfomance
> counter such as TLB miss, una
Dear Fabrice
> Log message:
> support for builtin profiler
Does this mean, qemu will have native profiling support just like
oprofile does? In other word, we can easily access cpu perfomance
counter such as TLB miss, unaligned cache access and so on?
regards
Mulyadi
QEMU compiles fine on ppc now, but the Problem wit DOS under PPC persists.
I tested Reactos 0.28 and Win95 and they both run fine so far.
On the Dos side I tried the Freedos image from oszoo, Freedos
installation Floppy from fdos.org, MS DOS 6.22 and MS DOS 7.0 (win95)
and they all fail. (eith
Hello,
I just wanted to build CVS taget i386-softmmu on a PPC G4 with OS X
10.3.9, GCC 3.3.
I get a ton of the following compile errors:
/diff/qemu/cpu-all.h: In function `ldq_le_p':
/diff/qemu/cpu-all.h:234: warning: implicit declaration of function `ldl_p'
/diff/qemu/cpu-all.h: In function
25 matches
Mail list logo
