src-test2/sys/alpha/include/atomic.h, branch release/6.3.0_cvs

This commit was manufactured by cvs2svn to create tag

2008-01-15T15:46:22Z

'RELENG_6_3_0_RELEASE'. This commit was manufactured to restore the state of the 6.3-RELEASE image.

MFC: Add atomic_fetchadd(9) operation for types int and 32.

2005-10-06T18:12:06Z

Other small updates to atomic(9) include: - Note that arm and ppc don't provide 64-bit atomic ops. - Update sample code. Approved by: re (scottl)

MFC: Stop using the '+' constraint modifier with memory operands in

2005-09-26T19:54:19Z

inline assembly. We still use it for register operands in various places. Approved by: re (kensmith)

MFC: Convert the atomic pointer operations to operate on uintptr_t rather

2005-08-05T19:44:00Z

than void *. Approved by: re (kensmith)

Some cleanups and tweaks to some of the atomic.h files in preparation for

2005-07-09T12:38:53Z

further changes and fixes in the future: - Use aliases via macros rather than duplicated inlines wherever possible. - Move all the aliases to the bottom of these files and the inline functions to the top. - Add various comments. - On alpha, drop atomic_{load_acq,store_rel}_{8,char,16,short}(). - On i386 and amd64, don't duplicate the extern declarations for functions in the two non-inline cases (KLD_MODULE and compiler doesn't do inlines), instead, consolidate those two cases. - Some whitespace fixes. Approved by: re (scottl)

netchild's mega-patch to isolate compiler dependencies into a central

2005-03-02T21:33:29Z

place. This moves the dependency on GCC's and other compiler's features into the central sys/cdefs.h file, while the individual source files can then refer to #ifdef __COMPILER_FEATURE_FOO where they by now used to refer to #if __GNUC__ > 3.1415 && __BARC__ <= 42. By now, GCC and ICC (the Intel compiler) have been actively tested on IA32 platforms by netchild. Extension to other compilers is supposed to be possible, of course. Submitted by: netchild Reviewed by: various developers on arch@, some time ago

The previous commit, roughly one and a half years ago removed the

2004-09-10T05:00:27Z

branch prediction optimization for LINT, because the kernel was too large. This commit now removes it altogether since it causes build failures for GENERIC kernels and the various applicable trends are such that one can expect that it these failure will cause more problems than they're worth in the future. These trends include: 1. Alpha was demoted from tier 1 to tier 2 due to lack of active support. The number of people willing to fix build breakages is not likely to increase and those developers that do have the gumption to test MI changes on alpha are not likely to spend time fixing unexpected build failures first. 2. The kernel will only increase in size. Even though stripped-down kernels do link without problems now, compiler optimizations (like inlining) and new (non-optional) functionality will likely cause stripped-down kernels to break in the future as well. So, with my asbestos suit on, get rid of potential problems before they happen. MT5 candidate.

Workaround for compiling LINT. Large kernels (like LINT) can have

2003-02-23T06:34:21Z

branch targets that are too far apart for the BRADDR relocation. This is caused by the branch prediction optimizationi in the atomic inlines here, because they jump across sections. The workaround is to suppress jumping to a different section when compiling LINT. To generate correct code in that case, the section directives are replaced by a branch and a label to deal with the fall-through case. Reasonably good C compilers will optimize this away anyway, so the end result isn't really that bad.

Remove extranious memory barriers, and correct the placement of a few others.

2002-10-30T01:41:44Z

This provides a 30% reduction in system time and a 6% reduction in wallclock time for a make buildworld on my xp1000 (one 21264). FWIW, I've been running this for nearly 2 months without problems. Portions submitted by: ticso, jhb Tested by: jhb (ds20 dual 21264)

Use the newer "+" modifier on output contraints when a register or

2002-10-25T20:22:12Z

memory datum is used for both input and output instead of using matching constraints.