From owner-freebsd-ppc@freebsd.org Mon Dec 12 21:11:58 2016 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 165A6C739A2; Mon, 12 Dec 2016 21:11:58 +0000 (UTC) (envelope-from rdivacky@vlakno.cz) Received: from vlakno.cz (mail.vlakno.cz [91.217.96.224]) by mx1.freebsd.org (Postfix) with ESMTP id 9D4221F29; Mon, 12 Dec 2016 21:11:57 +0000 (UTC) (envelope-from rdivacky@vlakno.cz) Received: by vlakno.cz (Postfix, from userid 1002) id D58E5A35642; Mon, 12 Dec 2016 22:09:22 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=vlakno.cz; s=mail; t=1481576962; bh=lqiJ6kDxVcnWgjuN7nB/UaDHEnFcv7pF9TsEzWTth80=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=NWsuVjqS+44Kj9tJh0hVymqTXqSt7W3kNSQb76DizRemIlFo1ngAnRcyxN2zvvu1s 3c0VdhlCm/GF8PUdDww+ZMObqIJ1Xo3cdsGhaRFpDecjEZQY2+aJsAOkttBYoQ/srl eRB6h2a2MBlP2sJU5ggWM6883clAAaakieIjNc0M= Date: Mon, 12 Dec 2016 22:09:22 +0100 From: Roman Divacky To: Mark Millard Cc: FreeBSD Toolchain , Justin Hibbits , FreeBSD PowerPC ML , nwhitehorn@freebsd.org Subject: Re: clang 3.9.0 buildkernel on old powerpc64's vs. trying to build hwpmc_e500.o and the like. . . Message-ID: <20161212210922.GA27403@vlakno.cz> References: <20161205161904.GA7889@vlakno.cz> <126E2EDE-9499-4103-A3DB-CC517105DAB2@dsl-only.net> <20161207190057.GA58950@vlakno.cz> <20161208185541.GA33364@vlakno.cz> <20161208221452.GA42380@vlakno.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20161208221452.GA42380@vlakno.cz> User-Agent: Mutt/1.7.1 (2016-10-04) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Dec 2016 21:11:58 -0000 Ping.... Can you take a look Nathan? Thanks! Roman On Thu, Dec 08, 2016 at 11:14:52PM +0100, Roman Divacky wrote: > I believe the code comes from sys/powerpc/aim/locore64.S and if you compare > the different values from the disssembly with the .S code you can see > it's __tocbase and TOC_REF(). > > I wonder if the assembly has the -mminimal-toc knowledge hardcoded in somehow. > I am not sure what expectations the locore64.S has about the kernel layout that > we're probably breaking. > > I've CCed Nathan Whitehorn. Nathan, can you take a look please? > > Thanks, Roman > > On Thu, Dec 08, 2016 at 02:03:58PM -0800, Mark Millard wrote: > > [I have dropped the patch related information and just have > > failing-boot related information here.] > > > > On 2016-Dec-8, at 10:55 AM, Roman Divacky wrote: > > > > > Can you try to investigate why it dies? I am not convinced -mminimal-toc > > > would result in a boot failure. I think the kernel would fail to link. > > > > I give information for both devel/powerpc64-binutils based > > and for WITH_BINUTILS_BOOTSTRAP= based. They are different. > > > > For using 2.25.1 of devel/powerpc64-binutils (a cross build): > > (from camera image of screen) > > > > . . . (omitted material) . . . > > Type '?' for a list of commands, 'help' for more detailed help. > > OK unload > > OK boot ker390 > > /boot/ker390/kernel data=0xf851a8+0x42dd98 syms=[0x8+0xd6848+0x8+0xf1137] > > /boot/entropy size=0x1000 > > Booting. . . > > Kernel entry at 0x100160 > > > > Invalid memory access at %SSR0: 00000000.001001b0 %SRR1:90000000.00003030 > > > > Apple PowerMac11,2 5.2.7f1 BootROM builtin on 09/30/005 at 15:31:03 > > . . . (omitted material) . . . > > ok > > 0 > > > > > The only options at this point are: > > > > mac-boot > > shut-down > > > > > > From objdump for the above failing boot > > but with notes added: > > (Note: booting xtoolchain kernel starts at > > 0000000000100120 instead; relative > > offsets are unchanged and the code > > is mostly the same.) > > > > Disassembly of section .text: > > 0000000000100160 <.__start> mfmsr r20 > > 0000000000100164 <.__start+0x4> li r21,1 > > 0000000000100168 <.__start+0x8> rldimi r20,r21,63,0 > > 000000000010016c <.__start+0xc> mtmsrd r20 > > 0000000000100170 <.__start+0x10> isync > > 0000000000100174 <.__start+0x14> nop > > 0000000000100178 <.__start+0x18> b 0000000000100180 <.__start+0x20> > > 000000000010017c <.__start+0x1c> nop > > 0000000000100180 <.__start+0x20> nop > > 0000000000100184 <.__start+0x24> bl 0000000000100190 <.__start+0x30> > > 0000000000100188 <.__start+0x28> .long 0x0 > > 000000000010018c <.__start+0x2c> .long 0xf8ce78 > > booting xtoolchain based kernel has: 0xfebeb8 above <<<=== note > > 0000000000100190 <.__start+0x30> mflr r2 > > 0000000000100194 <.__start+0x34> ld r1,0(r2) > > 0000000000100198 <.__start+0x38> add r2,r1,r2 > > 000000000010019c <.__start+0x3c> ld r31,-32768(r2) > > 00000000001001a0 <.__start+0x40> subf r31,r31,r2 > > 00000000001001a4 <.__start+0x44> ld r1,0(r2) <<<=== !!!!! > > booting xtoolchain based kernel has: r1,-32760(r2) above <<<=== !!!!! > > 00000000001001a8 <.__start+0x48> addi r1,r1,16288 > > 00000000001001ac <.__start+0x4c> add r1,r1,r31 > > 00000000001001b0 <.__start+0x50> std r3,48(r1) > > SRR0 points at the above instruction > > (I stopped comparing to the booting xtoolchain > > based code after this.) > > 00000000001001b4 <.__start+0x54> std r4,56(r1) > > 00000000001001b8 <.__start+0x58> std r5,64(r1) > > 00000000001001bc <.__start+0x5c> std r6,72(r1) > > 00000000001001c0 <.__start+0x60> bl 00000000001001cc <.__start+0x6c> > > 00000000001001c4 <.__start+0x64> .long 0x0 > > 00000000001001c8 <.__start+0x68> .long 0xf84ed4 > > 00000000001001cc <.__start+0x6c> mflr r3 > > 00000000001001d0 <.__start+0x70> ld r4,0(r3) > > 00000000001001d4 <.__start+0x74> add r3,r4,r3 > > 00000000001001d8 <.__start+0x78> mr r4,r31 > > 00000000001001dc <.__start+0x7c> bl 0000000000b18ebc <.elf_reloc_self> > > 00000000001001e0 <.__start+0x80> nop > > 00000000001001e4 <.__start+0x84> ld r3,48(r1) > > 00000000001001e8 <.__start+0x88> ld r4,56(r1) > > 00000000001001ec <.__start+0x8c> ld r5,64(r1) > > 00000000001001f0 <.__start+0x90> ld r6,72(r1) > > 00000000001001f4 <.__start+0x94> mr r4,r2 > > 00000000001001f8 <.__start+0x98> bl 0000000000b1e980 <.powerpc_init> > > 00000000001001fc <.__start+0x9c> nop > > 0000000000100200 <.__start+0xa0> mr r1,r3 > > 0000000000100204 <.__start+0xa4> li r3,0 > > 0000000000100208 <.__start+0xa8> std r3,0(r1) > > 000000000010020c <.__start+0xac> bl 00000000005c4af8 <.mi_startup> > > 0000000000100210 <.__start+0xb0> nop > > 0000000000100214 <.__start+0xb4> b 0000000000100214 <.__start+0xb4> > > > > > > > > For using WITH_BINUTILS_BOOTSTRAP= based binutils (a cross build): > > (completes for buildkernel; fails for buildworld) > > > > . . . (omitted material) . . . > > Type '?' for a list of commands, 'help' for more detailed help. > > OK unload > > OK boot ker39a > > /boot/ker39a/kernel data=0xfd6318+0x42dda8 syms=[0x8+0xd6860+0x8+0xf1193] > > /boot/entropy size=0x1000 > > Booting. . . > > Kernel entry at 0x100160 > > > > Invalid memory access at %SSR0: 00000000.00000000 %SRR1:10000000.00081000 > > > > Apple PowerMac11,2 5.2.7f1 BootROM builtin on 09/30/005 at 15:31:03 > > . . . (omitted material) . . . > > ok > > 0 > > > > > The only options at this point are: > > > > mac-boot > > shut-down > > > > The problem here is a different code order and a matching > > wrong start address that does not track the difference. > > (From objdump.) Note: the same 0(r2) vs. -32760(r2) oddity > > exists in the start routine as well. > > > > Disassembly of section .text: > > 0000000000100160 <.__start-0x2030> std r2,40(r1) > > 0000000000100164 <.__start-0x202c> addis r2,r2,1 > > 0000000000100168 <.__start-0x2028> addi r2,r2,-8 > > 000000000010016c <.__start-0x2024> b 0000000000b2c8e0 <.cpu_switch> > > 0000000000100170 <.__start-0x2020> std r2,40(r1) > > 0000000000100174 <.__start-0x201c> addis r2,r2,1 > > 0000000000100178 <.__start-0x2018> addi r2,r2,-8 > > 000000000010017c <.__start-0x2014> b 0000000000ade6c8 <.sf_buf_alloc> > > 0000000000100180 <.__start-0x2010> std r2,40(r1) > > 0000000000100184 <.__start-0x200c> addis r2,r2,1 > > 0000000000100188 <.__start-0x2008> addi r2,r2,-8 > > 000000000010018c <.__start-0x2004> b 0000000000a83f78 <.vm_fault_hold> > > 0000000000100190 <.__start-0x2000> std r2,40(r1) > > 0000000000100194 <.__start-0x1ffc> addis r2,r2,1 > > 0000000000100198 <.__start-0x1ff8> addi r2,r2,-8 > > 000000000010019c <.__start-0x1ff4> b 0000000000b1f1e8 <.fill_regs32> > > 00000000001001a0 <.__start-0x1ff0> std r2,40(r1) > > 00000000001001a4 <.__start-0x1fec> addis r2,r2,1 > > 00000000001001a8 <.__start-0x1fe8> addi r2,r2,-8 > > 00000000001001ac <.__start-0x1fe4> b 0000000000b1a7e4 <.casueword32> > > 00000000001001b0 <.__start-0x1fe0> std r2,40(r1) > > 00000000001001b4 <.__start-0x1fdc> addis r2,r2,1 > > 00000000001001b8 <.__start-0x1fd8> addi r2,r2,-8 > > 00000000001001bc <.__start-0x1fd4> b 0000000000a8fa30 <.kmap_free_wakeup> > > . . . > > 0000000000102190 <.__start> mfmsr r20 > > 0000000000102194 <.__start+0x4> li r21,1 > > 0000000000102198 <.__start+0x8> rldimi r20,r21,63,0 > > 000000000010219c <.__start+0xc> mtmsrd r20 > > 00000000001021a0 <.__start+0x10> isync > > 00000000001021a4 <.__start+0x14> nop > > 00000000001021a8 <.__start+0x18> b 00000000001021b0 <.__start+0x20> > > 00000000001021ac <.__start+0x1c> nop > > 00000000001021b0 <.__start+0x20> nop > > 00000000001021b4 <.__start+0x24> bl 00000000001021c0 <.__start+0x30> > > 00000000001021b8 <.__start+0x28> .long 0x0 > > 00000000001021bc <.__start+0x2c> .long 0xfc8e48 > > 00000000001021c0 <.__start+0x30> mflr r2 > > 00000000001021c4 <.__start+0x34> ld r1,0(r2) > > 00000000001021c8 <.__start+0x38> add r2,r1,r2 > > 00000000001021cc <.__start+0x3c> ld r31,-32768(r2) > > 00000000001021d0 <.__start+0x40> subf r31,r31,r2 > > 00000000001021d4 <.__start+0x44> ld r1,0(r2) <<< same 0 vs. -32760 oddity!!! > > 00000000001021d8 <.__start+0x48> addi r1,r1,16288 > > 00000000001021dc <.__start+0x4c> add r1,r1,r31 > > 00000000001021e0 <.__start+0x50> std r3,48(r1) > > 00000000001021e4 <.__start+0x54> std r4,56(r1) > > 00000000001021e8 <.__start+0x58> std r5,64(r1) > > 00000000001021ec <.__start+0x5c> std r6,72(r1) > > 00000000001021f0 <.__start+0x60> bl 00000000001021fc <.__start+0x6c> > > 00000000001021f4 <.__start+0x64> .long 0x0 > > 00000000001021f8 <.__start+0x68> .long 0xfd4014 > > 00000000001021fc <.__start+0x6c> mflr r3 > > 0000000000102200 <.__start+0x70> ld r4,0(r3) > > 0000000000102204 <.__start+0x74> add r3,r4,r3 > > 0000000000102208 <.__start+0x78> mr r4,r31 > > 000000000010220c <.__start+0x7c> bl 0000000000101a20 > > 0000000000102210 <.__start+0x80> ld r2,40(r1) > > 0000000000102214 <.__start+0x84> ld r3,48(r1) > > 0000000000102218 <.__start+0x88> ld r4,56(r1) > > 000000000010221c <.__start+0x8c> ld r5,64(r1) > > 0000000000102220 <.__start+0x90> ld r6,72(r1) > > 0000000000102224 <.__start+0x94> mr r4,r2 > > 0000000000102228 <.__start+0x98> bl 00000000001019a0 > > 000000000010222c <.__start+0x9c> ld r2,40(r1) > > 0000000000102230 <.__start+0xa0> mr r1,r3 > > 0000000000102234 <.__start+0xa4> li r3,0 > > 0000000000102238 <.__start+0xa8> std r3,0(r1) > > 000000000010223c <.__start+0xac> bl 00000000005c6b28 <.mi_startup> > > 0000000000102240 <.__start+0xb0> nop > > 0000000000102244 <.__start+0xb4> b 0000000000102244 <.__start+0xb4> > > > > > > Who is most appropriate to send such information to for powerpc64? > > > > === > > Mark Millard > > markmi at dsl-only.net From owner-freebsd-ppc@freebsd.org Tue Dec 13 20:40:06 2016 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 362A1C758A6 for ; Tue, 13 Dec 2016 20:40:06 +0000 (UTC) (envelope-from bounce@e.bananabed.com.au) Received: from mx9.bananabed.com.au (mx9.bananabed.com.au [178.32.153.32]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CCEDF643 for ; Tue, 13 Dec 2016 20:40:05 +0000 (UTC) (envelope-from bounce@e.bananabed.com.au) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; s=1481058667.bananabed; d=e.bananabed.com.au; h=To:Subject:Message-ID:Date:From:Reply-To:MIME-Version:List-Unsubscribe:Content-Type:Content-Transfer-Encoding; i=info@e.bananabed.com.au; bh=dqC8ibMdH5fw0aX4y8pXEVVPsf0=; b=QzkuhIoVjZ8oTVpbhjR09qxmE+bMREZUkAPaKxoWHKOzkjznJPCa5JpnbtKgspOuc7TbdXz2TT9q 17c9hn149/mtRULQ6v60HSDCdSr0Vx/zpoha1DjKhG+dQM8XHHD3+OmfygBEzLwwsiOL8f+2hT+O PXFfn1z9Vg+gAZq1haM= DomainKey-Signature: a=rsa-sha1; c=nofws; q=dns; s=1481058667.bananabed; d=e.bananabed.com.au; b=SoNPqGj2GbIwNQ9CSPB/HAVkaM+ZZ/uYPHq/1fPJlgRlx9gCFhS5sl1NpfwrYv3GKFi6aY5Wojbu FW/g5xghznNgt+tbz88DhrHDQnZLKO6OAhENgrbAY/9noWyW5SaOX2mQvG0leYE4KzRppckklQp/ jHWp3q6koOpv2m8m1rc=; To: freebsd-ppc@freebsd.org Subject: The EASIEST CHRISTMAS present for everyone.. Message-ID: <42d8cf0d59537430b7aeb414da865a51@e.bananabed.com.au> Date: Tue, 13 Dec 2016 20:40:04 +0000 From: "Banana Bed" Reply-To: info@e.bananabed.com.au MIME-Version: 1.0 X-Mailer-LID: 2 X-Mailer-RecptId: 167265 X-Mailer-SID: 9 X-Mailer-Sent-By: 1 Content-Type: text/plain; format=flowed; charset="UTF-8" Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Dec 2016 20:40:06 -0000 Your email client cannot read this email. To view it online, please go here: http://e.bananabed.com.au/mail/display.php?M=167265&C=1185400d3305f5fb1c87fcfba32f8b80&S=9&L=2&N=2 To stop receiving these emails:http://e.bananabed.com.au/mail/unsubscribe.php?M=167265&C=1185400d3305f5fb1c87fcfba32f8b80&L=2&N=9 From owner-freebsd-ppc@freebsd.org Wed Dec 14 04:41:45 2016 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E1334C760E2 for ; Wed, 14 Dec 2016 04:41:45 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-211-167.reflexion.net [208.70.211.167]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 96455136B for ; Wed, 14 Dec 2016 04:41:44 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 23798 invoked from network); 14 Dec 2016 04:42:34 -0000 Received: from unknown (HELO mail-cs-02.app.dca.reflexion.local) (10.81.19.2) by 0 (rfx-qmail) with SMTP; 14 Dec 2016 04:42:34 -0000 Received: by mail-cs-02.app.dca.reflexion.local (Reflexion email security v8.20.0) with SMTP; Tue, 13 Dec 2016 23:41:46 -0500 (EST) Received: (qmail 18218 invoked from network); 14 Dec 2016 04:41:46 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 14 Dec 2016 04:41:46 -0000 Received: from [192.168.1.118] (c-67-170-167-181.hsd1.or.comcast.net [67.170.167.181]) by iron2.pdx.net (Postfix) with ESMTPSA id 12E45EC9059; Tue, 13 Dec 2016 20:41:37 -0800 (PST) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.1 \(3251\)) Subject: sys/powerpc/powerpc/trap.c has messed up masking operation?: use of || for bit field masling Message-Id: <0661C9A5-5D4C-4F00-9B0C-F80688BED8A4@dsl-only.net> Date: Tue, 13 Dec 2016 20:41:36 -0800 Cc: FreeBSD PowerPC ML To: Justin Hibbits , Nathan Whitehorn X-Mailer: Apple Mail (2.3251) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Dec 2016 04:41:46 -0000 clang 3.9.0 is complaining about: --- trap.o --- /usr/src/sys/powerpc/powerpc/trap.c:283:42: warning: use of logical '||' = with constant operand [-Wconstant-logical-operand] frame->cpu.booke.dbcr0 &=3D ~(DBCR0_IDM || = DBCR0_IC); ^ = ~~~~~~~~ /usr/src/sys/powerpc/powerpc/trap.c:283:42: note: use '|' for a bitwise = operation frame->cpu.booke.dbcr0 &=3D ~(DBCR0_IDM || = DBCR0_IC); ^~ | Looking around: # grep DBCR0_ /usr/src/sys/powerpc/include/spr.h . . . #define DBCR0_IDM 0x40000000 /* Internal Debug Mode */ . . . #define DBCR0_IC 0x08000000 /* Instruction Completion = debug event */ . . . || use seems unlikely to be correct for the context. There is also this that I happened to notice = sys/powerpc/powerpc/intr_machdep.c : --- intr_machdep.o --- /usr/src/sys/powerpc/powerpc/intr_machdep.c:454:15: warning: comparison = of constant -1 with expression of type 'enum intr_trigger' is always = false [-Wtautological-constant-out-of-range-compare] if (i->trig =3D=3D -1) ~~~~~~~ ^ ~~ /usr/src/sys/powerpc/powerpc/intr_machdep.c:500:16: warning: comparison = of constant -1 with expression of type 'enum intr_trigger' is always = false [-Wtautological-constant-out-of-range-compare] if (i->trig =3D=3D -1) ~~~~~~~ ^ ~~ There are other comparisons around with a constant=20 result at compile time. But they tend to be in less central areas like zfs. Similarly for some other types of compiler reports. =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-ppc@freebsd.org Wed Dec 14 18:28:44 2016 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3934AC76722 for ; Wed, 14 Dec 2016 18:28:44 +0000 (UTC) (envelope-from gabriel.diaz@vgtelecomreports.com) Received: from smtp.vgtelecomreports.com (smtp.vgtelecomreports.com [202.0.103.20]) by mx1.freebsd.org (Postfix) with ESMTP id 244EF75D for ; Wed, 14 Dec 2016 18:28:39 +0000 (UTC) (envelope-from gabriel.diaz@vgtelecomreports.com) X-SmarterMail-Authenticated-As: admin@vgtelecomreports.com DomainKey-Signature: a=rsa-sha1; c=nofws; q=dns; d=vgtelecomreports.com; s=smtp; h=received:from:to:message-id:subject:date:mime-version:reply-to :content-type; b=a8nz3z5Qzarz1T72VRA3b7cfwVN4D1OOy9PB84XCGb9bUE0ljG2nLsx+7qWV7Sh99 XMxN0cAxeKPpGGfnKkF4GijD2QRFuOE/O2AVP+19do1ZgnyC7tO0CmQ4Vng9D2Vrn eConTortxvQ9Oa10or7mqkI5SAdJtAQ48vQpU5rIU= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=vgtelecomreports.com; s=smtp; h= content-type:reply-to:mime-version:date:subject:message-id:to:from; bh=C9VckiJDUSmw5Hbkrx0MsHQHTnHDCxr/UV+7XuHdzdU=; b=Z9jLx0H0EbKXP49llIJ3nxZSVFAB2oD7yu55XNkpSs/MFpzyTRVkGq9QqMhgkEEcf VUbEyDb1ITGS2Ckp4vSN5v0nSjoN6ax3e+kUBspxNo3664MqsPT0wgynQSAFFNeF5 2pxJ9cdXGqZNOkj5AdFKvyqkuheyJ6eTcTvWP9x9I= Received: from WIN-ASQ29B6R1EP (WIN-ASQ29B6R1EP [202.0.103.127]) by smtp.vgtelecomreports.com with SMTP; Wed, 14 Dec 2016 18:09:47 +0000 From: Gabriel Diaz To: freebsd-ppc@freebsd.org Message-Id: <20161214180947.51454887@vgtelecomreports.com> Subject: Intelligent Virtual Assistant (IVA) Market Report 2017-2027 Date: Wed, 14 Dec 2016 18:09:47 +0000 MIME-Version: 1.0 Reply-To: gabriel.diaz@vgtelecomreports.com Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Dec 2016 18:28:44 -0000 Visiongain - Business Report Updates Speak to our consultant now: +44 (0)20 7549 9933 Intelligent Virtual Assistant (IVA) Market Report 2017-2027 Forecasts By Technology (Text to Speech, Speech Recognition) By Application (Websites, Contact Centre, Messenger Bots) By End User (Individual User, Small & Medium Enterprise, Large Enterprise) Analysis of Leading Companies Developing Artificial intelligence (AI), Predictive Analytics & Natural Language Understanding The global Intelligent Virtual Assistant market will reach $1,138.8m in 2017. An Intelligent virtual assistant acts as a primary interface between digital data and customers. Today, most of the websites place a burden on end users to find answers to their queries. If end users are not able to find relevant information, they usually abandon the search and contact live customer service representatives. Companies need a cost effective way to effectively and efficiently respond to customer needs. Hence, most companies are turning to interactive online channels such as intelligent virtual assistants to solve this challenge. How This 115 Page Report Delivers: • 53 tables, charts and graphs that add visual analysis in order to explain developing trends within the Intelligent Virtual Assistant market. • forecasts for the period 2017-2027 for the leading Intelligent Virtual Assistant submarkets: - by technology (Text to Speech, Speech Recognition), - by Applications (Websites, Contact Centre, Messenger Bots) and - by End User (Individual User, Small & Medium Enterprise, Large Enterprise) • Forecasts and analysis for 5 regions and 15 leading national Intelligent Virtual Assistant markets. • Profiles of 9 companies including Anboto Group, Artificial Solutions Ltd., CodeBaby Corporation, Creative Virtual Ltd, eGain Communications Corporation, IntelliResponse Systems Inc, Next IT Corporation, Nuance Communications Inc and Speaktoit, Inc. Buy this report How to purchase our reports Select the license from the list below and send your details Licensing options: Single User GBP 1999 Dept. (5 Users) GBP 2999 Site GBP 4999 Global GBP 6999 For more information and orders please contact gabriel.diaz@vgtelecomreports.com Table of Contents - Intelligent Virtual Assistant (IVA) Market Report 2017-2027 1. Report Overview 2. Executive Summary 2.1 Market Snapshot: Global Intelligent Virtual Assistant Market (2016 and 2027) 2.2 Global Intelligent Virtual Assistant Market, 2015 – 2027, Revenue (US$ Mn) and Y-o-Y Growth (%). 2.3 Global Intelligent Virtual Assistant Market, by Technology, 2016 (US$ Mn) 2.4 Global Intelligent Virtual Assistant Market, by Application, 2016 (US$ Mn) 2.5 Global Intelligent Virtual Assistant Market, by End-user, 2016 (US$ Mn 2.6 Global Intelligent Virtual Assistant Market, by Geography, 2016 (US$ Mn) 3. Global Intelligent Virtual Assistant Market Overview. 3.1 Introduction. 3.2 Key Trends Analysis 3.3 Contribution and Market Potential of Jibo, Siri, Cortana, Google Now and Alexa Voice 3.4 Market Drivers 3.4.1 Drivers 3.4.1.1 Increasing Data Explosion Creating Demand for Intelligent Virtual Assistant Software 3.4.1.2. Increasing Focus on Improving Customer Relationship 3.4.1.3 Innovation in Speech Recognition Technology 3.4.2 Restraints 3.4.2.1 Cost and Complexity of Software and Lack of Skilled Resource 3.4.3. Opportunities 3.4.3.1 Expanding Application Areas Offer Potential Growth Opportunities to the Market 3.4.3.2 New Commerce Platform, Replacing Search Engines 3.5 Distribution Channel Analysis 3.6 Global Intelligent Virtual Assistant Market Analysis, By Technology 3.6.1 Overview: 3.6.1.1 Global Intelligent Virtual Assistant Market, by Technology – Market Share and Forecast, 2016 Vs 2027 (Value %) 3.6.2 Text-to-speech 3.6.2.1 Global Intelligent Virtual Assistant Market Revenue Growth for Text-to-Speech, 2015 - 2027 (US$ Mn 3.6.3 Speech Recognition 3.6.3.1 Global Intelligent Virtual Assistant Market Revenue Growth for Speech Recognition, 2015 - 2027 (US$ Mn) . 3.7 Global Intelligent Virtual Assistant Market Analysis, by End-user 3.7.1 Overview 3.7.1.1 Global Intelligent Virtual Assistant Market, by End-user – Market Share and Forecast, 2016 Vs 2027 (Value %) 3.7.2 Individual Users 3.7.2.1 Global Intelligent Virtual Assistant Market Revenue Growth for Individual Users, 2015 - 2027 (US$ Mn) 3.7.3 Small and Medium Enterprise 3.7.3.1 Global Intelligent Virtual Assistant Market Revenue Growth for Small and Medium Enterprise, 2015 - 2027 (US$ Mn 3.7.4 Large Enterprise 3.7.4.1 Global Intelligent Virtual Assistant Market Revenue Growth for Large Enterprise, 2015 - 2027 (US$ Mn) 3.8 Global Intelligent Virtual Assistant Market Analysis, by Application 3.8.1 Overview 3.8.1.1 Global Intelligent Virtual Assistant Market, by Application – Market Share and Forecast, 2016 Vs 2027 (Value %). 3.8.2 Websites 3.8.2.1 Global Intelligent Virtual Assistant Market Revenue Growth for Websites, 2015 - 2027 (US$ Mn) 3.8.3 Contact Centres 3.8.3.1 Global Intelligent Virtual Assistant Market Revenue Growth for Contact Centres, 2015 - 2027 (US$ Mn) 3.8.4 Messenger Bots 3.8.4.1 Global Intelligent Virtual Assistant Market Revenue Growth for Messenger Bots, 2015 - 2027 (US$ Mn) 3.9 Competitive Landscape 3.9.1 Market Positioning of Key Players, 2015 3.9.1.1 Global Intelligent Virtual Assistant Market Positioning Analysis, 2016 3.9.2 Competitive Strategies Adopted by Leading Players 3.9.2.1 Focus on Development of Intelligent Virtual Assistance for a Wide Range of Applications . . . . 3.9.2.2 Strategic Partnership and Acquisitions. 3.9.3 Recommendations 4. North America Intelligent Virtual Assistant Market Analysis 4.1 Overview 4.2 Global Intelligent Virtual Assistant Market Share by Geography, 2016 and 2027 (%). 4.2.1 North America Intelligent Virtual Assistant Market Revenue and Y-o-Y Growth, 2015 – 2027 (US$ Mn 4.3 Key Trend Analysis 4.3.1 Market Snapshot: North America Intelligent Virtual Assistant Market (2016 and 2027) 4.4 North America Intelligent Virtual Assistant Market Analysis, By Technology, 2015 – 2027 4.4.1 Overview 4.4.2 North America Intelligent Virtual Assistant Market Revenue and Forecast, By Technology, 2015 – 2027 (US$ Mn) 4.5 North America Intelligent Virtual Assistant Market Analysis, By Application, 2015 – 2027 4.5.1 Overview. 4.5.2 North America Intelligent Virtual Assistant Market Revenue and Forecast, By Application, 2015 – 2027 (US$ Mn) 4.6 North America Intelligent Virtual Assistant Market Analysis, By End-user, 2015 – 2027 4.6.1 Overview 4.6.2 North America Intelligent Virtual Assistant Market Revenue and Forecast, By End-user, 2015 – 2027 (US$ Mn) 4.7 North America Intelligent Virtual Assistant Market Analysis, By Geography, 2015 – 2027 4.7.1 Overview 4.7.2 North America Intelligent Virtual Assistant Market Revenue and Forecast, By Geography, 2015 – 2027 (US$ Mn) 5. Europe Intelligent Virtual Assistant Market Analysis 5.1 Overview. 5.2 Europe Intelligent Virtual Assistant Market Revenue and Y-o-Y Growth, 2015 – 2027 (US$ Mn) 5.3 Key Trends Analysis 5.4 Market Snapshot: Europe Intelligent Virtual Assistant Market (2016 and 2027) 5.5 Europe Intelligent Virtual Assistant Market Analysis, By Technology, 2015 – 2027 5.5.1 Overview. 5.5.2 Europe Intelligent Virtual Assistant Market Revenue and Forecast, By Technology, 2015 – 2027 (US$ Mn) 5.6 Europe Intelligent Virtual Assistant Market Analysis, By Application, 2015 – 2027 5.6.1 Overview 5.6.2 Europe Intelligent Virtual Assistant Market Revenue and Forecast, By Application, 2015 – 2027 (US$ Mn) 5.7 Europe Intelligent Virtual Assistant Market Analysis, By End-user, 2015 – 2027 5.7.1 Overview 5.7.2 Europe Intelligent Virtual Assistant Market Revenue and Forecast, By End-user, 2015 – 2027 (US$ Mn 5.8 Europe Intelligent Virtual Assistant Market Analysis, By Geography, 2015 – 2027 5.8.1 Overview 5.8.2 Europe Intelligent Virtual Assistant Market Revenue and Forecast, By Geography, 2015 – 2027 (US$ Mn) 6. Asia Pacific Intelligent Virtual Assistant Market Analysis 6.1 Overview 6.2 Asia Pacific Intelligent Virtual Assistant Market Revenue and Y-o-Y Growth, 2015 – 2027 (US$ Mn) 6.3 Key Trends Analysis 6.4 Market Snapshot: Asia Pacific Intelligent Virtual Assistant Market (2016 and 2027) 6.5 Asia Pacific Intelligent Virtual Assistant Market Analysis, By Technology, 2015 – 2027 6.5.1 Overview 6.5.2 Asia Pacific Intelligent Virtual Assistant Market Revenue and Forecast, By Technology, 2015 – 2027 (US$ Mn) 6.6 Asia Pacific Intelligent Virtual Assistant Market Analysis, By Application, 2015 – 2027 6.6.1 Overview. 6.6.2 Asia Pacific Intelligent Virtual Assistant Market Revenue and Forecast, By Application, 2015 – 2027 (US$ Mn 6.7 Asia Pacific Intelligent Virtual Assistant Market Analysis, By End-user, 2015 – 2027 6.7.1 Overview. 6.7.2 Asia Pacific Intelligent Virtual Assistant Market Revenue and Forecast, By End-user, 2015 – 2027 (US$ Mn) 6.8 Asia Pacific Intelligent Virtual Assistant Market Analysis, By Geography, 2015 – 2027. 6.8.1 Overview 6.8.2 Asia Pacific Intelligent Virtual Assistant Market Revenue and Forecast, By Geography, 2015 – 2027 (US$ Mn) 7. Middle East and Africa Intelligent Virtual Assistant Market Analysis. 7.1 Overview 7.2 Middle East and Africa Intelligent Virtual Assistant Market Revenue and Y-o-Y Growth, 2015 – 2027 (US$ Mn 7.3 Key Trends Analysis 7.4 Market Snapshot: Middle East and Africa Intelligent Virtual Assistant Market (2016 and 2027) 7.5 Middle East and Africa Intelligent Virtual Assistant Market Analysis, By Technology, 2015 – 2027. 7.5.1 Overview 7.5.2 Middle East and Africa Intelligent Virtual Assistant Market Revenue and Forecast, By Technology, 2015 – 2027 (US$ Mn) 7.6 Middle East and Africa Intelligent Virtual Assistant Market Analysis, By Application, 2015 – 2027 7.6.1 Overview. 7.6.2 Middle East and Africa Intelligent Virtual Assistant Market Revenue and Forecast, By Application, 2015 – 2027 (US$ Mn) 7.7 Middle East and Africa Intelligent Virtual Assistant Market Analysis, By End-user, 2015 – 2027 7.7.1 Overview 7.7.2 Middle East and Africa Intelligent Virtual Assistant Market Revenue and Forecast, By End-user, 2015 – 2027 (US$ Mn) 7.8 Middle East and Africa Intelligent Virtual Assistant Market Analysis, By Geography, 2015 – 2027 7.8.1 Overview 7.8.2 Middle East and Africa Intelligent Virtual Assistant Market Revenue and Forecast, By Geography, 2015 – 2027 (US$ Mn 8. Latin America Intelligent Virtual Assistant Market Analysis 8.1 Overview 8.2 Latin America Intelligent Virtual Assistant Market Revenue and Y-o-Y Growth, 2015 – 2027 (US$ Mn) 8.3 Key Trends Analysis 8.4 Market Snapshot: Latin America Intelligent Virtual Assistant Market (2016 and 2027) 8.5 Latin America Intelligent Virtual Assistant Market Analysis, By Technology, 2015 – 2027 8.5.1.Overview 8.5.2 Latin America Intelligent Virtual Assistant Market Revenue and Forecast, By Technology, 2015 – 2027 (US$ Mn) 8.6 Latin America Intelligent Virtual Assistant Market Analysis, By Application, 2015 – 2027 8.6.1 Overview 8.6.2 Latin America Intelligent Virtual Assistants Market Revenue and Forecast, By Application, 2015 – 2027 (US$ Mn) 8.7 Latin America Intelligent Virtual Assistant Market Analysis, By End-user, 2015 – 2027 8.7.1 Overview 8.7.2 Latin America Intelligent Virtual Assistant Market Revenue and Forecast, By End-user, 2015 – 2027 (US$ Mn) 8.8 Latin America Intelligent Virtual Assistant Market Analysis, By Geography, 2015 – 2027 8.8.1 Overview. 8.8.2 Latin America Intelligent Virtual Assistant Market Revenue and Forecast, By Geography, 2015 – 2027 (US$ Mn) 9.. Leading Companies Providing Intelligent Virtual Assistants 9.1 Next IT Corporation 9.1.1 Next IT Corporation Geographical Presence: 9.1.2 Next IT Corporation IVA Technologies 9.1.3 Next IT Corporation Overview: 9.1.4 Next IT Corporation Financial Analysis: 9.1.5 Next IT Corporation Recent Developments 9.1.6 Next IT Corporation Historic Roadmap 9.1.7 Next IT Corporation Strategy 9.2 Creative Virtual Ltd 9.2.1 Creative Virtual Ltd Geographical Presence: 9.2.2 Creative Virtual Ltd IVA Technologies 9.2.3 Creative Virtual Ltd Overview: 9.2.4 Creative Virtual Ltd Financial Analysis: 9.2.5 Creative Virtual Ltd Recent Developments: 9.2.6 Creative Virtual Ltd Historic Roadmap: 9.2.7 Creative Virtual Ltd Strategy: 9.3 CodeBaby Corporation 9.3.1 CodeBaby Corporation Geographical Presence 9.3.2 CodeBaby Corporation IVA Technologies 9.3.3 CodeBaby Corporation Overview: 9.3.4 CodeBaby Corporation Financial Analysis 9.3.5 CodeBaby Corporation Recent Developments 9.3.6 CodeBaby Corporation Historic Roadmap 9.3.7 CodeBaby Corporation Strategy 9.4 IntelliResponse Systems Inc 9.4.1 IntelliResponse Systems Inc Geographical Presence 9.4.2 IntelliResponse Systems Inc IVA Technologies 9.4.3 IntelliResponse Systems Inc Overview: 9.4.4 IntelliResponse Systems Inc Financial Analysis 9.4.5 IntelliResponse Systems Inc Recent Developments: 9.4.6 IntelliResponse Systems Inc Historic Roadmap: 9.4.7 IntelliResponse Systems Inc Strategy 9.5 Nuance Communications Inc 9.5.1 Nuance Communications Inc Geographical Presence 9.5.2 Nuance Communications Inc IVA Technologies 9.5.3 Nuance Communications Inc Overview 9.5.4 Nuance Communications Inc Financial Analysis 9.5.5 Nuance Communications Inc Recent Developments 9.5.6 Nuance Communications Inc Historic Roadmap 9.5.7 Nuance Communications Inc Strategy: 9.6 Speaktoit, Inc 9.6.1 Speaktoit, Inc Geographical Presence: 9.6.2 Speaktoit, Inc IVA Technologies 9.6.3 Speaktoit, Inc Overview: 9.6.4 Speaktoit, Inc Financial Analysis: 9.6.5 Speaktoit, Inc Recent Developments 9.6.6 Speaktoit, Inc Historic Roadmap 9.6.7 Speaktoit, Inc Strategy 9.7 Artificial Solutions Ltd. 9.7.1 Artificial Solutions Ltd Geographical Presence: 9.7.2 Artificial Solutions Ltd IVA Technologies 9.7.3 Artificial Solutions Ltd Overview 9.7.4 Artificial Solutions Ltd Financial Analysis 9.7.5 Artificial Solutions Ltd Recent Developments 9.7.6 Artificial Solutions Ltd Historic Roadmap 9.7.7 Artificial Solutions Ltd Strategy: 9.8 eGain Communications Corporation 9.8.1 eGain Communications Corporation .Geographical Presence 9.8.2 eGain Communications Corporation .IVA Technologies 9.8.3 eGain Communications Corporation .Overview 9.8.4 eGain Communications Corporation .Financial Analysis: 9.8.5 eGain Communications Corporation .Recent Developments 9.8.6 eGain Communications Corporation .Historic Roadmap: 9.8.7 eGain Communications Corporation .Strategy 9.9 Anboto Group 9.9.1 Anboto Group Geographical Presence 9.9.2 Anboto Group IVA Technologies 9.9.3 Anboto Group Overview 9.9.4 Anboto Group Features c82 9.9.5 Anboto Group Financial Analysis: 9.9.6 Anboto Group Recent Developments 9.9.7 Anboto Group Strategy List of Tables Table 1.1: Market Snapshot: Global Intelligent Virtual Assistant Market (2016 and 2027) Table 2.1: Market Snapshot: Global Intelligent Virtual Assistant Market (2016 and 2027) Table 3.1: Internet Penetration by Country 2014-2016 (% of population) Table 4.1 Market Snapshot: North America Intelligent Virtual Assistant Market (2016 and 2027) Table 4.2 North America Intelligent Virtual Assistant Market Revenue and Forecast, By Technology, 2015 – 2027 (US$ Mn) Table 4.3 North America Intelligent Virtual Assistant Market Revenue and Forecast, By Application, 2015 – 2027 (US$ Mn) Table 4.4 North America Intelligent Virtual Assistant Market Revenue and Forecast, By End-user, 2015 – 2027 (US$ Mn) Table 4.5 North America Intelligent Virtual Assistant Market Revenue and Forecast, By Geography, 2015 – 2027 (US$ Mn) Table 5.1 Market Snapshot: Europe Intelligent Virtual Assistant Market (2016 and 2027) Table 5.2 Europe Intelligent Virtual Assistant Market Revenue and Forecast, By Technology, 2015 – 2027 (US$ Mn) Table 5.3 Europe Intelligent Virtual Assistant Market Revenue and Forecast, By Application, 2015 – 2027 (US$ Mn) Table 5.4 Europe Intelligent Virtual Assistant Market Revenue and Forecast, By End-user, 2015 – 2027 (US$ Mn) Table 5.5 Europe Intelligent Virtual Assistant Market Revenue and Forecast, By Geography, 2015 – 2027 (US$ Mn) Table 6.1 Market Snapshot: Asia Pacific Intelligent Virtual Assistant Market (2016 and 2027) Table 6.2 Asia Pacific Intelligent Virtual Assistant Market Revenue and Forecast, By Technology, 2015 – 2027 (US$ Mn) Table 6.3 Asia Pacific Intelligent Virtual Assistant Market Revenue and Forecast, By Application, 2015 – 2027 (US$ Mn) Table 6.4 Asia Pacific Intelligent Virtual Assistant Market Revenue and Forecast, By End-user, 2015 – 2027 (US$ Mn) Table 6.5 Asia Pacific Intelligent Virtual Assistant Market Revenue and Forecast, By Geography, 2015 – 2027 (US$ Mn) Table 7.1 Market Snapshot: Middle East and Africa Intelligent Virtual Assistant Market (2016 and 2027) Table 7.2 Middle East and Africa Intelligent Virtual Assistant Market Revenue and Forecast, By Technology, 2015 – 2027 (US$ Mn) Table 7.3 Middle East and Africa Intelligent Virtual Assistant Market Revenue and Forecast, By Application, 2015 – 2027 (US$ Mn) Table 7.4 Middle East and Africa Intelligent Virtual Assistant Market Revenue and Forecast, By End-user, 2015 – 2027 (US$ Mn) Table 7.5 Middle East and Africa Intelligent Virtual Assistant Market Revenue and Forecast, By Geography, 2015 – 2027 (US$ Mn) Table 8.1 Market Snapshot: Latin America Intelligent Virtual Assistant Market (2016 and 2027) Table 8.2 Latin America Intelligent Virtual Assistant Market Revenue and Forecast, By Technology, 2015 – 2027 (US$ Mn) Table 8.3 Latin America Intelligent Virtual Assistant Market Revenue and Forecast, By Application, 2015 – 2027 (US$ Mn) Table 8.4 Latin America Intelligent Virtual Assistant Market Revenue and Forecast, By End-user, 2015 – 2027 (US$ Mn) Table 8.5 Latin America Intelligent Virtual Assistant Market Revenue and Forecast, By Geography, 2015 – 2027 (US$ Mn) Table 9.1 Other Intelligent Virtual Assistant Companies List of Figures Figure 1.1: Global Intelligent Virtual Assistant Market Segmentation Figure 2.1: Global Intelligent Virtual Assistant Market, 2015 – 2027, Revenue (US$ Mn) and Y-o-Y Growth (%) Figure 2.2 Global Intelligent Virtual Assistant Market, by Technology, 2016 (US$ Mn) Figure 2.3 Global Intelligent Virtual Assistant Market, by Application, 2016 (US$ Mn) Figure 2.4: Global Intelligent Virtual Assistant Market, by End-user, 2016 (US$ Mn) Figure 2.5: Global Intelligent Virtual Assistant Market, by Geography, 2016 (US$ Mn) Figure 3.1: Customer Expectation of Online Relationship Management Figure 3.2: Intelligent Virtual Assistant System Figure 3.3: Global Intelligent Virtual Assistant Market, by Technology – Market Share and Forecast, 2016 Vs 2027 (Value %) Figure 3.4: Global Intelligent Virtual Assistant Market Revenue Growth for Text-to-speech, 2015 - 2027 (US$ Mn) Figure 3.5 Global Intelligent Virtual Assistant Market Revenue Growth for Speech Recognition, 2015 - 2027 (US$ Mn) Figure 3.6 Global Intelligent Virtual Assistant Market, by End-user – Market Share and Forecast, 2016 Vs 2027 (Value %) Figure 3.7 Global Intelligent Virtual Assistant Market Revenue Growth for Individual Users, 2015 - 2027 (US$ Mn) Figure 3.8 Global Intelligent Virtual Assistant Market Revenue Growth for Small and Medium Enterprise, 2015 - 2027 (US$ Mn) Figure 3.9 Global Intelligent Virtual Assistant Market Revenue Growth for Large Enterprise, 2015 - 2027 (US$ Mn) Figure 3.10 Global Intelligent Virtual Assistant Market, by Application – Market Share and Forecast, 2016 Vs 2027 (Value %) Figure 3.11 Global Intelligent Virtual Assistant Market Revenue Growth for Websites, 2015 - 2027 (US$ Mn) Figure 3.12 Global Intelligent Virtual Assistant Market Revenue Growth for Contact Centres, 2015 - 2027 (US$ Mn) Figure 3.13 Global Intelligent Virtual Assistant Market Revenue Growth for Messenger Bots, 2015 - 2027 (US$ Mn) Figure 3.14: Global Intelligent Virtual Assistant Market Positioning Analysis, 2016 Figure 4.1: Global Intelligent Virtual Assistant Market Share by Geography, 2016 and 2027 (%) Figure 4.2: North America Intelligent Virtual Assistant Market Revenue and Y-o-Y Growth, 2015 – 2027 (US$ Mn) Figure 5.1 Europe Intelligent Virtual Assistant Market Revenue and Y-o-Y Growth, 2015 – 2027 (US$ Mn) Figure 6.2 Asia Pacific Intelligent Virtual Assistant Market Revenue and Y-o-Y Growth, 2015 – 2027 (US$ Mn) Figure 7.1 Middle East and Africa Intelligent Virtual Assistant Market Revenue and Y-o-Y Growth, 2015 – 2027 (US$ Mn) Figure 8.1 Latin America Intelligent Virtual Assistant Market Revenue and Y-o-Y Growth, 2015 – 2027 (US$ Mn) Companies Mentioned in this Report Aetna Alpine Technology Fund Amazon Anboto Group Anthem Inc., Apple Inc. Artificial Solutions Ltd. Asia Telecom Autodesk Camelot UK Lotteries Limited Clara Labs CodeBaby Corporation Commercial Bank of Dubai (CBD) Creative Virtual Ltd. CX Company, Domino’s. E-Trade eBay Ecreation Group Pte. Ltd eGain Communications Corporation Eidoserve (GetAbby) Inc. Elisa Entatech UK Ltd. Existor Facebook Fido Intelligence Ltd. H-Care SRL Ford Google Honda Motor Company HSBC IBM Corporation iDavatars Inbenta Technologies Inc. Incesoft Co. Ltd. Indisys Intel Capital Intel Corporation InteliWISE S.A. IntelliResponse Systems Inc Jibo Kaspersky Labs LG Lloyds Banking Group Microsoft Corporation Motorola Solutions Venture Capital Mphasis MyCyberTwin Pty. Ltd. National Rail Enquiries Next IT Corporation Next IT Healthcare NIBC Direct Nuance Communications Inc. Oddcast Inc. Oracle Corporation Paypal Plug and Play Ventures Samsung Sharp Corporation Shell Speaktoit Inc Stanusch Technologies Stubhub Swedbank Group Symplmed Pharmaceuticals LLC Synthetix Ltd., TAM airlines Tesco The Selfservice Company Inc. Three-Sixty Advisory Group LLC Top Bank Twitter Verizon ViClone Corporation Virtual Zone Ltd. will.i.am Organisations Mentioned in This Report Blue Cross Blue Shield Association Cleveland Burke Lakefront Airport Cleveland Hopkins International Airport Dubai International Airport Dubai World Central Airport Gonzaga University Rochester Institute of Technology, The Association of American Medical Colleges (AAMC) U.S. Bureau of Economic Analysis US patent office Virginia Community College System (VCCS) For more information and orders please contact gabriel.diaz@vgtelecomreports.com Terms and Conditions By replying to this e-mail submitting your order for this product you have agreed without limitation or qualification to be bound by and to comply with these Terms and Conditions. You agree that you will not fail to complete any transaction after submitting an order to purchase a product or submit any order to purchase a product where you do not intend to complete the transaction. Management Reports will only be sent on receipt of payment. Our mailing address is: 230 City Road. EC1V 2QY, London, UK. As a valued contact or customer, you are receiving this email with information that we believe will be relevant to you. If however, you wish to stop future messages you can unsubscribe from this list From owner-freebsd-ppc@freebsd.org Fri Dec 16 04:42:40 2016 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D4B9CC76AAE for ; Fri, 16 Dec 2016 04:42:40 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: from mail-io0-x234.google.com (mail-io0-x234.google.com [IPv6:2607:f8b0:4001:c06::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9BB681612; Fri, 16 Dec 2016 04:42:40 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: by mail-io0-x234.google.com with SMTP id d9so88488206ioe.0; Thu, 15 Dec 2016 20:42:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:cc:message-id:from:to:in-reply-to:content-transfer-encoding :mime-version:subject:date:references; bh=kYao2+tZ7hamxShl13x7kBxY6EItCejzcwWYxG0J0KE=; b=s/Io4WkRMdQGw8G0A7NElf5WDiq0cH0my9yfXvQUNDXNwWjDFXqhqc0FkklWxVQhFz P803iqm+gTcd3V+320eFCK5jTJDRH6iK8v8bdPw7t2KajkXqODtEOKJMqtOL/Zpl8uNr zNuwh9yaTEV27+NPamuoNz7yrvgNERpD3ZDbWzY5b8cEDNIufROMTi0hwuYAsfzRY8po 2jMx6r4h6Fhupc6Njdc+RhisVuOoofW0nT1hWNI+52qResDaju7psLp6ruBGb3FAEWrD Z2XIXYeB0FSgTpjfD/e/4Xkr9IqYE2HpSmdAgLqsGz24+1YbCQIGW+U2lDU+xJ7IXrn0 /F4w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:cc:message-id:from:to:in-reply-to :content-transfer-encoding:mime-version:subject:date:references; bh=kYao2+tZ7hamxShl13x7kBxY6EItCejzcwWYxG0J0KE=; b=JqRcZDTdSqx3URmSKXZQBfruXenJeahT6lOL2DPbiIMx/rhcCTOS5BtkUR1FWa4K4g p1Fp/J3xklIag7NtWx3CX9tBoypEjiGS3nV0oiMjXboaLyZmfgaeypQUXBlraG0R2Ac3 fixTRlarituts6YpLIUDSGgT1HpgQIaR7fKp5Ph49Ul40oBgCL3z+V9deifdgeTA+oO+ 8z9tsCmaJV8FiagzBZCflA55/DQDTf7DjiqEVWnDYGr52jQUJ9Z4AZO0g3+nWhagPNTz azERtwoNkPW2z9WkoIXCcyhLU6Wo3gWOsxY5sS+K4KA3R0NYol7Y6SoCVuZ9+6/ETXXh ZtOA== X-Gm-Message-State: AIkVDXI7OP11q2c4gRwQGxI+BXCPslVCj/q4uBJSq24y7MC7ZaejrQ7OPuw8+/ojRv+o4A== X-Received: by 10.107.198.21 with SMTP id w21mr1207817iof.111.1481863358849; Thu, 15 Dec 2016 20:42:38 -0800 (PST) Received: from blackstar.knownspace (50-80-150-234.client.mchsi.com. [50.80.150.234]) by smtp.gmail.com with ESMTPSA id l79sm770137itb.1.2016.12.15.20.42.37 (version=TLS1 cipher=AES128-SHA bits=128/128); Thu, 15 Dec 2016 20:42:38 -0800 (PST) Sender: Justin Hibbits Cc: Nathan Whitehorn , FreeBSD PowerPC ML Message-Id: <96CACD85-DED4-46C6-BBE3-53B4DEFF89DD@FreeBSD.org> From: Justin Hibbits To: Mark Millard In-Reply-To: <0661C9A5-5D4C-4F00-9B0C-F80688BED8A4@dsl-only.net> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v936) Subject: Re: sys/powerpc/powerpc/trap.c has messed up masking operation?: use of || for bit field masling Date: Thu, 15 Dec 2016 22:42:36 -0600 References: <0661C9A5-5D4C-4F00-9B0C-F80688BED8A4@dsl-only.net> X-Mailer: Apple Mail (2.936) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2016 04:42:40 -0000 Hi Mark, On Dec 13, 2016, at 10:41 PM, Mark Millard wrote: > clang 3.9.0 is complaining about: > > --- trap.o --- > /usr/src/sys/powerpc/powerpc/trap.c:283:42: warning: use of logical > '||' with constant operand [-Wconstant-logical-operand] > frame->cpu.booke.dbcr0 &= ~(DBCR0_IDM || > DBCR0_IC); > ^ > ~~~~~~~~ > /usr/src/sys/powerpc/powerpc/trap.c:283:42: note: use '|' for a > bitwise operation > frame->cpu.booke.dbcr0 &= ~(DBCR0_IDM || > DBCR0_IC); > ^~ > | > Looking around: > > > # grep DBCR0_ /usr/src/sys/powerpc/include/spr.h > . . . > #define DBCR0_IDM 0x40000000 /* Internal Debug Mode */ > . . . > #define DBCR0_IC 0x08000000 /* Instruction > Completion debug event */ > . . . > > || use seems unlikely to be correct for the context. > Good find. Fixed in r310146, to be merged to stable/11 in a couple weeks. > > There is also this that I happened to notice sys/powerpc/powerpc/ > intr_machdep.c : > > --- intr_machdep.o --- > /usr/src/sys/powerpc/powerpc/intr_machdep.c:454:15: warning: > comparison of constant -1 with expression of type 'enum > intr_trigger' is always false [-Wtautological-constant-out-of-range- > compare] > if (i->trig == -1) > ~~~~~~~ ^ ~~ > /usr/src/sys/powerpc/powerpc/intr_machdep.c:500:16: warning: > comparison of constant -1 with expression of type 'enum > intr_trigger' is always false [-Wtautological-constant-out-of-range- > compare] > if (i->trig == -1) > ~~~~~~~ ^ ~~ This may or may not be a problem, depending on optimization settings. Can you file a bug for this so it doesn't get lost? > > There are other comparisons around with a constant > result at compile time. But they tend to be in less > central areas like zfs. Similarly for some other > types of compiler reports. > > === > Mark Millard > markmi at dsl-only.net > Thanks for the clang and external toolchain testing. Lots of good finds. - Justin From owner-freebsd-ppc@freebsd.org Fri Dec 16 08:08:16 2016 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 63F10C822FA for ; Fri, 16 Dec 2016 08:08:16 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-211-162.reflexion.net [208.70.211.162]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 12EE91CA6 for ; Fri, 16 Dec 2016 08:08:15 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 19660 invoked from network); 16 Dec 2016 08:01:29 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 16 Dec 2016 08:01:29 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v8.20.0) with SMTP; Fri, 16 Dec 2016 03:01:41 -0500 (EST) Received: (qmail 13020 invoked from network); 16 Dec 2016 08:01:41 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 16 Dec 2016 08:01:41 -0000 Received: from [192.168.1.103] (c-67-170-167-181.hsd1.or.comcast.net [67.170.167.181]) by iron2.pdx.net (Postfix) with ESMTPSA id BC135EC8FC4; Fri, 16 Dec 2016 00:01:28 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.1 \(3251\)) Subject: Re: sys/powerpc/powerpc/trap.c has messed up masking operation?: use of || for bit field masling From: Mark Millard In-Reply-To: <96CACD85-DED4-46C6-BBE3-53B4DEFF89DD@FreeBSD.org> Date: Fri, 16 Dec 2016 00:01:28 -0800 Cc: Nathan Whitehorn , FreeBSD PowerPC ML Content-Transfer-Encoding: quoted-printable Message-Id: <6335DBE9-4942-45B2-8DD7-0EDF781CA0F4@dsl-only.net> References: <0661C9A5-5D4C-4F00-9B0C-F80688BED8A4@dsl-only.net> <96CACD85-DED4-46C6-BBE3-53B4DEFF89DD@FreeBSD.org> To: Justin Hibbits X-Mailer: Apple Mail (2.3251) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2016 08:08:16 -0000 On 2016-Dec-15, at 8:42 PM, Justin Hibbits = wrote: > Hi Mark, >=20 > On Dec 13, 2016, at 10:41 PM, Mark Millard wrote: >=20 >> clang 3.9.0 is complaining about: >>=20 >> --- trap.o --- >> /usr/src/sys/powerpc/powerpc/trap.c:283:42: warning: use of logical = '||' with constant operand [-Wconstant-logical-operand] >> frame->cpu.booke.dbcr0 &=3D ~(DBCR0_IDM || = DBCR0_IC); >> ^ = ~~~~~~~~ >> /usr/src/sys/powerpc/powerpc/trap.c:283:42: note: use '|' for a = bitwise operation >> frame->cpu.booke.dbcr0 &=3D ~(DBCR0_IDM || = DBCR0_IC); >> ^~ >> | >> Looking around: >>=20 >>=20 >> # grep DBCR0_ /usr/src/sys/powerpc/include/spr.h >> . . . >> #define DBCR0_IDM 0x40000000 /* Internal Debug Mode = */ >> . . . >> #define DBCR0_IC 0x08000000 /* Instruction = Completion debug event */ >> . . . >>=20 >> || use seems unlikely to be correct for the context. >>=20 >=20 > Good find. Fixed in r310146, to be merged to stable/11 in a couple = weeks. Thanks. >>=20 >> There is also this that I happened to notice = sys/powerpc/powerpc/intr_machdep.c : >>=20 >> --- intr_machdep.o --- >> /usr/src/sys/powerpc/powerpc/intr_machdep.c:454:15: warning: = comparison of constant -1 with expression of type 'enum intr_trigger' is = always false [-Wtautological-constant-out-of-range-compare] >> if (i->trig =3D=3D -1) >> ~~~~~~~ ^ ~~ >> /usr/src/sys/powerpc/powerpc/intr_machdep.c:500:16: warning: = comparison of constant -1 with expression of type 'enum intr_trigger' is = always false [-Wtautological-constant-out-of-range-compare] >> if (i->trig =3D=3D -1) >> ~~~~~~~ ^ ~~ >=20 > This may or may not be a problem, depending on optimization settings. = Can you file a bug for this so it doesn't get lost? Bugzilla 215333 has the submittal. >>=20 >> There are other comparisons around with a constant >> result at compile time. But they tend to be in less >> central areas like zfs. Similarly for some other >> types of compiler reports. >>=20 >> =3D=3D=3D >> Mark Millard >> markmi at dsl-only.net >>=20 >=20 >=20 > Thanks for the clang and external toolchain testing. Lots of good = finds. Glad to help. > - Justin =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-ppc@freebsd.org Fri Dec 16 12:16:21 2016 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 570C4C82E60 for ; Fri, 16 Dec 2016 12:16:21 +0000 (UTC) (envelope-from admin@x162.save85off.com) Received: from x162.save85off.com (x162.save85off.com [43.240.238.162]) by mx1.freebsd.org (Postfix) with ESMTP id 2289F1D68 for ; Fri, 16 Dec 2016 12:16:20 +0000 (UTC) (envelope-from admin@x162.save85off.com) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; s=save85off; d=x162.save85off.com; h=MIME-Version:From:To:Date:Subject:Content-Type:Content-Transfer-Encoding; i=admin@x162.save85off.com; bh=6cqWRqWCLMvTQ8/he10ketrNdNU=; b=eplUUNo1gzv9T2kRhicicsKO1rdFFdVqFEQlM7G0WRxZRJ/AfnElxjbUk8+r/RVzsd33GGrPDOYD nKATUj7ftxSOG+XtPI1FT5J1bLHx74Ld3rn6rNlmTGxkoUzz6uwvFLSozBHK3oC/iMWJUzbj81eP olDphPxRKj0PjlQGI4s= DomainKey-Signature: a=rsa-sha1; c=nofws; q=dns; s=save85off; d=x162.save85off.com; b=m8+B4m6KXU4MZs7enrnx2yptFMK9+dkmdL1Xp2Ol8ysb1fwkeYTRAa6xa4Oh7W7Nq/2nQfC3dmeL UrL5lKXytMDL1bDn6Tlt5C2tJopQ0VZaseu+D7uy3dggkMldHeUzmriSYD7N4ci/I8ubALQYyfY/ qBrDhoaU/XPi7bzdHRk=; From: "UGG Big Deals" To: freebsd-ppc@freebsd.org Date: 16 Dec 2016 20:04:21 +0800 Subject: Christmas is here - want a little help with your Christmas shopping? win 151$ MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2016 12:16:21 -0000 From owner-freebsd-ppc@freebsd.org Sat Dec 17 01:18:07 2016 Return-Path: Delivered-To: freebsd-ppc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 74FF5C82AFA for ; Sat, 17 Dec 2016 01:18:07 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-211-169.reflexion.net [208.70.211.169]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2793D1C5C for ; Sat, 17 Dec 2016 01:18:07 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 2825 invoked from network); 17 Dec 2016 01:18:12 -0000 Received: from unknown (HELO mail-cs-02.app.dca.reflexion.local) (10.81.19.2) by 0 (rfx-qmail) with SMTP; 17 Dec 2016 01:18:12 -0000 Received: by mail-cs-02.app.dca.reflexion.local (Reflexion email security v8.20.0) with SMTP; Fri, 16 Dec 2016 20:18:08 -0500 (EST) Received: (qmail 19600 invoked from network); 17 Dec 2016 01:18:08 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 17 Dec 2016 01:18:08 -0000 Received: from [192.168.1.103] (c-67-170-167-181.hsd1.or.comcast.net [67.170.167.181]) by iron2.pdx.net (Postfix) with ESMTPSA id 63CE9EC9190; Fri, 16 Dec 2016 17:17:59 -0800 (PST) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Subject: The updates of devel/powerpc64-* to 6.2.0 have killed my ability to buildkernel targeting powerpc64: SIGSEGV's Message-Id: Date: Fri, 16 Dec 2016 17:17:58 -0800 To: FreeBSD Toolchain , FreeBSD PowerPC ML X-Mailer: Apple Mail (2.3259) X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Dec 2016 01:18:07 -0000 I have submitted bugzilla 215350: devel/powerpc64-gcc -r428604: The 6.2.0 based gcc (indirectly?) gets = SIGSEGV building src/sys/modules/agp/agp_if.o but ctfconvert involved Attempting to build src/sys/modules/agp/agp_if.o ets a SIGSEGV reported. Despite "segmentation fault" being reported for a powerpc64-gcc command the only .core file was for ctfconvert instead. ctfconvert does report its own death as well --but multiple times yet with only one core file present. With clang 3.9.0 issues and this there seem to be no modern toolchain for head for which I can do both buildworld and buildkernel and end up with a bootable PowerMac G5 powerpc64 system. For powerpc64 things have definitely regressed overall despite clang progressing some from where it was for 3.8.0 . Note: The problem was a test without forcing older devel/*-binutils or other such. I've yet to try such a mix-and-match involving xtoolchain. Extracted from the typescript: # grep "ERROR" = /root/sys_typescripts/typescript_make_powerpc64vtsc_nodebug_incl_clang_xto= olchain_kernel-amd64-host-2016-12-16:14:43:08 | more ERROR: ctfconvert: die 10273: failed to get ref: No entry found = [dwarf_attrval_unsigned(177)] ERROR: ctfmerge: No ctf sections found to merge .ERROR_TARGET=3D'agp_if.o' = .ERROR_META_FILE=3D'/usr/obj/powerpc64vtsc_xtoolchain_kernel/powerpc.power= pc64/usr/src/sys/GENERIC64vtsc-NODBG/modules/usr/src/sys/modules/agp/agp_i= f.o.meta' .ERROR_TARGET=3D'agp_if.o' = .ERROR_META_FILE=3D'/usr/obj/powerpc64vtsc_xtoolchain_kernel/powerpc.power= pc64/usr/src/sys/GENERIC64vtsc-NODBG/modules/usr/src/sys/modules/agp/agp_i= f.o.meta' .ERROR_TARGET=3D'all_subdir_agp' .ERROR_META_FILE=3D'' ERROR: ctfconvert: die 26932: failed to get ref: No entry found = [dwarf_attrval_unsigned(177)] .ERROR_TARGET=3D'' .ERROR_META_FILE=3D'' .ERROR_TARGET=3D'all_subdir_acl_posix1e' .ERROR_META_FILE=3D'' .ERROR_TARGET=3D'' .ERROR_META_FILE=3D'' .ERROR_TARGET=3D'all_subdir_acl_nfs4' .ERROR_META_FILE=3D'' ERROR: ctfconvert: die 46063: failed to get ref: No entry found = [dwarf_attrval_unsigned(177)] .ERROR_TARGET=3D'' .ERROR_META_FILE=3D'' .ERROR_TARGET=3D'all_subdir_ae' .ERROR_META_FILE=3D'' ERROR: ctfconvert: die 52618: failed to get ref: No entry found = [dwarf_attrval_unsigned(177)] . . . =3D=3D=3D Mark Millard markmi at dsl-only.net