summaryrefslogtreecommitdiffstats
path: root/README
diff options
context:
space:
mode:
authorKen Raeburn <raeburn@mit.edu>2008-07-22 19:15:52 +0000
committerKen Raeburn <raeburn@mit.edu>2008-07-22 19:15:52 +0000
commitae629b14a7d2f1564d09f3ef49998ec7e35d2a27 (patch)
treee8a3eb1b797f51b3e5d9103a022f3b7f05a7dadc /README
parentaeb3688ce0a80b53d907863fa1a0611ac1340915 (diff)
downloadkrb5-ae629b14a7d2f1564d09f3ef49998ec7e35d2a27.tar.gz
krb5-ae629b14a7d2f1564d09f3ef49998ec7e35d2a27.tar.xz
krb5-ae629b14a7d2f1564d09f3ef49998ec7e35d2a27.zip
A step towards ensuring we check mutex lock attempt results..
Always use inline function k5_mutex_lock_1 instead of gcc statement expression, even under gcc. Under gcc 4, declane k5_mutex_lock_1 and krb5int_mutex_lock with attribute warn_unused_result. In k5_mutex_destroy macro, only store destroy code source+line if we succeed in temporarily locking the mutex. ticket: 5962 status: open git-svn-id: svn://anonsvn.mit.edu/krb5/trunk@20566 dc483132-0cff-0310-8789-dd5450dbe970
Diffstat (limited to 'README')
0 files changed, 0 insertions, 0 deletions