From d72a0b5c618a37b70ba4d111b457deefad8f025f Mon Sep 17 00:00:00 2001 From: Tor Lillqvist Date: Thu, 27 Dec 2012 13:37:20 +0200 Subject: Check for __GNUC__ instead of GCC in sources We still have checks for $(COM) being GCC or MSC in makefiles, of course. But there is no reason to pass -D$(COM) to compilations. Checking the built-in compiler-specific macros __GNUC__, _MSC_VER (etc) is the right thing to do. Change-Id: Ia961a29ba74e2c4977e5300a92318f38104c6592 --- cppuhelper/source/component_context.cxx | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) (limited to 'cppuhelper') diff --git a/cppuhelper/source/component_context.cxx b/cppuhelper/source/component_context.cxx index a44ec951b885..c168aa2a32b7 100644 --- a/cppuhelper/source/component_context.cxx +++ b/cppuhelper/source/component_context.cxx @@ -240,7 +240,9 @@ static OUString val2str( void const * pVal, typelib_TypeDescriptionReference * p case typelib_TypeClass_HYPER: case typelib_TypeClass_UNSIGNED_HYPER: buf.appendAscii( RTL_CONSTASCII_STRINGPARAM("0x") ); -#if defined(GCC) && defined(SPARC) +#if defined(__GNUC__) && defined(SPARC) +// I guess this really should check if there are strict alignment +// requirements, not just "GCC on SPARC". { sal_Int64 aVal; *(sal_Int32 *)&aVal = *(sal_Int32 *)pVal; -- cgit