search for: systemz

Hello, this set of patches adds SystemZ support to base LLVM. This is split up into three patches just to simplify review; they should be committed as a single change if approved. The first patch adds SystemZ support to the configure logic and support for the systemz Triple. This ought to be straightfoward. The second patch adds chan...

Hello, this set of patches adds platform-specific support to the base LLVM test suite. The first patch adds 290 new SystemZ CodeGen (.ll) tests. The second patch adds 582 new SystemZ MC assembler (.s) tests. The third patch adds the usual test suite config changes for a platform that supports MCJIT, but not the old JIT, modeled after existing changes for PPC64 and AARCH64. Overall, this test of tests ought to provide s...

Hal Finkel <hfinkel at anl.gov> wrote on 23.03.2015 19:42:06: > > >Attached are draft patches that do this for X86. Similar but smaller > > >cleanups can also be done for SystemZ and PowerPC if it’s agreed > > >this is a good idea. > > > > However, this was then never implemented for SystemZ and PowerPC. > > Should we do so as well? > > Yes, I think we should. Checked in for SystemZ as r233540. Do you want me to do PowerPC too? Bye, Ulric...

What assembler are people using with the SystemZ backend? I am trying to assemble the output of the SystemZ backend with the GNU binutils assembler (build with --target=s390x-linux). I get errors when assembling instructions with literals that are negatives. For example, the test case test/CodeGen/SystemZ/01-RetImm.ll gives errors: $ s390x...

Hello, this set of patches adds Clang support for SystemZ. The first patch adds a new common code feature that allows platform code to request minimum alignment of global symbols. The background for this is that on System Z, the most efficient way to load addresses of global symbol is the LOAD ADDRESS RELATIVE LONG (LARL) instruction. This instruction...

Hi, Two days ago, the test suite started failing. Initially there were hundreds of failing tests; now only seven remain. They appear to be related to SystemZ. Here's the last failed test: ******************** FAIL: LLVM :: MC/Disassembler/SystemZ/unmapped.txt (11484 of 14435) ******************** TEST 'LLVM :: MC/Disassembler/SystemZ/unmapped.txt' FAILED ******************** Script: -- /home/myself/workspace/LLVM/build/Release+Asserts/bin/...

Hi Anton, On 01/30/2011 12:44 PM, Anton Korobeynikov wrote: > Hello > >> I am trying to assemble the output of the SystemZ backend with the GNU >> binutils assembler (build with --target=s390x-linux). I get errors when >> assembling instructions with literals that are negatives. For example, >> the test case test/CodeGen/SystemZ/01-RetImm.ll gives errors: > There are different instruction sets fo...

Richard Sandiford wrote: >I'd like to step down as code owner for the SystemZ port and nominate >Ulrich Weigand to take over. Sorry for not doing this sooner. I'd be happy to take over that role. Thanks for all your work on SystemZ, Richard! Bye, Ulrich

Hi All, I had some questions regarding the SystemZ implementation and missing instructions. I've been comparing the IBM z/Architecture Reference Summary (SA22-7871-08) to the output of "llvm-tblgen SystemZ.td -print-enums -class=Instruction" and noticed that there's 525 missing instructions. For example, if I look at instruction...

...rding to the feature string for that CPU. This >(a) changes the auto-detection from opt-out to opt-in and (b) moves >the logic out of the core target backend and into the tools drivers. >Attached are draft patches that do this for X86. Similar but smaller >cleanups can also be done for SystemZ and PowerPC if it’s agreed this >is a good idea. However, this was then never implemented for SystemZ and PowerPC. Should we do so as well? Note that mesa has in the meantime changed to do the auto-detection before setting up the JIT context, and I assume other JIT users have done so as well...

Hello > I am trying to assemble the output of the SystemZ backend with the GNU > binutils assembler (build with --target=s390x-linux).  I get errors when > assembling instructions with literals that are negatives.  For example, > the test case test/CodeGen/SystemZ/01-RetImm.ll gives errors: There are different instruction sets for z/System. Basic...

Hello, I'd like to propose the addition of a new SystemZ backend to the LLVM and Clang code base. We're interested in this for the same reason we've been interested in the PowerPC back-end recently: to enable packages in upcoming enterprise Linux distributions that need LLVM support (e.g. 3D desktop support via llvmpipe). Now, I understand that...

> I'd still like to know if anyone has sucessfully assembled SystemZ generated > assembly language with a binutils assembler, and if so, how. Almost all testsuite passed ~ 1.5 years ago (with clang + gas). I doubt anyone tried to assembler anything else after that time. -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersb...

On 01/30/2011 02:09 PM, Anton Korobeynikov wrote: >> I'd still like to know if anyone has sucessfully assembled SystemZ generated >> assembly language with a binutils assembler, and if so, how. > Almost all testsuite passed ~ 1.5 years ago (with clang + gas). I > doubt anyone tried to assembler anything else after that time. > Lots of things have changed in 1.5 years with respect to assembly output,...

...achineFrameInfo::HasCalls" is calculated. Basically, the way it's calculated now is in PEI. And it only looks for frame adjustments (or inline ASM) to determine if the function has a call or not. This way is much more accurate and occurs much sooner. But it breaks this test: test/CodeGen/SystemZ/2009-07-10-BadIncomingArgOffset.ll (See below for the output with this patch.) The problem is that SystemZ is using "hasCalls()" in the back end to determine if a frame pointer is needed or not. My guess is that several of the places where it calls hasCalls() should really be hasFP(). I...

Hi, I have come across a major regression resulting after SLP vectorization (+18% on SystemZ, just for enabling SLP). This all relates to one particular very hot loop. Scalar code: %conv252 = zext i16 %110 to i64 %conv254 = zext i16 %111 to i64 %sub255 = sub nsw i64 %conv252, %conv254 ... repeated SLP output: %101 = zext <16 x i16> %100 to <16 x i64> %104 =...

...eing many instances of the following LLVM error message appearing in the Postgres server log: ORC error: No callback manager available for s390x-ibm-linux (strangely, it otherwise doesn't seem to be causing any problems) Looking through the LLVM source code, it appears that for the "systemz" architecture, there is currently no local CCMgr implementation available, and this then prevents indirection support and COD layer support. BUT - apparently it can still function (maybe less efficiently?) without these? Is somebody able to clarify exactly what that error message means and wh...

Hi, I found with the help of the optimization remarks a loop that could not be vectorized, but if loop distribution was enabled this may happen, which it in fact did with a very significant benchmark improvement (~25%). I tried (on SystemZ) to enable this pass, and found that it only affected a handful of files on SPEC. This means I could enable this without worrying about any regressions on SystemZ at least currently. I wonder if there is something more to know about this. It seems that no other target has enabled this due to ge...

> I'd like to propose the addition of a new SystemZ backend to the LLVM and > Clang code base. We're interested in this for the same reason we've been > interested in the PowerPC back-end recently: to enable packages in upcoming > enterprise Linux distributions that need LLVM support (e.g. 3D desktop > support via llvmpipe). Coo...

Hi, SystemZ supports @llvm.ctlz.i64() natively with a single instruction (FLOGR), and lesser bitwidth versions of the intrinsic are promoted to i64. For some reason, this leads to unfolded additions of constants as shown below: This function: define i16 @fun(i16 %arg) {   %1 = tail call i16 @llvm.ctlz.i1...