Re: sparc64 vs. gcc 4.8

"Erik E. Fair" <[email protected]>
Newsgroups gmane.os.netbsd.ports.sparc64
Message-ID <[email protected]> 
Is the divergence in memory ordering semantics and mutex implementation
something which can be remedied within the existing mutex API, or should that
API be changed/adjusted also? Or, put another way, can the different semantics
be virtualized in a reasonable way for MI code, or should we (for best
performance, or just correct operation) make more separately maintained MD
code for sparc?

	Erik <[email protected]>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.