From owner-freebsd-ppc@freebsd.org Fri Oct 9 22:22: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 7E2BA9D1EAE for ; Fri, 9 Oct 2015 22:22:45 +0000 (UTC) (envelope-from trix@juniper.net) Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2on0138.outbound.protection.outlook.com [207.46.100.138]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "MSIT Machine Auth CA 2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3B6A11A4F for ; Fri, 9 Oct 2015 22:22:44 +0000 (UTC) (envelope-from trix@juniper.net) Received: from DM2PR05MB701.namprd05.prod.outlook.com (10.141.177.20) by DM2PR05MB704.namprd05.prod.outlook.com (10.141.177.26) with Microsoft SMTP Server (TLS) id 15.1.286.20; Fri, 9 Oct 2015 22:07:14 +0000 Received: from DM2PR05MB701.namprd05.prod.outlook.com ([10.141.177.20]) by DM2PR05MB701.namprd05.prod.outlook.com ([10.141.177.20]) with mapi id 15.01.0286.019; Fri, 9 Oct 2015 22:07:14 +0000 From: Thomas Rix To: Justin Hibbits CC: "freebsd-ppc@FreeBSD.org" Subject: Re: e500 SPE support Thread-Topic: e500 SPE support Thread-Index: AQHQ/yRlGfp7gvVmYkmEQzSGLV5iW55eJCEAgAWMnwD//5lQAA== Date: Fri, 9 Oct 2015 22:07:14 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.5.5.150821 authentication-results: spf=none (sender IP is ) smtp.mailfrom=trix@juniper.net; x-ms-exchange-messagesentrepresentingtype: 1 x-originating-ip: [66.129.239.11] x-microsoft-exchange-diagnostics: 1; DM2PR05MB704; 5:E8BIfsXvJBGwXyrWXWo6UJ3HrRizrvMO/YtobrBK0T/ZgyPT7Gy0FQxlf6i5IvWPVo2zT8a2cZOWpWcZ4yGOJR7MRwqHKGJWXbEtSATJSI2TdDlqIPAmFYDwDxugLirHWuqGvvOqtc1WSxODpQqcmg==; 24:65XlyzY2wgU0ZWJHMH0FdW5OP2gpnlY6XnPT2d1kBvGVM70YTOI5zUDUtR2sjDlUBhlPRK3RMOTY7EIClK+FmAQajp0DzqXJ4wlAFfrUprs=; 20:YDNAbO7bE63ptalH8IlTf4ZtkjYmJWOab0BHdQj7N49UoycEvxZsYDKvGsiluKIO3uSsU0IFp5LY4YsKFEQxXQ== x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(42134001)(42139001); SRVR:DM2PR05MB704; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(138986009662008); x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(520078)(5005006)(8121501046)(3002001); SRVR:DM2PR05MB704; BCL:0; PCL:0; RULEID:; SRVR:DM2PR05MB704; x-forefront-prvs: 0724FCD4CD x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(479174004)(164054003)(46034005)(199003)(24454002)(189002)(377454003)(2950100001)(1411001)(83506001)(15975445007)(92566002)(5002640100001)(77096005)(189998001)(86362001)(102836002)(2900100001)(66066001)(64706001)(97736004)(19580395003)(106356001)(19580405001)(106116001)(101416001)(4001350100001)(5004730100002)(11100500001)(99286002)(81156007)(5001960100002)(122556002)(110136002)(36756003)(105586002)(5008740100001)(40100003)(76176999)(46102003)(5007970100001)(87936001)(50986999)(54356999)(10400500002)(94096001); DIR:OUT; SFP:1102; SCL:1; SRVR:DM2PR05MB704; H:DM2PR05MB701.namprd05.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en; received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts) spamdiagnosticoutput: 1:23 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="iso-8859-1" Content-ID: <63F848A6D3E424489784875BE2AD891F@namprd05.prod.outlook.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: juniper.net X-MS-Exchange-CrossTenant-originalarrivaltime: 09 Oct 2015 22:07:14.6725 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4 X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM2PR05MB704 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 22:22:45 -0000 I have a p2020rdb I would prefer to use but it doesn=B9t seem to have freebsd kernel support so toolchain work is only on linux. Please send me a link to where you bought your board, I will see about getting one. Thanks, Tom =20 --- Tom Rix Sr. Staff Compiler Engineer trix@juniper.net On 10/9/15, 2:14 PM, "Justin Hibbits" wrote: >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" >chmeeedalf@gmail.com> >> 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" >>