search for: kalintiris

...to do with the KILL instruction given the fact that the machine function pass calls TRI.invalidateLiveness()? Can we simply delete any KILL instruction we want? Or, can we ignore them as long as we don't request any register liveness analysis in subsequent machine function passes? -- Vasileios Kalintiris

On 5 September 2016 at 23:04, Krzysztof Parzyszek <kparzysz at codeaurora.org> wrote: > Let's first see how bad it is once bots are fixed to build the latest > revision. It's only been a few days and that includes a weekend. Of course. I'll wait until all our bots return from the first round to know the size of the damage. I just wanted to warn all other buildbot owners

Hi all, Is there any way to cross-compile LLVM and run check-all, or just the llvm-lit tests, (after moving the build directory) on the target machine? As far as I can tell from the CMakefiles, there's support only for cross-compiling LLVM and not for running the tests with the resulting compiler. Thanks, Vasileios

> From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] > On Behalf Of Kuperstein, Michael M via llvm-dev > Subject: Re: [llvm-dev] Test Email - Apologies for the noise > I'm seeing the same issue here, also with Outlook. > Had to CC the list manually for this email) Same problem here - good to know it's not just me. For reference, I'm using Outlook version

On 09/27/2015 06:41 PM, Vasileios Kalintiris wrote: > Hi Richard, > > Clang doesn't have support for MIPS I. The trap-on-condition instructions were added in MIPS II and they should work fine. This is why it works with ".set mips32r2". > > Which version of the ISA did you specify when you used the integrated assem...

Dear testers, The final version of 3.9.0 was just tagged (from the 3.9 branch at r280312). There were no changes after rc3. This took a little longer than expected, but on the up side that means it's had more time to be tested. Please build the final binaries and upload to the sftp. For others following along: this means 3.9.0 is complete, but it will take a few days to get the tarballs

> On Nov 2, 2015, at 11:41 AM, Vasileios Kalintiris <Vasileios.Kalintiris at imgtec.com> wrote: > >> The problem comes when bootstrapping a cross-compiler toolchain. In order to >> have a cross-compiling toolchain that can build a “hello world” application you >> need four basic components: >> >> (1) clang &g...

Thanks! Can you post the sha1's for the files you uploaded? Windows and Mac look good. Uploaded: ca26fbfabb54ac1f70776ab3a5503313ec518f18 clang+llvm-3.9.0-rc2-x86_64-apple-darwin.tar.xz 26d616e1355dc0802f90babbd5ea0b72abc0c0bb LLVM-3.9.0-rc2-win32.exe 42363aeaff395d442f418d77b542a088b5b0658b LLVM-3.9.0-rc2-win64.exe Thanks, Hans On Fri, Aug 19, 2016 at 9:22 AM, Diana Picus <diana.picus

On 9 October 2015 at 23:44, Vasileios Kalintiris via llvm-dev <llvm-dev at lists.llvm.org> wrote: > Both cmake & configure test for Python >= 2.7. Given the amount of python > code in the various scripts inside the LLVM projects, I wouldn't expect > Python 3.x to work for everything without changes. I use Arch, which de...

Apologies for the noise. I'm investigating a weird mail client issue that's been occurring for me since the mailing list switch and I've been unable to reproduce it outside of the list. When I click reply-all, Outlook removes all the LLVM mailing lists from the recipients list leaving just the individual recipients. Outlook Web Access is working perfectly fine. This thread is just to

Hi All, I am trying to build firefox with clang in Ubuntu 14.04 64bit. There is always configure failed errors problem. I follow compiling firefox with clang on linux <https://developer.mozilla.org/en-US/docs/Compiling_Firefox_With_Clang_On_Linux>. I add "export CC=clang export CXX=clang++" to mozconfig file. I wonder whether you guys have built firefox with clang in Linux. Could

We're very very close to the final release. Source and binaries for LLVM-3.9.0-rc3 are available at http://llvm.org/pre-releases/3.9.0/#rc3 This release candidate is almost the same as rc2, with the following additional commits: r279224 - Minor change to OpenCL release notes r279260 - [lld] Add a note that 3.9 is a major milestone for us r279468, r279474 - Fix gather-root.ll SLP vectorizer

