From 220649ca78f729f8d65f75ebd45025d8c9f9cbe6 Mon Sep 17 00:00:00 2001 From: knu Date: Mon, 6 Jan 2003 16:37:29 +0000 Subject: [PATCH] [Forced commit] I was wrong about something. It was a return value, not arguments that are not covered by the int-to-long promotion rule on IA64, if the function is not explicitly declared. The commit itself was generally a right thing to do, but just let me correct my commit message. git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@3304 b2dd03c8-39d4-4d8f-98ff-823fe69b080e --- ChangeLog | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/ChangeLog b/ChangeLog index b407ac662f..ebd6020466 100644 --- a/ChangeLog +++ b/ChangeLog @@ -4,11 +4,7 @@ Mon Jan 6 23:36:29 2003 Akinori MUSHA st_compare_func_t, st_hash_func_t and st_each_func_t. * st.h, st.c: Do explicit function declarations and do not rely on - implicit declarations. On such platforms as IA64, int argument - values are NOT automatically promoted to long (64bit) values, so - explicit declarations are mandatory for those functions that - take long values or pointers. This fixes miniruby's coredump on - FreeBSD/IA64. + implicit declarations. * class.c, eval.c, gc.c, hash.c, marshal.c, parse.y, variable.c: Add proper casts to avoid warnings.