1berry/ruby
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

[Forced commit]

Browse Source 
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
This commit is contained in:
knu 2003-01-06 16:37:29 +00:00
parent 91b9d37a85
commit 220649ca78
1 changed files with 1 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
ChangeLog
View File

@ -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_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 * st.h, st.c: Do explicit function declarations and do not rely on
implicit declarations. On such platforms as IA64, int argument implicit declarations.
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.
* class.c, eval.c, gc.c, hash.c, marshal.c, parse.y, variable.c: * class.c, eval.c, gc.c, hash.c, marshal.c, parse.y, variable.c:
Add proper casts to avoid warnings. Add proper casts to avoid warnings.