[Note other build failures stopped builds before the below before
this was run into. Now those pass to reach the below.]
ci.free.bsd.org has FreeBSD-head-amd64-gcc failing for:
--- libpmc_json.o ---
In file included from /workspace/src/lib/libpmc/libpmc_json.cc:39:0:
On Fri, Jun 08, 2018 at 11:40:37AM -0400, Jonathan T. Looney wrote:
> ...
> If anyone is hitting this bug and needs to get a working system in the
> meantime, you'll need to revert the following commits which implemented (or
> updated) this change:
>
> r334830
> r334829
> r334824
>
> Jonathan
I
On Thu, Jun 7, 2018 at 11:26 PM, Greg wrote:
> On 06/07, Matthew Macy wrote:
>>
>> On Thu, Jun 7, 2018 at 10:33 Michael Butler
>> wrote:
>>
>>> Ah - I'll re-enable that to see if it makes a difference ..
>>>
>>
>>
>> It's not a question of enabling. It doesn't explicitly use the 11 symbols.
>>
weird, my grep-fu failed me hardcore i guess.
Will fix shortly.
On Fri, Jun 8, 2018 at 5:40 PM, Jonathan T. Looney wrote:
> On Fri, Jun 8, 2018 at 10:52 AM, Jonathan T. Looney
> wrote:
> >
> > On Fri, Jun 8, 2018 at 9:38 AM, David Wolfskill
> wrote:
> > >
> > > Sorry for lack of much
On Fri, Jun 8, 2018 at 10:52 AM, Jonathan T. Looney wrote:
>
> On Fri, Jun 8, 2018 at 9:38 AM, David Wolfskill
wrote:
> >
> > Sorry for lack of much analysis; am at BSDCan. jtl@ suggested that a
> > sequence of changes involving memory allocation and ipfw counters is
> > likely to be at issue.
On Fri, Jun 8, 2018 at 9:38 AM, David Wolfskill
wrote:
>
> Sorry for lack of much analysis; am at BSDCan. jtl@ suggested that a
> sequence of changes involving memory allocation and ipfw counters is
> likely to be at issue.
Just to be clear, I speculated that this seemed like it could be caused
On Fri, 8 Jun 2018 17:18:43 +0300
Andriy Gapon wrote:
> On 08/06/2018 15:27, Gary Jennejohn wrote:
> > On Thu, 7 Jun 2018 20:14:10 +0300
> > Andriy Gapon wrote:
> >
> >> On 03/05/2018 12:41, Andriy Gapon wrote:
> >>> I think that we need preemption policies that might not be expressible as
On 08/06/2018 15:27, Gary Jennejohn wrote:
> On Thu, 7 Jun 2018 20:14:10 +0300
> Andriy Gapon wrote:
>
>> On 03/05/2018 12:41, Andriy Gapon wrote:
>>> I think that we need preemption policies that might not be expressible as
>>> one or
>>> two numbers. A policy could be something like this:
Sorry for lack of much analysis; am at BSDCan. jtl@ suggested that a
sequence of changes involving memory allocation and ipfw counters is
likely to be at issue.
I tried grabbing some screen shots, the last of which has a backtrace
(that isn't cut off, as the middle one is); they are available at
On Thu, 7 Jun 2018 20:14:10 +0300
Andriy Gapon wrote:
> On 03/05/2018 12:41, Andriy Gapon wrote:
> > I think that we need preemption policies that might not be expressible as
> > one or
> > two numbers. A policy could be something like this:
> > - interrupt threads can preempt only threads
On Fri, 8 Jun 2018 02:51+0200, Mateusz Guzik wrote:
> Thanks for the report. Next time if you identify the culprit please cc:
> the committer - not everyone watches mailing lists too closely.
Wilco.
> I set it up on FreeBSD as dom0 and verified the problem exists.
> I fixed it with the
On 06/07, Matthew Macy wrote:
On Thu, Jun 7, 2018 at 10:33 Michael Butler
wrote:
Ah - I'll re-enable that to see if it makes a difference ..
It's not a question of enabling. It doesn't explicitly use the 11 symbols.
Rust developers assume that every OS has a frozen ABI like Linux. The
powerpc 64, powerpc, powerpcspe gets things like:
--- all_subdir_hwpmc ---
cc1: warnings being treated as errors
/usr/src/sys/dev/hwpmc/hwpmc_e500.c: In function 'e500_intr':
/usr/src/sys/dev/hwpmc/hwpmc_e500.c:611: warning: passing argument 3 of
'pmc_process_interrupt' from incompatible pointer
13 matches
Mail list logo
