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

warn: DRAM device capacity (8192 Mbytes) does not match the address range assigned (128 Mbytes)
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(1, ...)
warn: ignoring syscall sigprocmask(1, ...)
stats: update for previous changeset Very small differences in IQ-specific O3 stats. 2015-04-23 05:22:29 +02:00			`warn: DRAM device capacity (8192 Mbytes) does not match the address range assigned (128 Mbytes)`
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 for syscall DPRINTF change Only printing one rather than two args for the ignored syscall warning means the count of register accesses has changed on a few runs. Oddly only Alpha Tru64 seems to have any ignored syscalls in the regression tests. 2014-07-20 04:04:58 +02:00			`warn: ignoring syscall sigprocmask(1, ...)`
			`warn: ignoring syscall sigprocmask(1, ...)`