Date: Mon, 4 Feb 2013 13:13:49 -0800 From: Adrian Chadd <adrian@freebsd.org> To: Andriy Gapon <avg@freebsd.org> Cc: freebsd-hackers <freebsd-hackers@freebsd.org> Subject: Re: [clang] NMI while trying to read acpi timer register Message-ID: <CAJ-Vmom=6687bi3fgpE8-2P2wB=2%2BD1-=nv-5pAebC6fXicj-Q@mail.gmail.com> In-Reply-To: <5110238D.8090808@FreeBSD.org> References: <51068B74.2070808@FreeBSD.org> <51098A9E.1080100@FreeBSD.org> <CAJ-VmokD-iiSwb8eqxFq97HQ6Y2Ed__7gHqFyLus=KGGrC9ntA@mail.gmail.com> <5110215B.5000405@FreeBSD.org> <CAJ-Vmokkx2RG6APfNpG2H%2BtPRt=fw7ha0JTtfSr9yUkGh3GxgA@mail.gmail.com> <5110238D.8090808@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
... 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 <avg@freebsd.org> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmom=6687bi3fgpE8-2P2wB=2%2BD1-=nv-5pAebC6fXicj-Q>