similar to: [LLVMdev] Dubious code in llvm/lib/MC/MachObjectWriter.cpp

Hi, I've been slowly but steadily working towards enabling the Mach-O/PPC backend for MC, starting with the mach-o relocation entry translation. patches/logs: http://www.csl.cornell.edu/~fang/sw/llvm/ git: http://github.com/fangism/llvm/tree/powerpc-darwin8 git: http://github.com/fangism/clang/tree/powerpc-darwin8 I've managed to get the simplest single-function-call hello-world

On Thu, May 16, 2013 at 11:30 AM, Renato Golin <renato.golin at linaro.org> wrote: > On 16 May 2013 09:01, Csaba Raduly <rcsaba at gmail.com> wrote: >> >> "s390x--linux-gnu" seems wrong: either there's a dash too many or a >> word too few. > > > Nope, this triple is correct. The canonicalization of the triple (actually a > quadruple)

Hi, For a couple of days now, one of the tests fails: FAIL: LLVM :: MC/R600/sopp.s (16225 of 19902) ******************** TEST 'LLVM :: MC/R600/sopp.s' FAILED ******************** Script: -- /home/csabaraduly/workspace/LLVM/build/Release+Asserts/bin/llvm-mc -arch=r600 -mcpu=SI -show-encoding /home/csabaraduly/workspace/LLVM/llvm/test/MC/R600/sopp.s |

MSVC complains of truncating a double to a float. Let's just give it a float. -- GCS a+ e++ d- C++ ULS$ L+$ !E- W++ P+++$ w++$ tv+ b++ DI D++ 5++ Life is complex, with real and imaginary parts. "Ok, it boots. Which means it must be bug-free and perfect. " -- Linus Torvalds "People disagree with me. I just ignore them." -- Linus Torvalds -------------- next part

On Fri, Dec 24, 2010 at 10:32 AM, NAKAMURA Takumi wrote: > me2. I don't know why too slow. I know now. It was a debug build (enable-optimized=no) created only for trying out your patch on Util.py. Doh! -- GCS a+ e++ d- C++ ULS$ L+$ !E- W++ P+++$ w++$ tv+ b++ DI D++ 5++ Life is complex, with real and imaginary parts. "Ok, it boots. Which means it must be bug-free and perfect. "

On Wed, Apr 20, 2011 at 11:24 AM, Csaba Raduly <rcsaba at gmail.com> wrote: > On Wed, Apr 20, 2011 at 10:44 AM, Joe Armstrong  wrote: >> >> It seems very strange to me that the ansi standard says "XXX is >> undefined" and that both clang and gcc >> can detect that something is undefined and that by default they >> compile the offending code without

On 11/14/11, Alan Garny wrote: > For what is worth, I have been able to trace my problem (thanks Kevin Kelley > for the indirect help!). The 'culprit' was DLL Expert Viewer > (http://www.nirsoft.net/utils/dll_export_viewer.html). It kept reporting > that there were no exported functions, so I (wrongly) assumed that something > had gone wrong while, using PEInfo >

On Thu, Nov 14, 2013 at 4:40 AM, Mikael Lyngvig wrote: > Yes, ARM normally runs as a little-endian and it is a 32-bit CPU. It CAN be > configured to be a big-endian system, but that requires hardware support as > far as I know. > > I do have an old, slow Mac Mini G4 PowerPC (big-endian) that I could hook up > as a builder too. I was thinking of it the moment you mentioned big

On Thu, Oct 20, 2011 at 10:59 PM, monica j wrote: > The latest in my problems building clang-only: > > llvm[4]: Linking Debug+Asserts executable clang > /llvm/build/Debug+Asserts/lib/libclangLex.a: could not read symbols: File > format not recognized > collect2: ld returned 1 exit status What is the output of file /llvm/build/Debug+Asserts/lib/libclangLex.a ? Csaba -- GCS

Any input on this? I cleaned up the whole directory and re-build. still get the error. I am builing on x86. downloaded clang from llvm.org. Should I pick up an older version? llvm[4]: Linking Debug+Asserts executable clang > /llvm/build/Debug+Asserts/lib/libclangLex.a: could not read symbols: File > format not recognized > collect2: ld returned 1 exit status file

On Wed, Apr 20, 2011 at 10:44 AM, Joe Armstrong wrote: > > It seems very strange to me that the ansi standard says "XXX is > undefined" and that both clang and gcc > can detect that something is undefined and that by default they > compile the offending code without > any feelings of guilt. "The good thing — the only good thing! — about undefined behavior in

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:

On Mon, Jun 18, 2012 at 11:46 AM, Chandler Carruth wrote: > On Mon, Jun 18, 2012 at 2:32 AM, Mikael Lyngvig wrote: >> >> Hi, >> >> The docs state that you can do a "make update" to update all top-level and >> embedded projects from Subversion. > > > This is a feature of the configure+make build system, and not a feature of > the CMake build

Hi Anand On Wed, Feb 9, 2011 at 7:19 PM, Anand Arumugam wrote: > On Wed, Feb 9, 2011 at 9:40 AM, NAKAMURA Takumi wrote: >> >> Anand, >> >> >> I have not tried building llvm-gcc, though, ... >> >> Please show me "/path/to/config.status --version". > > [Anand] Here is the config.status output taken from '/cygdrive/c/llvm-2.8':

I wouldn't say that. I know quite a few systems here around that even try to avoid python where possible. but cmake however, as a build system, is welcomed by all of us (working as a sysop in a unix environment). I'd also (as a non-llvm-dev but llvm-userdev) vote for NOT reinventing the wheel but to use the tool the fits you the best, personally that's even cmake, too. it has a well

I have been working on getting ELF object file writing working for the MBlaze backend. Currently, each supported backend calls ELFObjectWriter::createELFObjectWriter from within the backend's TargetAsmBackend::createObjectWriter method. The createELFObjectWriter method then creates a new backend specific ELFObjectWriter class (either X86ELFObjectWriter or ARMELFObjectWriter) by decoding a

Hi all, LLVM+clang builds fine under Cygwin 1.7, but "make check-all" fails to run because lit doesn't find the freshly built clang. The reason is as follows: in llvm/utils/lit/lit/Util.py, in the "which" method, there's 66: # Get suffixes to search. 67: pathext = os.environ.get('PATHEXT', '').split(os.pathsep) The problem is, PATHEXT is imported

Hi, I haven't seen those errors. Clang and LLVM both build with no warnings on the 3 versions of GCC I test with. MSVC reports loads of warnings however. Cheers, James ________________________________________ From: Csaba Raduly [rcsaba at gmail.com] Sent: 23 October 2011 18:44 To: James Molloy Cc: Paul Berube; llvmdev at cs.uiuc.edu Subject: Re: [LLVMdev] build warnings On Sat, Oct 22,

On Sun, Oct 23, 2011 at 10:34 PM, James Molloy wrote: > Hi, > > I haven't seen those errors. Clang and LLVM both build with no warnings on the 3 versions of GCC I test with. MSVC reports loads of warnings however. > $ make happiness ... Updated to revision 142790. ... make[4]: Entering directory `/home/ecsardu/LLVM/build-tcclab1/tools/clang/tools/libclang' llvm[4]: Compiling

Compiling a simple automaton created by GNU bison with -O1 or -O2 resulted in the following machine code: 1300 /*-----------------------------. 1301 | yyreduce -- Do a reduction. | 1302 `-----------------------------*/ 1303 yyreduce: 1304 /* yyn is the number of a rule to reduce with. */ 1305 yylen = yyr2[yyn]; 0x0000000000400c14 <rpcalc_parse+628>: mov