On Thu, 2022-06-09 at 11:04 +0200, Tim Lange wrote: > Hi everyone, > > my name is Tim and I'm also working on the static analyzer this summer.
Hi Tim - and welcome to GCC development. > Some of you might already noticed my nooby questions in the IRC ;). > Specifically, I'll be working on extending the analyzer with several > smaller warnings that the clang analyzer already has. David created a > meta-bug[0] with the results of the discussion between him and me about > the gap and what seems to be useful. > > I won't do all of those but rather look how many of them I'm able to > get done until September. I will begin with a Cast Size warning. This > emits a warning when the tracked allocation size is not a multiple of > the pointee's size, e.g., when casting malloc(10) to int*. I think this is: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105900 You ought to mark that bug as ASSIGNED to you. Do you have an account for GCC's git and bugzilla yet? See: https://gcc.gnu.org/gitwrite.html#authenticated for info on how to get an account on sourceware.org/gcc.gnu.org I can be your sponsor. Once you have that, I think you automatically get a usern...@gcc.gnu.org account that you can use to login to the GCC bugzilla. > > Furthermore, in preparation for the official coding phase, I played > around a bit with a state machine that tracks whether an int is zero or > not. So this is probably my next candidate after cast size. This would be for: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99669 (generalizing the division-by-zero check) Dave > > - Tim > > [0] > > https://gcc.gnu.org/bugzilla/showdependencytree.cgi?id=105887&hide_resolved=1 > >
