Date: Fri, 22 Mar 2019 09:12:19 -0700 From: D Scott Phillips <d.scott.phillips@intel.com> To: rebecca@bluestop.org, Larry Rosenman <ler@lerctr.org> Cc: freebsd-virtualization@freebsd.org, owner-freebsd-virtualization@freebsd.org Subject: Re: Updating uefi-edk2-bhyve Message-ID: <86k1gqanx8.fsf@intel.com> In-Reply-To: <33fcf111-fe00-4ec7-8a2f-7c53246d756f@Spark> References: <86muln68ld.fsf@intel.com> <1fe3ca3f-be70-99db-e7c0-35c9194c97e4@bluestop.org> <7e84fd01c3f46268c26f9bab8b9fb9bc@lerctr.org> <33fcf111-fe00-4ec7-8a2f-7c53246d756f@Spark>
next in thread | previous in thread | raw e-mail | index | archive | help
rebecca@bluestop.org writes: > On Mar 21, 2019, 9:54 PM -0600, Larry Rosenman <ler@lerctr.org>, wrote: > > out of curiosity, is there any work being done to move this to later > > LLVM/CLANG? > > That=E2=80=99s something else I=E2=80=99m hoping to work on, since gcc 4.= 8 is very > outdated now. It seems to build fine using gcc 7, but I need to test > that it still runs fine. And that=E2=80=99s complicated by the fact that = the > DEBUG build generates a triple fault even with gcc 4.8. You're seeing this firmware triple fault in the DEBUG build of this new firmware? It seems to be functioning properly for me. Do you get any serial output before the fault?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86k1gqanx8.fsf>