On Tue, Dec 30, 2014 at 04:34:42PM -0600, Dennis Ferguson wrote:
On 30 Dec, 2014, at 12:52 , David Laight da...@l8s.co.uk wrote:
Is that the correct fix?
Unless the rdpr actually accesses memory (don't think it does) then
then problem is probably a missing 'volatile' instead.
On Tue, Dec 30, 2014 at 05:58:06PM -0500, Christos Zoulas wrote:
Modified Files:
xsrc/external/mit/MesaLib/dist/src/mesa/main: format_utils.c
Log Message:
The macros in this file generate a gigantic function that takes a long time
to compile and a ton of memory. Split it per datatype
On Wed, Dec 31, 2014 at 10:05:22AM +, David Laight wrote:
In this case I suspect removing __constfunc and making the
asm volatile will force correct sequencing.
Check the commit history.
Can we make only the hypverisor call __constfunc?
Martin
On Wed, Dec 31, 2014 at 11:15:24AM +0100, Martin Husemann wrote:
On Wed, Dec 31, 2014 at 10:05:22AM +, David Laight wrote:
In this case I suspect removing __constfunc and making the
asm volatile will force correct sequencing.
Check the commit history.
Can we make only the hypverisor
In article 20141231101118.gb2...@snowdrop.l8s.co.uk,
David Laight da...@l8s.co.uk wrote:
On Tue, Dec 30, 2014 at 05:58:06PM -0500, Christos Zoulas wrote:
Modified Files:
xsrc/external/mit/MesaLib/dist/src/mesa/main: format_utils.c
Log Message:
The macros in this file generate a
On Dec 31, 2:52pm, Christos Zoulas wrote:
}
} This is a multi-part message in MIME format.
}
} --_--=_14200555275200
} Content-Disposition: inline
} Content-Transfer-Encoding: 8bit
} Content-Type: text/plain; charset=US-ASCII
}
} Module Name: src
} Committed By: christos
} Date:
Frank Wille writes:
Module Name: src
Committed By: phx
Date: Wed Dec 31 18:43:18 UTC 2014
Modified Files:
src/sys/arch/ofppc/ofppc: mainbus.c
Log Message:
Make it compile with GCC48.
thanks.
no idea how this didn't trigger for me. we might need
this on netbsd-7 as
In article 201501010346.t013klrb023...@server.cornerstoneservice.ca,
John Nemeth jnem...@cue.bc.ca wrote:
When adding this stanza to drivers, should you not set error = 0;
after it just to be safe? It seems that some drivers aren't very
clean in the way they deal with error and/or are not
