Re: r246916 probably broke amd64 build
Davide Italiano dav...@freebsd.org writes: Unfortunately tinderbox didn't catch this bug because it's triggered only when gcc is used to build kernel. In this particular case, the broken code is only built on platforms which default to clang. Otherwise, it would have been caught when building one of the platforms that default to gcc. The tinderbox servers simply donn't have enough CPU power to build all possible combinations. There isn't even enough for a standard build of all platforms at a reasonable frequency. I have a stack of new servers, but nowhere to host them - see the donations wantlist for details. DES -- Dag-Erling Smørgrav - d...@des.no ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: r246916 probably broke amd64 build
On Wed, Feb 20, 2013 at 10:54 AM, Dag-Erling Smørgrav d...@des.no wrote: Davide Italiano dav...@freebsd.org writes: Unfortunately tinderbox didn't catch this bug because it's triggered only when gcc is used to build kernel. In this particular case, the broken code is only built on platforms which default to clang. Otherwise, it would have been caught when building one of the platforms that default to gcc. I see. In fact this was a very unlucky case (problem in MD code, for a platform that default to clang). The tinderbox servers simply donn't have enough CPU power to build all possible combinations. There isn't even enough for a standard build of all platforms at a reasonable frequency. I have a stack of new servers, but nowhere to host them - see the donations wantlist for details. DES -- Dag-Erling Smørgrav - d...@des.no Sorry I can't help you with that. Thanks, Davide ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
r246916 probably broke amd64 build
Hey, I think r246916 broke the build. I get the following when building amd64 kernel: cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror /usr/src/sys/x86/isa/clock.c cc1: warnings being treated as errors /usr/src/sys/x86/isa/clock.c: In function 'set_i8254_freq': /usr/src/sys/x86/isa/clock.c:409: warning: 'new_mode' may be used uninitialized in this function Could you have a look? Thanks. -- Simon L. B. Nielsen ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: r246916 probably broke amd64 build
On Tue, Feb 19, 2013 at 3:22 PM, Simon L. B. Nielsen si...@qxnitro.org wrote: Hey, I think r246916 broke the build. I get the following when building amd64 kernel: cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror /usr/src/sys/x86/isa/clock.c cc1: warnings being treated as errors /usr/src/sys/x86/isa/clock.c: In function 'set_i8254_freq': /usr/src/sys/x86/isa/clock.c:409: warning: 'new_mode' may be used uninitialized in this function Could you have a look? Thanks. -- Simon L. B. Nielsen ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org It's fixed (r247000). Unfortunately tinderbox didn't catch this bug because it's triggered only when gcc is used to build kernel. Thanks, Davide ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
