... again, that's why I'm suggesting they post some further details, such as the disassembly in question.
The contents of /etc/src.cnof and /etc/make.conf would be useful too, as well as a verbose dmesg just to make sure devices and CPU flags are all there. Who knows, it could be some corner case of optimisation that's screwing him, or a bad choice of instruction for his given platform, etc, etc. Adrian On 4 February 2013 13:09, Andriy Gapon <[email protected]> wrote: > on 04/02/2013 23:06 Adrian Chadd said the following: >> I'm not the right person for it, but I think it's worth wrapping up >> all my requested details in a PR so Those Who Know can take a peek. >> >> Especially if it boils down to the choice of compiler. Who knows what >> other weird corner issues people will see with clang compiling their >> drivers? > > OK, I'll ask the user to open a PR. > I'll just note that the problem seems to be too strange... > There is a huge distance from compiler to nmi. > > -- > Andriy Gapon _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[email protected]"
