gem5/tests/long/se/40.perlbmk/ref/alpha/tru64/o3-timing/simerr

warn: Sockets disabled, not accepting gdb connections
warn: Prefetch instructions in Alpha do not do anything
warn: Prefetch instructions in Alpha do not do anything
warn: Prefetch instructions in Alpha do not do anything
warn: ignoring syscall sigprocmask(0, 1, ...)
warn: ignoring syscall sigprocmask(18446744073709547831, 1, ...)
hack: be nice to actually delete the event here
tests: perlbmk now works. Commit stats and assume the're right. Kevin fixed how O3 handles syscalls that change NextPC (longjump). 2008-09-28 23:15:50 +02:00			`warn: Sockets disabled, not accepting gdb connections`
alpha:o3:simple: update simout/err files A few prior changesets have changed the gem5 output in a way that wont cause errors but may be confusing for someone trying to debug the regressions. Ones that I caught were: - no more "warn: <hash address" - typo in the ALPHA Prefetch unimplemented warning Additionaly, the last updated stats changes rearrange the ordering of the stats output even though they are still correct stats (gem5 is smart enough to detect this). All the regressions pass w/the same stats even though it looks like they are being changed. 2011-06-21 00:57:14 +02:00			`warn: Prefetch instructions in Alpha do not do anything`
			`warn: Prefetch instructions in Alpha do not do anything`
			`warn: Prefetch instructions in Alpha do not do anything`
stats: update stats for the changes I pushed re: shared cache occupancy 2010-02-25 19:08:41 +01:00			`warn: ignoring syscall sigprocmask(0, 1, ...)`
stats: update stats for preceding coherence changes Because the handling of the E state for multilevel caches has changed, stats are affected for any non-ruby config with caches, even uniprocessor simple CPU. 2010-09-09 20:40:19 +02:00			`warn: ignoring syscall sigprocmask(18446744073709547831, 1, ...)`
			`hack: be nice to actually delete the event here`