> >> The real bug is the reverted varasm.c change. GCC creates the .eh_frame
> >> section with the wrong permissions.
> >
> >yes - putting your varasm.c back fixes the crtbegin.o
> >build, but it breaks the libstdc++ one:
> >
> >In file included from
> >/usr/src4/external/gpl3/gcc/dist/libstdc++-v3
"Andreas Gustafsson" writes:
> Module Name: src
> Committed By: gson
> Date: Wed Feb 13 07:55:33 UTC 2019
>
> Modified Files:
> src/distrib/pmax/ramdisk: Makefile
> src/sys/arch/pmax/conf: RAMDISK
>
> Log Message:
> Bump pmax install ramdisk size by another 100k, as 3500k is
On 2019/02/13 21:13, Christos Zoulas wrote:
In article ,
Rin Okuyama wrote:
Hi,
On 2019/02/13 6:07, Paul Goyette wrote:
On Tue, 12 Feb 2019, Rin Okuyama wrote:
Hi,
As Martin pointed out, it is useful for debugging to turn on
DIAGNOSTIC for modules (for non-release branches).
Now, all mod
In article ,
Rin Okuyama wrote:
>Hi,
>
>On 2019/02/13 6:07, Paul Goyette wrote:
>> On Tue, 12 Feb 2019, Rin Okuyama wrote:
>>
>>> Hi,
>>>
>>> As Martin pointed out, it is useful for debugging to turn on
>>> DIAGNOSTIC for modules (for non-release branches).
>>>
>>> Now, all modules for amd64 are
In article <20190213065626.ga22...@mail.duskware.de>,
Martin Husemann wrote:
>On Tue, Feb 12, 2019 at 09:20:23PM -, Christos Zoulas wrote:
>> Well, regardless of what the right permissions of .eh_frame are,
>> we could just nuke the code and default to the "new" behavior...
>> We can then put
On 2019/02/13 19:06, Paul Goyette wrote:
I would also wonder if we could increase the WARNS?= level from 3 to 5 (to
match the current WARNS?= level used for kernel builds). Has anyone tried to
see how many modules would fail with WARNS?=5 ??
Thank you for your comment.
Well, I examined tha
Le 13/02/2019 à 10:08, Cherry G.Mathew a écrit :
(resent to source-changes-d@)
"Maxime Villard" writes:
- There is no recursive slot possible, so we can't use pmap_map_ptes().
Rather, we walk down the EPT trees via the direct map, and that's
actually a lot simpler (and probably faste
I would also wonder if we could increase the WARNS?= level from 3 to 5 (to
match the current WARNS?= level used for kernel builds). Has anyone tried
to see how many modules would fail with WARNS?=5 ??
Thank you for your comment.
Well, I examined that (both for GCC7 & clang). Among ~ 360 modu
Hi,
On 2019/02/13 6:07, Paul Goyette wrote:
On Tue, 12 Feb 2019, Rin Okuyama wrote:
Hi,
As Martin pointed out, it is useful for debugging to turn on
DIAGNOSTIC for modules (for non-release branches).
Now, all modules for amd64 are successfully built with DIAGNOSTIC.
I'd like to commit the p
Hi,
On 2019/02/13 3:54, Nick Hudson wrote:
On 12/02/2019 16:02, Rin Okuyama wrote:
Hi,
The system freezes indefinitely with xhci(4) or ehci(4), when NIC with
multiple outstanding transfers [axen(4), mue(4), and ure(4)] is stopped
by "ifconfig down" or detached.
As discussed in the previous me
(resent to source-changes-d@)
"Maxime Villard" writes:
[...]
>
> Contrary to AMD-SVM, Intel-VMX uses a different set of PTE bits from
> native, and this has three important consequences:
>
> - We can't use the native PTE bits, so each time we want to modify the
>page tables, we need to kn
11 matches
Mail list logo
