Konstantin, *, good day.
I noticed that the current ioctl processing code for drm2 implicitely
assumes that the number of native ioctls is higher than that of 32-bit
compat ones, so it immediately gives EINVAL when
nr = dev-driver-max_ioctl. Seems that in future such assumption
may not be true
Do we need to compile all modules with witness definitions when
linking with a kernel compiled with witness?
This was true at one stage but I remember some work was done to make
them compatible.
___
freebsd-current@freebsd.org mailing list
On 11/28/14, 2:37 AM, Alfred Perlstein wrote:
On Nov 27, 2014, at 1:52 AM, Konstantin Belousov wrote:
On Wed, Nov 26, 2014 at 04:41:27PM -0800, Davide Italiano wrote:
On Mon, Aug 25, 2014 at 12:37 PM, John Baldwin j...@freebsd.org wrote:
On Wednesday, August 20, 2014 11:00:14 AM Davide
On Fri, Nov 28, 2014 at 04:29:42PM +0300, Eygene Ryabinkin wrote:
Konstantin, *, good day.
I noticed that the current ioctl processing code for drm2 implicitely
assumes that the number of native ioctls is higher than that of 32-bit
compat ones, so it immediately gives EINVAL when
nr =
In a thread on comp.lang.c, it was pointed out that softfloat
has a bug and in checking src/lib/libc/softfloat I confimed
the issue is present in FreeBSD. What I hae not confirmed
is whether or not it is possible to hit this bug. In fact,
it may only hit arm and mips. Anyway, here's the patch
On 28 November 2014 at 10:34, Steve Kargl
s...@troutmask.apl.washington.edu wrote:
In a thread on comp.lang.c, it was pointed out that softfloat
has a bug and in checking src/lib/libc/softfloat I confimed
the issue is present in FreeBSD. What I hae not confirmed
is whether or not it is
On Fri, Nov 28, 2014 at 10:54:25AM -0800, Adrian Chadd wrote:
On 28 November 2014 at 10:34, Steve Kargl
s...@troutmask.apl.washington.edu wrote:
In a thread on comp.lang.c, it was pointed out that softfloat
has a bug and in checking src/lib/libc/softfloat I confimed
the issue is present in
You can easily fire up a mips32 / mips64 emulator build - cross-build
a world+kernel, build an image, then run qemu-devel to boot it.
https://wiki.freebsd.org/FreeBSD/MipsEmulation
You should be able to get a 32 bit soft-float mips environment inside
there which you can use to trigger it.
(And
Hi,
We're working on updating llvm, clang and lldb to 3.5.0 in head. This
is quite a big update again, and any help with testing is appreciated.
To try this out, ensure you have good backups or snapshots, then build
world and kernel from the projects/clang350-import branch [1]. Please
use a
Something's wrong in base/head when /usr/sbin/cron and
/usr/sbin/fifolog_{create,reader,writer} winds up in ${DESTDIR}/
during installworld.
Seen on amd64 as of r275212, both with and without DESTDIR set.
Is it a pilot error on my part?
--
On Fri, Nov 28, 2014 at 10:54:07PM +0100, Trond Endrestøl wrote:
Something's wrong in base/head when /usr/sbin/cron and
/usr/sbin/fifolog_{create,reader,writer} winds up in ${DESTDIR}/
during installworld.
Seen on amd64 as of r275212, both with and without DESTDIR set.
Is it a pilot
On 28 Nov 2014, at 22:54, Trond Endrestøl trond.endres...@fagskolen.gjovik.no
wrote:
Something's wrong in base/head when /usr/sbin/cron and
/usr/sbin/fifolog_{create,reader,writer} winds up in ${DESTDIR}/
during installworld.
Seen on amd64 as of r275212, both with and without DESTDIR set.
On Fri, Nov 28, 2014 at 10:59:00PM +0100, Dimitry Andric wrote:
On 28 Nov 2014, at 22:54, Trond Endrestøl
trond.endres...@fagskolen.gjovik.no wrote:
Something's wrong in base/head when /usr/sbin/cron and
/usr/sbin/fifolog_{create,reader,writer} winds up in ${DESTDIR}/
during
13 matches
Mail list logo
