search for: v4.0

Are there any updates on when LLVM v4.0 is to be released? Just curious, MartinO -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20170301/0811ce97/attachment.html>

I have to change a file in c:\Program Files <x86>\MSBuild\Microsoft.Cpp\v4.0. I have tried various ways to encapsule the Windows path with spaces but to no avail. The following file { "\"c:\\program files <x86>\\MSBuild\\Microsoft.Cpp\\v4.0\\Microsoft.CppCommon.targets\"": ensure => present, source =>

I am trying to upgrade to the LLVM v4.0 branch, but I am seeing failures in my TableGen descriptions for conversion from FP32 to FP16 (scalar and vector). The patterns I have are along the lines of: [(set (f16 RF16:$dst), (fround (f32 RF32:$src)))] or: [(set (v2f16 VF16:$dst), (fround (v2f32 VF32:$src)))] and these now produce the errors: error: In CONV_f32_f16: Type inference

> Have you tried compiling it yourself? I just installed git for the first time and downloaded all of the latest source code packages directly from the site. I'm getting the following every time I try to (re)build any of the projects: 1>------ Build started: Project: opus, Configuration: Release Win32 ------ 1> fatal: Not a git repository: 'C:\My

Hi Serge, Thanks for your help. I have looked at the change log, and so far as I can tell, my implementation is pretty much identical to all of the in-tree targets, but I’m missing something and can’t see what it is. I have simplified my TD description to just: def MyCallseqStart : SDNode<"ISD::CALLSEQ_START", SDCallSeqStart<[SDTCisVT<0, i32>,

Hello, With regards to Peter's comment, I got R to compile on OSF 4.0C, though I'm a little behind on versions. I only have 0.63.3 and haven't found anything newer... All kidding regarding typos aside, I went through that floating point exception business on the Alpha and I just didn't have time to make it work. Someone tipped me on to f2c, which I had used with my (old gcc

I wrote about my problems building R-0.63.3 on a Digital Alpha running OSF V4.0D. Thanks to the suggestion Jonathan.Yuen at tvs.slu.se, I tried using the DEC CC compiler instead of gcc, and it worked just fine. (Seeing that I needed gmake to build, it never occured to me to try DEC CC. It seems that you cannot combine DEC F77 with gcc; I do not have g77 to try.) Below is a set of instructions

CentOS 7.4 client mounting a CentOS 7.4 server filesystem over nfs4. nfs seems to be much slower since the upgrade to 7.4, so I thought it might be nice to mount the directory as v4.0 rather than the new default of v4.1 to see if it makes a difference. The release notes state, without an example: "You can retain the original behavior by specifying 0 as the minor version" nfs(5)

Hi Martin, Pseudo CALLSEQ_START was changed in r302527, commit message contains details on the changes. However CALLSEQ_END was not modified. If your made changes to ADJCALLSTACKUP to add additional argument, that may result in error. Thanks, --Serge 2017-09-15 19:09 GMT+07:00 Martin J. O'Riordan via llvm-dev < llvm-dev at lists.llvm.org>: > Hi LLVM-Devs, > > I have managed

Hello, I think the current implementation for the call "bl __aeabi_idiv0" in builtins\arm\udivsi3.S is broken. At least for the case that __aeabi_idiv0 returns. (the provided implementation does) Since LR is not preserved, the following JMP(lr) results in an endless loop. Or is this an intentional change of the behavior? The file contains another implementation enabled by

Hi LLVM-Devs, I have managed to complete updating our sources from LLVM v4.0 to v5.0, but I am getting selection errors for 'callseq_end'. I am aware that the 'ADJCALLSTACKUP' and 'ADJCALLSTACKDOWN' patterns have changed, and have added an additional argument to the TD descriptions for these. There are interactions with 'ISD::CALL' and 'ISD::RET_FLAG',

> > This is as expected. The build system is trying to get a git revision > string out of the source tree to compile in for reference. If you're > building from a downloaded source .zip, there won't be any git > information available and it will fall back to the hard-coded release > string. That's why the error isn't fatal to the build. Ok, this seems

R ran find on our Sun until it was stolen. I have now set up R on one of our Dec Alphas OSF1 V4.0 386. R-0.49 configures builds and runs fine except that the glm command crashes R. R-0.60.1 configures builds and runs until a cis entered. I think the problem is the floating point conventions but before I get in over my head a question Has anyone used glm successfully on Alphas OSF1 V4.0 386?

Yes, it's a bug. Please review https://reviews.llvm.org/D31716 On 4/5/2017 3:50 AM, Renato Golin wrote: > On 21 March 2017 at 18:32, Peter Jakubek via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> I think the current implementation for the call "bl __aeabi_idiv0" in >> builtins\arm\udivsi3.S is broken. >> At least for the case that __aeabi_idiv0

Is there maybe a way to consolidate (At the developer level) all of the tools and methods into one concise list. samba is not really tightly integrated with the OS, Is there maybe a way to re-organise the way samba works? maybe to make it completely emulate the way it works on the windows command line? for example make everything integrated into the net command..... net use (file system

We encountered a weird problem today, and I thought some of you might like to hear the solution. The underlying change was listed in the 7.4 changelog, so it's not a bug, but it may drive you buggy. The majority of our HPC cluster nodes run CentOS 7, though the exact patch levels vary from node to node. None is older than 7.3, but a few newer nodes were kickstarted right to 7.4. The

I am trying to install R-0.63.3 on a Digital Alpha running OSF V4.0D, and having some difficulties. Can anyone help? Also, I found some "oddities" in the installation process. I expect that this message is read by the developers, maybe some of my suggestions can be incorporated into future releases. Please reply to me directly (as well as possibly also to this mailing list): I am not a

Hi appreciate your help. I am new to puppet. I have taken over a system. Running Debian v4.0 Puppetmaster & puppet v0.20.1-1 I keep getting the following error from puppetmaster Could not connect to LDAP: Can''t contact LDAP server. Please advise me how to analyse and work through this problem. Thanks John --~--~---------~--~----~------------~-------~--~----~ You received this

Hello, There was no problem installing "APT" package in CentOS 4.0 Beta, but so far I could not install APT or Synaptic by "# yum install apt" or by "# yum install synaptic" in a usual manner. Is there any solution for this? It seems to me, something is wrong only for these two packages. Regards.

Hello, i use ubuntu 11.10 and wine 1.3.x i want install eveHq (http://www.evehq.net/downloads.html) and I read this (http://wiki.indiceve.com/doku.php?id=installation:installation) > EveHQ is written using Visual Studio .Net 2010 and requires the following to run: > > .Net Framework v3.5 SP1 > MS SQL Compact Edition v4.0 (for the databases) I can install MS SQL Compact