Re: r246916 probably broke amd64 build

2013-02-20 Thread Davide Italiano
On Wed, Feb 20, 2013 at 10:54 AM, Dag-Erling Smørgrav wrote: > Davide Italiano 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

Re: r246916 probably broke amd64 build

2013-02-20 Thread Dag-Erling Smørgrav
Davide Italiano 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 platfo

Re: r246916 probably broke amd64 build

2013-02-19 Thread Davide Italiano
On Tue, Feb 19, 2013 at 3:22 PM, Simon L. B. Nielsen 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 > -Wmis

r246916 probably broke amd64 build

2013-02-19 Thread Simon L. B. Nielsen
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-s