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: wide-int, dwarf

From: Jason Merrill <jason at redhat dot com>
To: Mike Stump <mikestump at comcast dot net>, "gcc-patches at gcc dot gnu dot org Patches" <gcc-patches at gcc dot gnu dot org>
Cc: Kenneth Zadeck <zadeck at naturalbridge dot com>
Date: Sat, 23 Nov 2013 20:47:27 -0500
Subject: Re: wide-int, dwarf
Authentication-results: sourceware.org; auth=none
References: <E033ABFE-E76E-47FE-A5F1-823A7F20CCAF at comcast dot net>

On 11/23/2013 02:21 PM, Mike Stump wrote:

-	  if (SCALAR_FLOAT_MODE_P (mode))
+#if TARGET_SUPPORTS_WIDE_INT == 0
+	  if (!SCALAR_FLOAT_MODE_P (mode))
+	    {
+	      mem_loc_result->dw_loc_oprnd2.val_class
+		= dw_val_class_const_double;
+	      mem_loc_result->dw_loc_oprnd2.v.val_double
+		= rtx_to_double_int (rtl);
+	    }
+	  else
+#endif
 	    {
 	      unsigned int length = GET_MODE_SIZE (mode);
 	      unsigned char *array

So if the target supports wide ints you'll always use the scalar floatcode? Why does that do the right thing?


Jason

Follow-Ups:
- Re: wide-int, dwarf
  - From: Kenneth Zadeck

References:
- wide-int, dwarf
  - From: Mike Stump

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