|author||knu <knu@b2dd03c8-39d4-4d8f-98ff-823fe69b080e>||2003-01-06 16:37:29 +0000|
|committer||knu <knu@b2dd03c8-39d4-4d8f-98ff-823fe69b080e>||2003-01-06 16:37:29 +0000|
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
Diffstat (limited to 'ChangeLog')
1 files changed, 1 insertions, 5 deletions
@@ -4,11 +4,7 @@ Mon Jan 6 23:36:29 2003 Akinori MUSHA <knu@iDaemons.org>
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
+ implicit declarations.
* class.c, eval.c, gc.c, hash.c, marshal.c, parse.y, variable.c:
Add proper casts to avoid warnings.