Re: cppcheck errors

On Tue, Sep 1, 2015 at 5:43 PM, Joel Sherrill wrote: > > > On 9/1/2015 2:10 PM, Martin Galvan wrote: >> >> Hi everyone! >> >> I just ran CppCheck again on a fresh clone of the git repo and saw the >> number of error reports was quite smaller than what I reported before.

Re: cppcheck errors

Hi everyone! I just ran CppCheck again on a fresh clone of the git repo and saw the number of error reports was quite smaller than what I reported before. That's because my previous run was on a (quite older) version; most of those must've been fixed already. Some of the error reports remain,

Re: cppcheck errors

On 9/1/2015 2:10 PM, Martin Galvan wrote: Hi everyone! I just ran CppCheck again on a fresh clone of the git repo and saw the number of error reports was quite smaller than what I reported before. That's because my previous run was on a (quite older) version; most of those must've been fixed

Re: cppcheck errors

On Thu, Aug 27, 2015 at 6:38 PM, Joel Sherrill joel.sherr...@oarcorp.com wrote: On 8/27/2015 4:15 PM, Martin Galvan wrote: On Thu, Aug 27, 2015 at 6:10 PM, Daniel Gutson daniel.gut...@tallertechnologies.com wrote: Maybe we can just provide the list until we provide the fixes? Martín?

Re: cppcheck errors

On 8/13/2015 10:52 AM, Daniel Gutson wrote: El 13/8/2015 12:49, Gedare Bloom ged...@gwu.edu mailto:ged...@gwu.edu escribió: Daniel, Unknown deadline right now. Probably whenever Joel can get around to it! Realistically, we can create a bugfix dot release anytime after the release

Re: cppcheck errors

On Thu, Aug 27, 2015 at 6:19 PM, Daniel Gutson daniel.gut...@tallertechnologies.com wrote: Please note too that there are some false positives, like the realloc one. Actually, we ruled out most false positives. IIRC that one is an actual bug. Btw, sorry for the Spanish comment there. It means

Re: cppcheck errors

On Thu, Aug 27, 2015 at 6:10 PM, Daniel Gutson daniel.gut...@tallertechnologies.com wrote: Maybe we can just provide the list until we provide the fixes? Martín? Gladly. Keep in mind we ran cppcheck only on the modules we use (though some things may've slipped in, like nios):

Re: cppcheck errors

On 8/27/2015 4:10 PM, Daniel Gutson wrote: On Thu, Aug 27, 2015 at 6:06 PM, Joel Sherrill joel.sherr...@oarcorp.com wrote: On 8/13/2015 10:52 AM, Daniel Gutson wrote: El 13/8/2015 12:49, Gedare Bloom ged...@gwu.edu mailto:ged...@gwu.edu escribió: Daniel, Unknown deadline

Re: cppcheck errors

On 8/27/2015 4:15 PM, Martin Galvan wrote: On Thu, Aug 27, 2015 at 6:10 PM, Daniel Gutson daniel.gut...@tallertechnologies.com wrote: Maybe we can just provide the list until we provide the fixes? Martín? Gladly. Keep in mind we ran cppcheck only on the modules we use (though some things

Re: cppcheck errors

On Thu, Aug 27, 2015 at 6:06 PM, Joel Sherrill joel.sherr...@oarcorp.com wrote: On 8/13/2015 10:52 AM, Daniel Gutson wrote: El 13/8/2015 12:49, Gedare Bloom ged...@gwu.edu mailto:ged...@gwu.edu escribió: Daniel, Unknown deadline right now. Probably whenever Joel can get around

obsolete h8300 was Re: cppcheck errors

On 8/27/2015 4:22 PM, Martin Galvan wrote: On Thu, Aug 27, 2015 at 6:19 PM, Daniel Gutson daniel.gut...@tallertechnologies.com wrote: Please note too that there are some false positives, like the realloc one. Actually, we ruled out most false positives. IIRC that one is an actual bug. Btw,

Re: cppcheck errors

Daniel, The release has (unofficially) happened on rtems.git/4.11 branch, from which master is slowly diverging. Any patches you want applied before the official release need to be (1) associated with a ticket on Trac, and (2) apply to both the 4.11 and master branches. Gedare On Wed, Aug 12,

Re: cppcheck errors

Daniel, Unknown deadline right now. Probably whenever Joel can get around to it! Realistically, we can create a bugfix dot release anytime after the release subject to user demand. So, even if you miss the 4.11.0 release with your patches, we can cut a 4.11.1 after applying the patches if you

Re: cppcheck errors

El 13/8/2015 12:49, Gedare Bloom ged...@gwu.edu escribió: Daniel, Unknown deadline right now. Probably whenever Joel can get around to it! Realistically, we can create a bugfix dot release anytime after the release subject to user demand. So, even if you miss the 4.11.0 release with your