From owner-freebsd-ppc@freebsd.org Fri Oct 9 21:14:45 2015 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 BEFF79D2100 for ; Fri, 9 Oct 2015 21:14:45 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: from mail-ig0-x234.google.com (mail-ig0-x234.google.com [IPv6:2607:f8b0:4001:c05::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 8D8016D9 for ; Fri, 9 Oct 2015 21:14:45 +0000 (UTC) (envelope-from chmeeedalf@gmail.com) Received: by igbkq10 with SMTP id kq10so44763338igb.0 for ; Fri, 09 Oct 2015 14:14:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=V5HM6f6FVOds2r8Urm2y9j3REZekMX9/ZcJfTTf3H4w=; b=VzjMjEe3d5T2iEcdkTeQVN1ipqsDAhUvcITinck53Z0NMsokovshT2D4bij5Lwgndy RNcqe+0O3NjnLKUgpg5oP2sBMJlomFnw/HObJCLMaWdr6a2R7WzySTzbyCufAhprHywp +pq/BN/HYWiNJJglZ78HhX0J1xWjXsQNPEJqouofaMcvOgUj3Vbf2XCmN1GqemnbfN2o usIRPM4iG7Ltvud2GfcjYwyt+vdGFkBvneIwSN+S+OewsZ1YEHXYquMNKqTl+ae6Rct2 IUtzTDdJCvx0bZm985gx+CYC7ixjVFilowsZjMkARNbV/oWB7fhgrYNhsZz06lG55CnR DYwg== MIME-Version: 1.0 X-Received: by 10.50.118.42 with SMTP id kj10mr1486611igb.71.1444425284826; Fri, 09 Oct 2015 14:14:44 -0700 (PDT) Received: by 10.36.41.138 with HTTP; Fri, 9 Oct 2015 14:14:44 -0700 (PDT) In-Reply-To: References: Date: Fri, 9 Oct 2015 16:14:44 -0500 Message-ID: Subject: Re: e500 SPE support From: Justin Hibbits To: Thomas Rix Cc: "freebsd-ppc@FreeBSD.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-ppc@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting FreeBSD to the PowerPC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Oct 2015 21:14:45 -0000 After talking with others, I'll be creating a new target, powerpc/powerpcspe. This will live in a branch while I stabilize it (I'll create a branch this weekend). My testing will be on the Mikrotik RouterBoard RB800, but if anyone has hardware they can test on, all the better. To keep things simple, I'll be overloading the enable_vec()/save_vec() functions, and using this common API between Altivec and SPE. - Justin On Tue, Oct 6, 2015 at 10:30 AM, Thomas Rix wrote: > I see the spe feature is in ToT llvm, but not no target is has this > enabled by default. > What hardware/software are you using to exercise the feature ? > Asking so I could play too :) > > Likely folks wanting the feature would be willing to trade off with > altivec. > So mutually exclusive for me. > > Sprinkling code with spe specific seems clunky. > Could there be some task bit that linker/compiler sets that the loader > uses to do this automagically ? > A tie into the task state would help with ptrace and possible debugger > support. > > Tom > > --- > Tom Rix > Sr. Staff Compiler Engineer > trix@juniper.net > > > > > > On 10/4/15, 9:14 PM, "owner-freebsd-ppc@freebsd.org on behalf of Justin > Hibbits" > wrote: > >>I've been doing some work on the e500 Signal Processing Engine (SPE, >>sort of like Altivec, only weirder), but have some questions on >>implementation: >> >>* This is mutually exclusive to Altivec, of course, because it shares >>the GPRs, extending them to 64-bits, but only for SPE instructions. >>Should the implementation be mutually exclusive, as well? Meaning, is >>it better to have enable_spe()/save_spe() strewn throughout the code, >>like is done with Altivec and FPU, or is it better to name them >>*_vec(), and have a compile-time option of switching between Altivec >>and SPE? The userland ABI would be different as well, which brings the >>next question: >> >>* Do we want another target, like how Linux does it (powerpcspe)? Or >>have this as just a different build option in src.conf? >> >>Suggestions are welcome and wanted. >> >>- Justin >>_______________________________________________ >>freebsd-ppc@freebsd.org mailing list >>https://lists.freebsd.org/mailman/listinfo/freebsd-ppc >>To unsubscribe, send any mail to "freebsd-ppc-unsubscribe@freebsd.org" >