search for: z196

...a default > for all the ports, but I can understand if people want to move this > way to reduce uncertainty. FWIW, since it's one of the three targets Jim mentioned, -march=z10 is the obvious default for SystemZ. On the other hand, I think it's good to run the tests on both z10 and z196, since there were significant additions to the architecture in z196. Until now we've been getting that by implicitly using -mcpu=z10 for cross testing on the usual x86_64 buildbots and implicitly using -mcpu=native (-mcpu=z196) on the z buildbot. We could do it instead by having two llcs and F...

> 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). Cool! > - focus on feature completeness

All, Currently the X86 backend does CPU auto-detection and subtarget feature detection when the TargetMachine is created if no explicit CPU was specified. It's counterintuitive for low level tools like ‘llc’ to do this, as it means the same .ll file compiled on heterogenous machines generates different results from the same ‘llc’ command line. It is still useful to be able to opt-in to such

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 a SystemZ backend used to be part of

...> > LLVM no longer attempts to automatically detect the > current host CPU when invoked natively. > > LLVM now supports all thread-local storage models on SystemZ. > (Previous releases would support only the local-exec TLS model.) > > LLVM now uses the POPCNT instruction on z196 and above. > > LLVM now uses the RISBGN instruction on zEC12 and above. > > LLVN now supports the transactional-execuction facility > on zEC12 and above. > > LLVM now supports the z13 processor and its vector facility. http://llvm.org/viewvc/llvm-project?rev=245102&view=re...

I have the following problem: # wbinfo -V Version 3.0.24 # wbinfo -a anyuser%goodpassword plaintext password authentication succeeded challenge/response password authentication succeeded # wbinfo -a anyuser%badpassword plaintext password authentication failed error code was NT_STATUS_WRONG_PASSWORD (0xc000006a) error messsage was: Wrong Password Could not authenticate user anyuser%badpassword

Hi, On SystemZ there are a set of "access registers" that can be copied in and out of 32-bit GPRs with special instructions. These instructions can only perform the copy using low 32-bit parts of the 64-bit GPRs. As reported and discussed at https://bugs.llvm.org/show_bug.cgi?id=44254, this is currently broken due to the fact that the default register class for 32-bit integers is

Dear everyone, The in-progress release notes for 3.7 [1,2] make it look like we didn't do very much over the past six months. Obviously that's not the case at all, so let's get them in shape! If you've been thinking "I should probably add this to the release notes at some point", now is the time :-) I have a list below of changes that might be worth mentioning. I