Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@cup.hp.com>
To: gcc-patches@gcc.gnu.org
Cc: parisc-linux@thepuffingroup.com
Subject: [parisc-linux] PATCH: build gcc/gcc/depedence.c w/HPUX ANSI C
Date: Thu, 31 Aug 2000 19:20:06 -0700	[thread overview]
Message-ID: <200009010220.TAA20141@milano.cup.hp.com> (raw)


Hi folks,
I work on the parisc-linux port and was trying to build binutils/gcc
on an HP-UX 11 system. HP-UX ansic didn't like enum direction_type[][]
or int[][] constructs.  It complained with:
cc: "/linux/pa32/gcc/gcc/dependence.c", line 199: error 1501: Only the first
	dimension of an array may be omitted.

I've been told GCC refuses to compile the same thing with:
	x.c:1: warning: array `i' assumed to have one element
	x.c:1: storage size of `i' isn't known

This is probably not exactly the right fix but at least I can
build a binary now. I haven't tested the resulting binary.

thanks,
grant

grundler <815>cvs diff gcc/gcc/dependence.c
Index: gcc/gcc/dependence.c
===================================================================
RCS file: /home/cvs/parisc/gcc/gcc/dependence.c,v
retrieving revision 1.1
diff -u -p -r1.1 dependence.c
--- dependence.c        2000/08/22 20:56:22     1.1
+++ dependence.c        2000/08/31 23:44:27
@@ -196,15 +196,15 @@ static int get_one_coefficient PARAMS ((
 static void normalize_coefficients PARAMS ((subscript[], loop*, int));
 static void classify_dependence PARAMS ((subscript[], subscript[],
                                 enum complexity_type[], int*, int));
-static void ziv_test PARAMS ((subscript[], subscript[], enum direction_type[][],
-                     int[][], loop*, int));
-static void siv_test PARAMS ((subscript[], subscript[], enum direction_type[][],
-                     int[][], loop*, int));
+static void ziv_test PARAMS ((subscript[], subscript[], enum direction_type[MAX_SUBSCRIPTS][MAX_SUBSCRIPTS],
+                     int[MAX_SUBSCRIPTS][MAX_SUBSCRIPTS], loop*, int));
+static void siv_test PARAMS ((subscript[], subscript[], enum direction_type[MAX_SUBSCRIPTS][MAX_SUBSCRIPTS],
+                     int[MAX_SUBSCRIPTS][MAX_SUBSCRIPTS], loop*, int));
 static int check_subscript_induction PARAMS ((subscript*, subscript*, loop*));
-static void gcd_test PARAMS ((subscript[], subscript[], enum direction_type[][],
-                     int[][], loop*, int));
+static void gcd_test PARAMS ((subscript[], subscript[], enum direction_type[MAX_SUBSCRIPTS][MAX_SUBSCRIPTS],
+                     int[MAX_SUBSCRIPTS][MAX_SUBSCRIPTS], loop*, int));
 static int find_gcd PARAMS ((int, int));
-static void merge_dependencies PARAMS ((enum direction_type[][], int[][], int, int));
+static void merge_dependencies PARAMS ((enum direction_type[MAX_SUBSCRIPTS][MAX_SUBSCRIPTS], int[MAX_SUBSCRIPTS][MAX_SUBSCRIPTS], int, int));
 static void dump_array_ref PARAMS ((tree));
 static void dump_one_node PARAMS ((def_use*, varray_type*));
 static void dump_node_dependence PARAMS ((void));

             reply	other threads:[~2000-09-01  2:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-01  2:20 Grant Grundler [this message]
2000-09-01  2:48 ` [parisc-linux] PATCH: build gcc/gcc/depedence.c w/HPUX ANSI C John David Anglin

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=200009010220.TAA20141@milano.cup.hp.com \
    --to=grundler@cup.hp.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=parisc-linux@thepuffingroup.com \
    /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