Hi, Is there a rule or guideline about what Python versions must be supported for scripts in the LLVM tree? I am working on some patches to some scripts in LLVM to use features in Python 2.7, so that these scripts can run under Python 2.7 and Python 3.x Is that OK? For example, here is a patch to use print as a function, so that the scripts can work in Python 2.7 and Python 3.x -- Craig

The latest TOT of libunwind fails for me when I build UnwindRegistersSave.S for the Mips. My copy of clang uses a 2.25 binutils Mips assembler. This is the message I get: "/home/rich/ellcc/bin/mips-elf-as" -o /tmp/UnwindRegistersSave-a2c974.o -EL /tmp/UnwindRegistersSave-545450.s src/UnwindRegistersSave.S: Assembler messages: src/UnwindRegistersSave.S:99: Error: opcode not

.../clang/tools/extra/docs/ReleaseNotes.html http://llvm.org/releases/3.9.0/tools/lld/docs/ReleaseNotes.html Thanks to everyone who helped with filing, fixing and doing code review for release blocking bugs. Special thanks to the release testers and packagers: Dimitry Andric, Renato Golin, Vasileios Kalintiris, Diana Picus, Ben Pope and Nikola Smiljanic. Also thanks to Zhendong Su whose fuzz testing prevented many bugs going into this release. For questions or comments about this release, please contact the community on the mailing lists. Onward to 4.0! Cheers, Hans

.../clang/tools/extra/docs/ReleaseNotes.html http://llvm.org/releases/3.9.0/tools/lld/docs/ReleaseNotes.html Thanks to everyone who helped with filing, fixing and doing code review for release blocking bugs. Special thanks to the release testers and packagers: Dimitry Andric, Renato Golin, Vasileios Kalintiris, Diana Picus, Ben Pope and Nikola Smiljanic. Also thanks to Zhendong Su whose fuzz testing prevented many bugs going into this release. For questions or comments about this release, please contact the community on the mailing lists. Onward to 4.0! Cheers, Hans

...lease contains bug-fixes for the LLVM 3.9.0 release. This release is API and ABI compatible with 3.9.0. LLVM 3.9.1 would not be possible without the help of our volunteer release team! Thanks to all the release testers: Hans Wennborg, Brian Cain, Sylvestre Ledru, Ben Pope, Renato Golin, Vasileios Kalintiris, Dimitry Andric Also, a big thanks to everyone else who helped identify critical bugs, track down bug-fixes, and resolve merge conflicts. If you have questions or comments about this release, please contact the LLVMdev mailing list! LLVM 3.9.0 Release Announcement: http://lists.llvm.org/pipermai...

...such, I feel it's time for me to step down as code owner of the Mips target so that we have a single code owner throughout the LLVM 3.9 release which is scheduled to finish just after my last day. I'd like to nominate Simon Dardis as the new code owner. Is that ok with everyone? Vasileios Kalintiris is going to take over my release testing, starting with the 3.9 release. He will also be taking over my buildbots over the next few weeks. Daniel Sanders Leading Software Design Engineer, MIPS Processor IP Imagination Technologies Limited www.imgtec.com<http://www.imgtec.com/> -------------...

Hi, I have tagged 3.9.1-rc3. The only differences from -rc2 were a few bug fixes for ARM/AARCH64, so if you aren't testing either of these I think it's safe to take this -rc off and what for -final. I'm hoping to do -final next week after I get the ARM test results. Thanks, Tom

On 3 Dec 2014, at 23:36, Robert Lougher <rob.lougher at gmail.com> wrote: > On 2 December 2014 at 22:18, Alex Rosenberg <alexr at leftfield.org> wrote: >> >> Our C library amplifies this problem by being in a dynamic library, so the >> call has additional overhead, which for small trip counts swamps the >> copy/set. >> > > I can't imagine