Need help reducing gcc compiler warnings in BSD
rodrigc at FreeBSD.org
Sun Jul 12 02:29:41 UTC 2015
Yes, I agree that formal collaboration is overkill for this stuff, but I
thought I would inform
the DragonFlyBSD community, because I have been benefiting by taking good
done to the DragonFlyBSD tree. One advantage of the Jenkins build is that
the compiler warnings in a table, so it is easy to track over time if
compiler warnings increase or decrease
as code changes are made, so DragonFlyBSD users can monitor that if they
One item I could use help with is that gcc 4.9 compiles FreeBSD's
greater than 8192 bytes, so it is unusable:
I see that DragonFlyBSD has changed a lot of the boot code compared to
I'm not familiar with all the changes. Are there fixes done in this area
that could be pushed back to FreeBSD?
On Fri, Jul 10, 2015 at 3:56 PM, Matthew Dillon <dillon at backplane.com>
> I'm not sure the work load is high enough to require a formal
> collaboration. We just fix things as they come up for the most part.
> Sascha has been doing WARNS related cleanups on the codebase and slowly
> bumping up the WARNS level for various parts of the build for years, which
> reduces problems going forwards. It's mostly a matter of being proactive
> about it.
> On Fri, Jul 10, 2015 at 7:52 AM, Craig Rodrigues <rodrigc at freebsd.org>
>> I set up this Jenkins job which builds FreeBSD with gcc 4.9, and reports
>> all the compiler warnings here:
>> I have been working with other people like Marcelo Araujo to
>> reduce the gcc compiler warnings on FreeBSD, even though
>> the default system compiler for FreeBSD is clang.
>> I have noticed that a lot of fixes to the problems have been down
>> in DragonFlyBSD. I have imported some of these fixes, especially ones
>> done by
>> Sascha Wildner, such as this one:
>> Is there a way that we can collaborate across the FreeBSD and DragonFlyBSD
>> projects to reduce gcc compiler warnings? That it would be quite nice.
>> It would make code easier to share, and improve the code overall.
More information about the freebsd-testing