This is the mail archive of the mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[PATCH] always define __sparc64__ on ultrasparc

This patch would be a big help to FreeBSD, and I image the other BSD's
as well.  W/o this patch ``gcc -mcpu=ultrasparc'' causes __sparc64__ to
not be defined on FreeBSD (which we need).  Is it possible that
specifying an implied 64-bit value for mcpu should not nullify

Since __sparc64__ is in the compilers namespace, I don't think this patch
will cause a problem for anyone.

2002-05-16  David O'Brien  <>

	* config/sparc/sparc.h (CPP_CPU_SPEC): Define __sparc64__ when
	mcpu specifies ultrasparc.

Index: config/sparc/sparc.h
RCS file: /cvs/gcc/egcs/gcc/config/sparc/sparc.h,v
retrieving revision 1.195
diff -u -r1.195 sparc.h
--- config/sparc/sparc.h	15 May 2002 05:30:00 -0000	1.195
+++ config/sparc/sparc.h	17 May 2002 04:01:56 -0000
@@ -235,8 +235,8 @@
 %{mcpu=hypersparc:-D__hypersparc__ -D__sparc_v8__} \
 %{mcpu=sparclite86x:-D__sparclite86x__} \
 %{mcpu=v9:-D__sparc_v9__} \
-%{mcpu=ultrasparc:-D__sparc_v9__} \
-%{mcpu=ultrasparc3:-D__sparc_v9__} \
+%{mcpu=ultrasparc:-D__sparc_v9__ -D__sparc64__} \
+%{mcpu=ultrasparc3:-D__sparc_v9__ -D__sparc64__} \
 %{!mcpu*:%{!mcypress:%{!msparclite:%{!mf930:%{!mf934:%{!mv8:%{!msupersparc:%(cpp_cpu_default)}}}}}}} \

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]