Work around different C implentations

[libfirm] / testprograms / array-stack_example.c

diff --git a/testprograms/array-stack_example.c b/testprograms/array-stack_example.c
index 7153543..cda2601 100644 (file)
--- a/testprograms/array-stack_example.c
+++ b/testprograms/array-stack_example.c
@@ -1,9 +1,9 @@
  /* Copyright (C) 1998 - 2000 by Universitaet Karlsruhe
-** All rights reserved.
-**
-** Authors: Goetz Lindenmaier
-**
-** testprogram.
+* All rights reserved.
+*
+* Authors: Goetz Lindenmaier
+*
+* testprogram.
 */
 
 # include <string.h>
@@ -13,24 +13,24 @@
 # include "irdump.h"
 # include "firm.h"
 
-/**  This example describes representation of stack allocated variables of
-***  imperative programs.
-***  It constructs the IR for the following program:
-***
-***
-***  main(): int
-***    int a[10];
-***
-***    return (a[3]);
-***  end;
-***
-***  The array is placed on the stack, i.e., a pointer to the array
-***  is obtained by selecting the entity "a" from the stack.  The variables
-***  on the stack are considered to be entities of the method, as locals
-***  of a method are only visible within the method.  (An alternative to
-***  make the method owner of the stack variables is to give the ownership
-***  to the class representing the C-file.  This would extend the visibility
-***  of the locals, though.)
+/**
+*  imperative programs.
+*  It constructs the IR for the following program:
+*
+*
+*  main(): int
+*    int a[10];
+*
+*    return (a[3]);
+*  end;
+*
+*  The array is placed on the stack, i.e., a pointer to the array
+*  is obtained by selecting the entity "a" from the stack.  The variables
+*  on the stack are considered to be entities of the method, as locals
+*  of a method are only visible within the method.  (An alternative to
+*  make the method owner of the stack variables is to give the ownership
+*  to the class representing the C-file.  This would extend the visibility
+*  of the locals, though.)
 **/
 
 
@@ -59,7 +59,7 @@ main(void)
   ir_graph       *main_irg;
   ir_node        *array_ptr, *c3, *elt, *val, *x;
 
-  init_firm ();
+  init_firm (NULL);
 
   printf("\nCreating an IR graph: ARRAY-STACK_EXAMPLE...\n");
 
@@ -84,8 +84,8 @@ main(void)
 # define U_BOUND 9
   array_type = new_type_array(id_from_str("a_tp", 4), N_DIMS, prim_t_int);
   set_array_bounds(array_type, 1,
-                  new_Const(mode_Iu, tarval_from_long (mode_Iu, L_BOUND)),
-                  new_Const(mode_Iu, tarval_from_long (mode_Iu, U_BOUND)));
+                  new_Const(mode_Iu, new_tarval_from_long (L_BOUND, mode_Iu)),
+                  new_Const(mode_Iu, new_tarval_from_long (U_BOUND, mode_Iu)));
   /* The array is an entity of the method, placed on the mehtod's own memory,
      the stack frame. */
   array_ent = new_entity(get_cur_frame_type(), id_from_str("a", 1), array_type);
@@ -105,7 +105,7 @@ main(void)
      array pointer by (three * elt_size), but this complicates some
      optimizations.) The type information accessible via the entity
      allows to generate the pointer increment later. */
-  c3 = new_Const (mode_Iu, tarval_from_long (mode_Iu, 3));
+  c3 = new_Const (mode_Iu, new_tarval_from_long (3, mode_Iu));
   {
      ir_node *in[1];
      in[0] = c3;