public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
* Segfault on arm-linux-gnueabi
@ 2007-05-15 21:47 Paul Brook
  2007-05-16  8:12 ` Martin Michlmayr
  0 siblings, 1 reply; 3+ messages in thread
From: Paul Brook @ 2007-05-15 21:47 UTC (permalink / raw)
  To: fortran; +Cc: gcc-patches

The patch below fixes a crash building libgfortran on arm-linux-gnueabi.

This target doesn't really have a 128-bit integer type, however it does use 
TImode to represent the return value of certain special ABI defined library 
functions. This results in type_for_size(TImode) being called.

Because TImode deosn't correspond to any gfortran integer kind 
gfc_type_for_size returns NULL and we segfault shortly after.

The patch below fixes this by making gfc_type_for_size handle TImode in the 
same way as the C frontend.

Tested on x86_64-linux and arm-linux-gnueabi.
Applied to trunk.

Paul

2007-05-15  Paul Brook  <paul@codesourcery.com>

	gcc/fortran/
	* trans-types.c (gfc_type_for_size): Handle signed TImode.

Index: gcc/fortran/trans-types.c
===================================================================
--- gcc/fortran/trans-types.c	(revision 170435)
+++ gcc/fortran/trans-types.c	(working copy)
@@ -1800,6 +1800,13 @@ gfc_type_for_size (unsigned bits, int un
 	  if (type && bits == TYPE_PRECISION (type))
 	    return type;
 	}
+
+      /* Handle TImode as a special case because it is used by some backends
+         (eg. ARM) even though it is not available for normal use.  */
+#if HOST_BITS_PER_WIDE_INT >= 64
+      if (bits == TYPE_PRECISION (intTI_type_node))
+	return intTI_type_node;
+#endif
     }
   else
     {

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2007-05-16 19:06 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-05-15 21:47 Segfault on arm-linux-gnueabi Paul Brook
2007-05-16  8:12 ` Martin Michlmayr
2007-05-16 19:06   ` Paul Brook

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).