Subject: 264 binaries ok? SRM_CHECK available for linux? (fwd)
To: None <firstname.lastname@example.org, email@example.com>
From: Matthew Jacob <firstname.lastname@example.org>
Date: 04/14/1999 08:50:11
raising the issue for anyone with concerns
---------- Forwarded message ----------
Date: 14 Apr 1999 13:16:40 +0300
From: Harvey J. Stein <email@example.com>
Subject: 264 binaries ok? SRM_CHECK available for linux?
Resent-Date: 14 Apr 1999 10:39:40 -0000
Resent-cc: recipient list not shown: ;
I just found this on the openvms page:
Ensuring Proper Use of Interlocked Memory Instructions
The Alpha Architecture Reference Manual, Third Edition (AARM)
describes strict rules for using interlocked memory
instructions. The forthcoming Alpha 21264 (EV6) processor and all
future Alpha processors are more stringent than their predecessors
in their requirement that these rules be followed. As a result,
code that has worked in the past despite noncompliance may now fail
when executed on systems featuring the new 21264 processor.
Does anyone know if this is relevant to gcc on linux? The above page
includes a tool which finds inconsistencies in a binary (on VMS
systems, of course):
Does anyone know if such a thing is needed and/or available for Linux?
I didn't find any such caveats on the "Tru64 Unix" pages.
Harvey J. Stein
BFM Financial Research
To unsubscribe: send e-mail to firstname.lastname@example.org with
'unsubscribe' as the subject. Do not send it to email@example.com