Since I've been poking around the Interrupts object, I've noticed
we've got a lot of functions on there, and we can probably trim that
down a bit. There are functions related to setting and clearing
interrupts which go away when those are delivered through the memory
system, although that
scons: *** [build/ALPHA_SE/m5.fast] Error 1
scons: *** [build/ALPHA_FS/m5.fast] Error 1
* build/SPARC_SE/tests/fast/quick/02.insttest/sparc/linux/simple-atomic
passed.
* build/SPARC_SE/tests/fast/quick/00.hello/sparc/linux/simple-atomic passed.
= Output differences =*
how long has SMT regressions been broke? Is this a new thing?
I havent looked at O3 SMT in awhile, but I would assume the O3 changes
over the past year or so take my fix time way up!
Is there a particular changeset or marker where we can say it broke here...?
On Sat, Sep 6, 2008 at 1:25 PM,
alright, i'll dig a little and see what's up.
On Mon, Sep 8, 2008 at 10:27 AM, nathan binkert [EMAIL PROTECTED] wrote:
how long has SMT regressions been broke? Is this a new thing?
I havent looked at O3 SMT in awhile, but I would assume the O3 changes
over the past year or so take my fix time
I'm trying to get thing working in gcc 4.3, so I installed a beta of
intrepid ibex.
The first bug was that the logic for detecting GCC is wrong in some
way. How about the attached diff. It seems right for old ubuntu, new
ubuntu, fedora, and my mac.
Nate
cxx.diff
Description: Binary data
Seems reasonable to me.
Ali
On Sep 8, 2008, at 6:32 PM, nathan binkert wrote:
I'm trying to get thing working in gcc 4.3, so I installed a beta of
intrepid ibex.
The first bug was that the logic for detecting GCC is wrong in some
way. How about the attached diff. It seems right for old
As usual the gnu guys are out to make our life easier. I've more or
less got things working with 4.3, but there are a couple of issues we
need to sort out. I'll also need people to compile M5 on as many
systems as possible to make sure that my changes don't break things.
(I'll commit the patches
I don't think this optimization will work. The reason that the get and
update parts were separated was because getInterupt() is supposed to
be callable without changing the interrupt/system state. If memory
serves the reason for this is because there are cases where you might
call get a
On Sep 8, 2008, at 8:19 PM, nathan binkert wrote:
As usual the gnu guys are out to make our life easier. I've more or
less got things working with 4.3, but there are a couple of issues we
need to sort out. I'll also need people to compile M5 on as many
systems as possible to make sure that
changeset bb31ea8583d8 in /z/repo/m5
details: http://repo.m5sim.org/m5?cmd=changeset;node=bb31ea8583d8
description:
style: This file hugely violated the M5 style.
Remove a bunch of unused cruft from the interface while we're at it
diffstat:
2 files changed, 20 insertions(+), 40
I'm in favor of ignoring the parenthesis warning.
Gabe
Quoting nathan binkert [EMAIL PROTECTED]:
As usual the gnu guys are out to make our life easier. I've more or
less got things working with 4.3, but there are a couple of issues we
need to sort out. I'll also need people to compile M5
I'll buy that.
Gabe
Quoting Ali Saidi [EMAIL PROTECTED]:
I don't think this optimization will work. The reason that the get and
update parts were separated was because getInterupt() is supposed to
be callable without changing the interrupt/system state. If memory
serves the reason for this
12 matches
Mail list logo
