within the XEN amd64 dom0 build is resolved.
Detail:
The xen public headers >= 0x00030201 depend on a linuxism - a memory
barrier "API" namely mb(), rmb() and wmb(). These are made accessible
to NetBSD code via the interface
sys/external/bsd/common/include/asm/barrier.h
Currently the ixg(4) driver uses an identical API by defining them
(incorrectly) to inline assembler macro definitions in
sys/dev/pci/ixgbe/ixgbe_osdep.h
This will result in the dom0 builds failing to build due to this
redefinition of the macros. We therefore disable the driver in
NetBSD/amd64 dom0 in order to facilitate smoothly moving the XEN
kernel builds to the new XEN source level API (RELEASE-4.11.1).
The fix for this is trivial, but needs the attention of the driver
maintainer.
Release tag: RELEASE-4-11-1
git log of the freeze is as follows:
commit 96cbd0893f783997caaf117e897d5fa8f2dc7b5f
Author: Jan Beulich <jbeulich@suse.com>
Date: Thu Nov 29 15:04:11 2018 +0100
update Xen version to 4.11.1
- move -std=* handling, besides the list in CXX11_ALWAYS, to
libsupc++/Makefile.common
- include the arch defs.mk to obtain ${G_*_SOURCES} and use them
for -std= setting
- make sure VER_CPPFLAGS is applied to all required files
- add ADD_FRONTEND_LIBRARY to avoid linking libfrontend, while
using the rest of this fragment
* Uh I put the wrong masks in some GPRs, fuck.
* When the opsize of MOVZX is 4, we need to combine the zero-extend from
the instruction with the natural zero-extend of long mode.
Add two associated tests.
directly, use abstracted bits that are converted from/to PTE bits when
needed (in pmap_sync_pv).
This allows us to use the same pp_attrs for pmaps that have PTE bits at
different locations.
- Drop AXEN_RXCTL_ACPT_PHY_MCAST bit (neither Linux nor FreeBSD sets it).
- 0x0010 bit is not AXEN_RXCTL_ACPT_BCAST ("accept broadcast") but
AXEN_RXCTL_ACPT_MCAST ("accept multicast (hash-table-based)").
For consistency move prototype to the _mod.h header.
XXX: Why are the compat files here? Shouldn't they be in compat/common?
Or because this could be a separate module, they belong with it?
to build with GCC7:
revision 1.3
date: 2017-07-22 13:52:52 -0700; author: joerg; state: Exp; lines: +2 -1; commitid: gesFYL8PorhYCg0A;
One more missing check for DECL_INITIAL being non-NULL.
revision 1.2
date: 2017-07-17 12:53:10 -0700; author: joerg; state: Exp; lines: +2149 -1573; commitid: fxGaJg3EuIcnsCZz;
branches: 1.2.2;
A const declaration with explicit section attribute should create a
read-only section, whether it is initialized or not.
XXX: i may have merged them wrongly into gcc7, but AFAICT, they're
expecting to use named BSS sections, so this seems wrong now anyway.
joerg, please feel free to check :-)
mrg