similar to: [LLVMdev] lit test suite on Windows always hangs.

I am talking about Windows Mobile 8 and 8.1 and not CE. Not sure though that the Windows 8 (ARM NT) is similar to Windows Mobile 8 platform. I used the following command to generate the obj file Llc.exe -mtriple=thumbv7-windows -filetype=obj <some_name>.bc The object file generated in the above object doesn't get linked when I try to link it with the windows mobile library as it

Thanks a lot Saleem, The issue is fixed and a simple app works fine now. -Daman On 08/06/14 12:57 pm, "Nick Lewycky" <nicholas at mxc.ca> wrote: >Damanjit Singh wrote: >> Thanks Saleem, Nick. >> >> I will try with the latest code and share the results. >> >> Though, just curious if I need to really use clang to generate the >> object file

Hi Saleem, Though a simple app works great I am facing few issues trying to link a slightly complex object file, generated via LLVM, with some libs generated via Visual Studio - 1. Seems IMAGE_SCN_MEM_16BIT is only written for the the first header in the COFF file, thus functions in other headers (if you are using function sections) don’t work. I was able to workaround this by forcing this entry

On Wed, Jun 18, 2014 at 10:25 AM, Saleem Abdulrasool <compnerd at compnerd.org> wrote: > On Wed, Jun 18, 2014 at 9:09 AM, Damanjit Singh <dsingh at adobe.com> wrote: > >> Hi Saleem, >> >> Though a simple app works great I am facing few issues trying to link a >> slightly complex object file, generated via LLVM, with some libs generated >> via

Hi Saleem, I have a similar situation - I'd appreciate your inputs on it. I noticed that the obj file generated using llvm does not contain "thumb" instructions. I suspect that is what is causing runtime crash for me. Here's what I've tried - Start with a.c (on my linux machine where I have llvm/clang built as of yesterday) int add(int i, int j) {int k

Hi, Is there support available in llc to convert llvm bytecode to Windows Mobile binary? I have tried triples like arm-pc-win32 , thumbv7-window ... but the object file generated is not getting linked to the windows native project. Any pointers will be greatly appreciated? Thanks, ~rajat -------------- next part -------------- An HTML attachment was scrubbed... URL:

Thank you so much Saleem, The target is Windows phone 8.1 (ARM). I'll update the crash details tomorrow. One big problem is that I have to use a physical windows phone for execution. I wonder if it is possible to execute such "exes" using qemu. Regards, Kashyap On Sun, Jun 8, 2014 at 2:53 AM, Saleem Abdulrasool <compnerd at compnerd.org> wrote: > On Sat, Jun 7, 2014 at

Hi, After a discussion with David, Id like to propose a rework of the Windows target triples. The current set of Windows triples are somewhat less uniform than their Linux counterparts. With multiple ABIs and environments on Windows, they are also slightly awkward. Obviously, certain ones might be nice to keep around for compatibility (e.g. the mingw triple). Just to ensure that everyone has

Hello, I have a fix for Bug17623 (http://llvm.org/bugs/show_bug.cgi?id=17623) but I am not sure how best to install a regression test. The commands I use to run the test are (approximately) $LLVM/clang -flto -O2 -o BUG.o -c BUG.c $LLVM/llvm-lto -exported-symbol=main -o lto.o BUG.o $LLVM/clang -o bug lto.o ./bug Where the failing behavior is to seg fault and corrected behavior is to run to

Hi Sanjoy, Responses inlined… > On May 8, 2017, at 12:49 PM, Sanjoy Das <sanjoy at playingwithpointers.com> wrote: > > Hi Daniel, > > [+CC Mehdi, Vedant for the auto upgrade issue] > > On Mon, May 8, 2017 at 7:54 AM, Daniel Neilson via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> **Method** >> >> Clearly we are going to have to teach

Greetings all, I am picking up the work that was started in https://reviews.llvm.org/D27133 — adding support for an element-atomic memcpy/memset/memmove to LLVM. I would appreciate suggestions/thoughts/advice/comments on how to best proceed with this work in a way that will be acceptable to the LLVM group. I apologize in advance; this is going to be a long one... **Background** Loads/stores

Hi, I use wine to run a terminal emulator (NetTerm). It connects to a Linux Server (it was meant to run from windows) that runs a commerce software. This Linux commerce software sends the terminal emulator escape codes to interface with a "ticket" printer attached to a serial port. The reason to go thru all this problem is that the printer has a proprietary, closed source driver for

cmake -E cmake_progress_report llvm-3.8.0.src_bld_x86_64-rhel6.4-linux-gnu/CMakeFiles In file included from llvm-3.8.0.src/projects/libcxx/include/__hash_table:19:0, from llvm-3.8.0.src/projects/libcxx/src/hash.cpp:10: llvm-3.8.0.src/projects/libcxx/include/cmath:310:9: error: '::signbit' has not been declared using ::signbit; ^

Thanks for the info, that is very helpful. It does look like that change got back-ported to master, albeit in a different form. I'll take a look at how OpenVPN does its windows device I/O. - todd

Hi, The C backend in llc generates code like: static inline int llvm_fcmp_ord(double X, double Y) { return X == X && Y == Y; } static inline int llvm_fcmp_uno(double X, double Y) { return X != X || Y != Y; } First of all it generates a warning by clang and gcc (with certain flags): x.cbe.c:130: warning: comparing floating point with == or != is unsafe Now, C99 provides a macro for this

Hi i'm developing a sort of VoIP application for my ipaq using speex... I'm still at beginning and i have many problems encoding and decoding my wav files....output is only noise! Why? I'm using Libspeex 1.1.3, Embedded VisualC++ 3.0, Ipaq 3850(206 MHz Intel® Strong ARM 32-bit RISC Processor) PocketPC 2002 (Windows CE 3.0). Libspeex is complied with the definition of

Here's some C code: extern void *GetStdHandle(unsigned int nStdHandle); extern void ExitProcess(unsigned int exit_code); extern char WriteFile(void *HANDLE, const void * lpBuffer, unsigned int nNumberOfBytesToWrite, unsigned int *lpNumberOfBytesWritten, void *lpOverlapped); static const char *message_ptr = "hello\n"; static const unsigned int message_len = 6;

Greetings! I have been building llvm-3.6.x, 3.7.1 and 3.7.2 with (glibc-2.12.1, binutils-2.24, gcc-4.9.2) almost same set if CMake flags. However while building LLVM-3.8.0 using same CMake flags I am observing projects/libcxx/include/cmath errors... ...'::signbit' has not been declared ...'::fpclassify' has not been declared ...'::isfinite' has not been declared ...

Hi, I have attached a small patch from r192263 that I am using to add LLVM into the toolchain for VS2013. Is someone able to review this and (if all good) submit to the source tree? Changes are all local to llvm/tools/msbuild/ and account for VS2013 requiring the files to be named toolset.props / .targets, rather than the longer name in the previous versions. Cheers, Joshua Samuel

Hello, Today we hit another VS 2013 breakage < http://lab.llvm.org:8011/builders/sanitizer-windows/builds/26666/steps/run%20tests/logs/stdio> which results us having to alter LLVM. While we have no documented policy of supporting two version of MSVC, we do have an informal agreement that we should support the last two versions. I suggest that we alter our informal policy to the following: