[Bug 248995] devel/avarice: current llvm 11.0.0 fallout

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Sat Aug 29 20:19:02 UTC 2020


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248995

            Bug ID: 248995
           Summary: devel/avarice: current llvm 11.0.0 fallout
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: joerg at FreeBSD.org
          Reporter: leres at freebsd.org
             Flags: maintainer-feedback?(joerg at FreeBSD.org)
          Assignee: joerg at FreeBSD.org

Building on FreeBSD 13.0-CURRENT (r364847) produces two fatal errors:

    --- devdescr.o ---
    devdescr.cc:2251:2: error: type 'gdb_io_reg_def_type []' cannot be narrowed
to 'bool' in initializer list [-Wc++11-narrowing]
            atmega32m1_io_registers,
            ^~~~~~~~~~~~~~~~~~~~~~~
    devdescr.cc:2251:2: note: insert an explicit cast to silence this issue
            atmega32m1_io_registers,
            ^~~~~~~~~~~~~~~~~~~~~~~
            static_cast<bool>(     )
    devdescr.cc:2375:2: error: type 'gdb_io_reg_def_type []' cannot be narrowed
to 'bool' in initializer list [-Wc++11-narrowing]
            atmega32c1_io_registers,
            ^~~~~~~~~~~~~~~~~~~~~~~
    devdescr.cc:2375:2: note: insert an explicit cast to silence this issue
            atmega32c1_io_registers,
            ^~~~~~~~~~~~~~~~~~~~~~~
            static_cast<bool>(     )
    devdescr.cc:2375:2: warning: address of array 'atmega32c1_io_registers'
will always evaluate to 'true' [-Wpointer-bool-conversion]
            atmega32c1_io_registers,
            ^~~~~~~~~~~~~~~~~~~~~~~
    devdescr.cc:2251:2: warning: address of array 'atmega32m1_io_registers'
will always evaluate to 'true' [-Wpointer-bool-conversion]
            atmega32m1_io_registers,
            ^~~~~~~~~~~~~~~~~~~~~~~
    2 warnings and 2 errors generated.

The problem appears to be two instances of static initialization of the wrong
field. These look like straight up bugs to me that the newer compiler with
better warning detects.

I also filed an upstream bug report:

    https://sourceforge.net/p/avarice/bugs/28/

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-ports-bugs mailing list