This is the mail archive of the gcc-patches@gcc.gnu.org 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]

Re: [Bug bootstrap/9697] [3.4 regression] wrong assembly emitted for m68000 __umulsidi3


dhazeghi at yahoo dot com wrote:-

> PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
> 
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9697
> 
> 
> 
> ------- Additional Comments From dhazeghi at yahoo dot com  2003-06-28 06:58 -------
> The original one yes. But the current bug starts at comment #6 on, and is present only on mainline 
> (not on gcc 3.2 or 3.3), and is, I suspect, related to the conversion. If it would make things clearer, 
> I can open this as a new bug... Thanks,

In 3.3, it appears that m68k-elf includes m68020-elf.h:

tm_file="m68k/m68k-none.h m68k/m68kelf.h dbxelf.h elfos.h m68k/m68kemb.h
m68k/m68020-elf.h"

and in 3.4.  Naming conventions on this port seem to be a bit confused.

Anyway, does this fix it?

Neil.

	* config/m68k/m68k.h (TARGET_CPU_CPP_BUILTINS): Predicate
	__mc68020__ on TARGET_68020.

Index: m68k.h
===================================================================
RCS file: /cvs/gcc/gcc/gcc/config/m68k/m68k.h,v
retrieving revision 1.90
diff -u -p -r1.90 m68k.h
--- m68k.h	19 Jun 2003 21:47:15 -0000	1.90
+++ m68k.h	28 Jun 2003 07:30:53 -0000
@@ -29,7 +29,8 @@ Boston, MA 02111-1307, USA.  */
   do						\
     {						\
 	builtin_define ("__mc68000__");		\
-	builtin_define ("__mc68020__");		\
+	if (TARGET_68020)			\
+	  builtin_define ("__mc68020__");	\
 	builtin_define ("__m68k__");		\
 	builtin_assert ("cpu=m68k");		\
 	builtin_assert ("machine=m68k");	\


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