public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at techfak dot uni-bielefeld dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/15234] [gfortran] libgfortran doesn't compile on Tru64 UNIX
Date: Tue, 18 May 2004 10:36:00 -0000	[thread overview]
Message-ID: <20040517191043.20053.qmail@sourceware.org> (raw)
In-Reply-To: <20040430190236.15234.ro@techfak.uni-bielefeld.de>


------- Additional Comments From ro at techfak dot uni-bielefeld dot de  2004-05-17 19:10 -------
Subject: Re:  [gfortran] libgfortran doesn't compile on Tru64 UNIX

Bootstrap on alpha-dec-osf5.1b doesn't succeed either, but this time it's a
different failure:

/vol/gnu/src/gcc/gcc-dist/libgfortran/intrinsics/associated.c:26: error: parse error before numeric constant

This happens because <sys/types.h> has

#define TRUE 1
#define FALSE 0

so we get

enum { 0 = 0, 1 = 1 };

But even with the obvious patch below, I run into another error:

/vol/gnu/src/gcc/gcc-dist/libgfortran/generated/exp_c4.c:29: error: conflicting types for 'cabsf'
/vol/gcc/obj/gcc-3.5.0-20040517/5.1b-gcc/gcc/include/math.h:315: error: previous declaration of 'cabsf' was here
make[3]: *** [exp_c4.lo] Error 1

I.e.

GFC_REAL_4 cabsf (GFC_COMPLEX_4 z); 

vs.

extern float cabsf ( float, float );

This is similar to PR libfortran/15266, which isn't fixed yet, either.

	Rainer


Mon May 17 20:56:21 2004  Rainer Orth  <ro@TechFak.Uni-Bielefeld.DE>

	* intrinsics/associated.c: Renamed FALSE, TRUE to GFC_FALSE,
	GFC_TRUE.

Index: intrinsics/associated.c
===================================================================
RCS file: /cvs/gcc/gcc/libgfortran/intrinsics/associated.c,v
retrieving revision 1.2
diff -u -p -r1.2 associated.c
--- intrinsics/associated.c	13 May 2004 06:41:02 -0000	1.2
+++ intrinsics/associated.c	17 May 2004 18:59:06 -0000
@@ -23,7 +23,7 @@ Boston, MA 02111-1307, USA.  */
 
 #define associated prefix(associated)
 
-enum { FALSE = 0, TRUE = 1 };
+enum { GFC_FALSE = 0, GFC_TRUE = 1 };
 
 
 GFC_LOGICAL_4
@@ -32,19 +32,19 @@ associated (const gfc_array_void *pointe
   int n, rank;
 
   if (GFC_DESCRIPTOR_DATA (pointer) != GFC_DESCRIPTOR_DATA (target))
-    return FALSE;
+    return GFC_FALSE;
   if (GFC_DESCRIPTOR_DTYPE (pointer) != GFC_DESCRIPTOR_DTYPE (target))
-    return FALSE;
+    return GFC_FALSE;
 
   rank = GFC_DESCRIPTOR_RANK (pointer);
   for (n = 0; n < rank; n++)
     {
       if (pointer->dim[n].stride != target->dim[n].stride)
-        return FALSE;
+        return GFC_FALSE;
       if ((pointer->dim[n].ubound - pointer->dim[n].lbound)
           != (target->dim[n].ubound - target->dim[n].lbound))
-        return FALSE;
+        return GFC_FALSE;
     }
 
-  return  TRUE;
+  return  GFC_TRUE;
 }


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15234


  parent reply	other threads:[~2004-05-17 19:10 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-30 19:20 [Bug fortran/15234] New: [tree-ssa] " gcc-bugzilla at gcc dot gnu dot org
2004-04-30 19:34 ` [Bug libfortran/15234] " pinskia at gcc dot gnu dot org
2004-05-07  9:03 ` cvs-commit at gcc dot gnu dot org
2004-05-07  9:09 ` steven at gcc dot gnu dot org
2004-05-07  9:11 ` steven at gcc dot gnu dot org
2004-05-10 13:59 ` ro at techfak dot uni-bielefeld dot de
2004-05-10 13:59 ` ro at techfak dot uni-bielefeld dot de
2004-05-10 14:09 ` ro at gcc dot gnu dot org
2004-05-14  9:54 ` [Bug libfortran/15234] [gfortran] " pinskia at gcc dot gnu dot org
2004-05-15 12:27 ` tobi at gcc dot gnu dot org
2004-05-16 21:45 ` cvs-commit at gcc dot gnu dot org
2004-05-16 21:46 ` tobi at gcc dot gnu dot org
2004-05-16 22:04 ` pinskia at gcc dot gnu dot org
2004-05-18  1:17 ` ro at techfak dot uni-bielefeld dot de
2004-05-18  5:08 ` ro at techfak dot uni-bielefeld dot de
2004-05-18 10:36 ` ro at techfak dot uni-bielefeld dot de [this message]
2004-05-18 11:45 ` pinskia at gcc dot gnu dot org
2004-05-18 23:20 ` ro at techfak dot uni-bielefeld dot de
2004-05-19  5:11 ` tobi at gcc dot gnu dot org
2004-05-27 21:08 ` cvs-commit at gcc dot gnu dot org
2004-07-15 14:53 ` [Bug libfortran/15234] " cvs-commit at gcc dot gnu dot org
2004-07-15 15:03 ` tobi at gcc dot gnu dot org
2004-08-04  7:20 ` pinskia at gcc dot gnu dot org
2004-08-11 21:56 ` pinskia at gcc dot gnu dot org
2004-11-18 11:32 ` paul dot richard dot thomas at cea dot fr
2004-11-18 12:18 ` [Bug libfortran/15234] libgfortran doesn't compile on Tru64 4.0f UNIX pinskia at gcc dot gnu dot org
2004-11-20 15:45 ` [Bug libfortran/15234] libgfortran doesn't compile on Tru64 UNIX V4.0F pinskia at gcc dot gnu dot org
2004-12-01 18:15 ` mmitchel at gcc dot gnu dot org
2005-01-06 14:40 ` tobi at gcc dot gnu dot org
2005-06-13 16:04 ` fxcoudert at gcc dot gnu dot org
2005-07-19 10:32 ` fxcoudert at gcc dot gnu dot org
2005-08-16 19:28 ` tobi at gcc dot gnu dot org
2005-08-16 19:34 ` ro at techfak dot uni-bielefeld dot de
2005-08-17  2:24 ` pinskia at gcc dot gnu dot org
2005-09-05 10:43 ` fxcoudert at gcc dot gnu dot org
2005-09-22 17:50 ` fxcoudert at gcc dot gnu dot org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040517191043.20053.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).