[#29911] [Bug #3231] Digest Does Not Build — Charlie Savage <redmine@...>

Bug #3231: Digest Does Not Build

19 messages 2010/05/01

[#29920] [Feature #3232] Loops (while/until) should return last statement value if any, like if/unless — Benoit Daloze <redmine@...>

Feature #3232: Loops (while/until) should return last statement value if any, like if/unless

9 messages 2010/05/01

[#29997] years in Time.utc — Xavier Noria <fxn@...>

Does anyone have a precise statement about the years supported by

13 messages 2010/05/04

[#30010] [Bug #3248] extension 'tk' is finding tclConfig.sh and tkConfig.sh incorrectly — Luis Lavena <redmine@...>

Bug #3248: extension 'tk' is finding tclConfig.sh and tkConfig.sh incorrectly

9 messages 2010/05/05

[#30226] [Bug #3288] Segmentation fault - activesupport-3.0.0.beta3/lib/active_support/callbacks.rb:88 — Szymon Jeż <redmine@...>

Bug #3288: Segmentation fault - activesupport-3.0.0.beta3/lib/active_support/callbacks.rb:88

10 messages 2010/05/13

[#30358] tk doesn't startup well in doze — Roger Pack <rogerdpack2@...>

Currently with 1.9.x and tk 8.5,the following occurs

12 messages 2010/05/22

[ruby-core:30500] [Bug #1296] [trunk/22981] 64-bit issues on trunk in ext/zlib

From: Yusuke Endoh <redmine@...>
Date: 2010-05-29 21:30:01 UTC
List: ruby-core #30500
Issue #1296 has been updated by Yusuke Endoh.

Priority changed from Normal to Low
Target version changed from 1.9.2 to 1.9.x

Hi,

Thank you, Benoit.

2010/5/30 Benoit Daloze <eregontp@gmail.com>:
> Well, actually there are hundreds of them:
> $ cat make.log | grep 'warning: implicit conversion shortens 64-bit
> value into a 32-bit value' | wc -l #=> 375

Umm...  I wonder why OP reported only about zlib's warnings.


And I remembered you had posted recent make.log in ticket #3255:
https://gist.github.com/c8034f83cc9afbf79e6b

I glanced over a part of zlib, and I guess nearly all warnings
are false positive.  Some struct fields of zlib are int types,
and RSTRING_LEN(buf), which returns long type, is assigned to
the field.  But the `buf' seems to be created based on int-typed
length.  So the warnings are benign.

Of course some may be malignant.  If anyone realizes actual issue,
please let us know.


> It would indeed be nice to not have these warnings, but I suppose it
> is not so easy to solve.

Agreed.
To fix them, tons of casts will be needed.  I'm afraid if it may
enbug another issue.  Thus, at least in 1.9.2 release, we won't
fix these warnings unless actual issue is reported.

Thanks again!

-- 
Yusuke Endoh <mame@tsg.ne.jp>
----------------------------------------
http://redmine.ruby-lang.org/issues/show/1296

----------------------------------------
http://redmine.ruby-lang.org

In This Thread