[prev in list] [next in list] [prev in thread] [next in thread] 

List:       perl5-changes
Subject:    [perl.git]  branch smoke-me/gcc460, created. v5.13.11-332-gdcddeba
From:       "Nicholas Clark" <nick () ccl4 ! org>
Date:       2011-03-29 14:08:57
Message-ID: E1Q4ZbN-00026f-V9 () camel ! ams6 ! corp ! booking ! com
[Download RAW message or body]

In perl.git, the branch smoke-me/gcc460 has been created

<http://perl5.git.perl.org/perl.git/commitdiff/dcddeba64665deae2d03428a58e959c9ab82f83b?hp=0000000000000000000000000000000000000000>


        at  dcddeba64665deae2d03428a58e959c9ab82f83b (commit)

- Log -----------------------------------------------------------------
commit dcddeba64665deae2d03428a58e959c9ab82f83b
Author: Nicholas Clark <nick@ccl4.org>
Date:   Tue Mar 29 15:06:50 2011 +0100

    In Perl_safesyscalloc(), only declare total_size if conditional code needs it.
    
    gcc 4.6.0 warns about variables that are set but never read, and for most
    combinations of conditional compilation options, total_size is never read.
    So avoid declaring or setting it if it's not actually going to be used later.

M	util.c

commit 3d6ff8202f9280ca129bd8b8dfadcc19f4b2cff2
Author: Nicholas Clark <nick@ccl4.org>
Date:   Tue Mar 29 14:15:59 2011 +0100

    In pp_warn and pp_die, eliminate pv, which is assigned to but never read.

M	pp_sys.c

commit 9029c9aff9243ad70f432598981918cd6b9211d9
Author: Nicholas Clark <nick@ccl4.org>
Date:   Tue Mar 29 13:38:13 2011 +0100

    Eliminate C variables unused since 4d0fbddde6c5dcb9 refactored HvFILL()
    
    3 functions had C variables previously used to track whether the number of
    hash chains have any entries. 4d0fbddde6c5dcb9 refactored the hash
    implementation to calculated this on demand, instead of tracking changes to
    it on hash updates. That change missed eliminating those variables, as
    gcc prior to 4.6.0 didn't actually warn that they weren't used, because
    (technically) they aren't unused - they are assigned to, but never read.
    
    gcc (at least 4.3.2 and 4.6.0) generates identical object code with/without
    this change, implying that its optimiser correctly eliminates the code.
    Other optimisers may be similar, in which case there's no runtime saving from
    this change.

M	hv.c
-----------------------------------------------------------------------

--
Perl5 Master Repository


[prev in list] [next in list] [prev in thread] [next in thread]