similar to: [LLVMdev] RFC: TileGX, a new backend for Tilera's many core processor

On 03/01/2013 02:57 PM, Hal Finkel wrote: Hi Hal, thanks for feedback. > Jiong, I am happy to see the Tile backend being offered for upstream inclusion. Among other things, in the long run, this may help inform and motivate many-core capabilities in LLVM. > > First, can you elaborate on the future maintenance and development plans for the target code? Do you plan to add SIMD support?

----- Original Message ----- > From: "Jiong Wang" <jiwang at tilera.com> > To: "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu>, cfe-dev at cs.uiuc.edu > Sent: Thursday, February 28, 2013 6:09:20 PM > Subject: [LLVMdev] RFC: TileGX, a new backend for Tilera's many core processor > > Hi, > > On behalf of Tilera Corporation,

----- Original Message ----- > From: "Jiong Wang" <jiwang at tilera.com> > To: "Hal Finkel" <hfinkel at anl.gov> > Cc: "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu>, cfe-dev at cs.uiuc.edu > Sent: Friday, March 1, 2013 1:34:15 AM > Subject: Re: [LLVMdev] RFC: TileGX, a new backend for Tilera's many core processor >

On 03/01/2013 10:42 PM, Hal Finkel wrote: > > As some of the llvm modules are in active development, for example MC > Layer, we want to return code to community repository first, so that > it will be easy to keep pace with llvm main tree. > I think this makes sense; but my impression is that the community will want a clear idea that this will be maintained and improved for the

On 03/02/2013 04:50 AM, Dmitri Gribenko wrote: > You also need tests for Clang bits, too. > > Mechanical issues: > > +/// getTileRegisterNumbering - Given the enum value for some register, > +/// return the number that it corresponds to. > > Please don't duplicate function and class name in comments. Existing > code does this, but current style guidelines advise not

Hi all, Updated the patches for TILE-Gx backend: 1. added initial regression tests for tilegx codegen. 2. added initial regression tests for MC Layer. 3. fixed those commenting style issues. please review, thanks. I have tried to understand the new backend requirement for LLVM from the mailiing list archive, it's sure TILE-Gx backend will be actively maintained & improved, it's

On Thu, Mar 7, 2013 at 6:33 PM, Jiong Wang <jiwang at tilera.com> wrote: > Hi all, > > Updated the patches for TILE-Gx backend: > > 1. added initial regression tests for tilegx codegen. > 2. added initial regression tests for MC Layer. > 3. fixed those commenting style issues. > > please review, thanks. This is a huge patch, and reviewing it in tar.gz is hard. To

On 03/08/2013 04:48 AM, Dmitri Gribenko wrote: > On Thu, Mar 7, 2013 at 6:33 PM, Jiong Wang <jiwang at tilera.com> wrote: >> Hi all, >> >> Updated the patches for TILE-Gx backend: >> >> 1. added initial regression tests for tilegx codegen. >> 2. added initial regression tests for MC Layer. >> 3. fixed those commenting style issues. >>

Hi Chris, could you please comment on committing TILE-Gx backend into community? ========== TILE-Gx Status =========== Features Supported === 1. general function. 2. PIC/TLS/JumpTable. 3. Instructoin Bundling for VLIW. 4. Asm Parser 5. MC Layer (aware of instruction bundle), MCJIT support. 6. Initial regression tests for CodeGen & MC Layer. Regression Result === Expected Passes : 13363

On Mar 19, 2013, at 8:58 PM, Jiong Wang <jiwang at tilera.com> wrote: > Hi Chris, > > could you please comment on committing TILE-Gx backend into community? Hi Jiong, I don't have any special advice here. It sounds like the general functionality level is high enough. Taking it into mainline sounds great, so long as it is reviewed by someone. -Chris > > >

on 2013/3/23 1:52, Chris Lattner wrote: > On Mar 19, 2013, at 8:58 PM, Jiong Wang <jiwang at tilera.com> wrote: > >> Hi Chris, >> >> could you please comment on committing TILE-Gx backend into community? > Hi Jiong, > > I don't have any special advice here. It sounds like the general functionality level is high enough. Taking it into mainline sounds

On Fri, Mar 08, 2013 at 12:33:58AM +0800, Jiong Wang wrote: > please review, thanks. configure.ac: I guess it would be preferable to not enable it by default for the moment. include/llvm/Support/FEnv.h: What is supposed to handle? Build on/for Tile? Does the platform provide fenv.h but in a broken way? lib/Target/Mips/MCTargetDesc/MipsMCAsmInfo.cpp: Is this change intentional? Personally, I

On 03/03/2013 02:09 PM, Timothy Mattausch Creech wrote: > Hi, > We would like to inform the community that we're releasing a version of our research compiler, "AESOP", developed at UMD using LLVM. AESOP is a distance-vector-based autoparallelizing compiler for shared-memory machines. The source code and some further information is available at > >

On Fri, Mar 1, 2013 at 4:52 PM, Jiong Wang <jiwang at tilera.com> wrote: > On 03/01/2013 10:42 PM, Hal Finkel wrote: >> >> >> As some of the llvm modules are in active development, for example MC >> Layer, we want to return code to community repository first, so that >> it will be easy to keep pace with llvm main tree. >> I think this makes sense; but

On Mar 8, 2013, at 2:31 AM, Jiong Wang <jiwang at tilera.com> wrote: > On 03/08/2013 04:48 AM, Dmitri Gribenko wrote: >> On Thu, Mar 7, 2013 at 6:33 PM, Jiong Wang <jiwang at tilera.com> wrote: >>> Hi all, >>> >>> Updated the patches for TILE-Gx backend: >>> >>> 1. added initial regression tests for tilegx codegen. >>>

Hi, We would like to inform the community that we're releasing a version of our research compiler, "AESOP", developed at UMD using LLVM. AESOP is a distance-vector-based autoparallelizing compiler for shared-memory machines. The source code and some further information is available at http://aesop.ece.umd.edu The main components of the released implementation are loop memory

On 03/23/2013 10:51 AM, Jiong Wang wrote: > on 2013/3/23 1:52, Chris Lattner wrote: >> On Mar 19, 2013, at 8:58 PM, Jiong Wang <jiwang at tilera.com> wrote: >> >>> Hi Chris, >>> >>> could you please comment on committing TILE-Gx backend into community? >> Hi Jiong, >> >> I don't have any special advice here. It sounds like the

On Sat, Mar 23, 2013 at 04:59:49PM +0100, Tobias Grosser wrote: > With Chris's reply you also got the general OK to upstream the > patch, _AFTER_ the actual patches have been reviewed. One thing I was asking on IRC for is whether it makes sense for new backends to be committable in incremental steps. Especially for a complete backend like this, e.g. the asm parser would make a

于 2013/3/24 0:07, Joerg Sonnenberger 写道: > On Sat, Mar 23, 2013 at 04:59:49PM +0100, Tobias Grosser wrote: >> With Chris's reply you also got the general OK to upstream the >> patch, _AFTER_ the actual patches have been reviewed. > One thing I was asking on IRC for is whether it makes sense for new > backends to be committable in incremental steps. Especially for a >

On Sat, Mar 23, 2013 at 12:34 PM, Jiong Wang <jiwang at tilera.com> wrote: > 于 2013/3/24 0:07, Joerg Sonnenberger 写道: > > On Sat, Mar 23, 2013 at 04:59:49PM +0100, Tobias Grosser wrote: >> >>> With Chris's reply you also got the general OK to upstream the >>> patch, _AFTER_ the actual patches have been reviewed. >>> >> One thing I was