We have a frequently occurring hack to "Avoid an ICE in gcc2 on 
sparc64". A few occurrences are in package hacks.mk files. A whole 
bunch more are in package Makefiles:

$ grep -l 'ICE.*sparc64' */*/Makefile*
audio/faad2/Makefile
audio/lame/Makefile
audio/libid3tag/Makefile
audio/libmad/Makefile
audio/libsndfile/Makefile
audio/libvorbis/Makefile
audio/madplay/Makefile
audio/speex/Makefile
chat/irssi/Makefile
chat/silc-server/Makefile
databases/dbh/Makefile
databases/libpqxx/Makefile
databases/mysql-client/Makefile.common
databases/mysql4-client/Makefile.common
devel/atk/Makefile
devel/glib2/Makefile
devel/pango/Makefile
devel/pcre/Makefile
devel/silc-toolkit/Makefile
devel/ucl/Makefile
graphics/lcms/Makefile
lang/chicken/Makefile
net/libIDL/Makefile
security/gpgme/Makefile
www/curl/Makefile
www/libwww/Makefile
www/tinyproxy/Makefile
x11/lesstif/Makefile
x11/xosd/Makefile.common

On the one hand, existing practice suggests splitting these instances 
into hacks.mk files. On the other hand, that's a lot of duplication for 
a hack that, in practice, looks pretty common. Would it make sense to 
provide a definition for "sparc64-gcc2-ice" in bsd.hacks.mk, and 
provide a way for a package to indicate that it needs this particular 
hack?

- Amitai