similar to: [LLVMdev] Sefault in llvm-mc when emitting an object file

Hallo Guys, something went wrong and I didn't know from where. - uninstall vmware (removed to virtual adapter) - reinstall package with route and ping and glibc - test with original kernel and own vanilla nothing helps. Laptop by my side has same software stand no problem at all gdb --args ping benzler.me GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-94.el7 Copyright (C) 2013 Free

OCFS2 development team, We are on RHEL5 oracle-umawachorad01-+ASM1:/u00/app/oracle/admin/wachprd/bdump> uname -a Linux umawachorad01 2.6.18-92.el5 #1 SMP Tue Apr 29 13:16:15 EDT 2008 x86_64 We want to upgrade our current OCFS2 version 1.2.8 to the latest release 1.4.1 oracle-umawachorad01-+ASM1:/u00/app/oracle/admin/wachprd/bdump> cat /proc/fs/ocfs2/version OCFS2 1.2.8 Wed May 21

Hi, I had to add an include statement for the math header to LiveIntervalAnalysis.h to get it to compile today e.g #ifndef LLVM_CODEGEN_LIVEINTERVAL_ANALYSIS_H #define LLVM_CODEGEN_LIVEINTERVAL_ANALYSIS_H #include <math.h> It seems then to work without failures; odd. However, the deprecation warnings are not suppressed for std::_Uninit_Copy and std::_Copy_Opt (warning 4996) in xutility

Hi! I want to use LLVM for my own "pet" programming language compiler as a backend. Currently it generates C code, but I am not satisfied with this approach as generating high-level C (with proper type declarations!) is horrible. So here are my questions/problems with LLVM: 1.) Are there operations that add, sub, mul integers with overflow checking? How much work would it be to add

Hi Chris, Thanks for taking time to communicate on this. In your open points, you speak about upgrading the JIT code path. If I want to take a look (or at least try...) on it, what would be the "roadmap" ? I assume, a MCJITStreamer is needed. And probably a JITObjectWriter (inherits from MCObjectWriter) and an associated TargetAsmBackend specific to the JIT (JITX86AsmBackend) ? What

On Apr 11, 2010, at 10:35 AM, Olivier Meurant wrote: > Hi Chris, > > Thanks for taking time to communicate on this. Sorry I missed responding to this email sooner. > In your open points, you speak about upgrading the JIT code path. If I want to take a look (or at least try...) on it, what would be the "roadmap" ? > > I assume, a MCJITStreamer is needed. > And

Hello, Lance > With regards to my original problem, still requires flex/bison to configure, > and I have installed. The problem that brought me to the list turns out to > be that I have a copy of borland/inprises grep tool on the path (which I use > a lot). Heh, name clashing is well-known problem. Another source of such problems is 'sort' util. > Probably not an issue,

Hi list, Here it is: I have compiled with no problem courier-imap-4.0.4 on this arch (x86_64). Now I want to update my install with 4.0.6. I want to do this because the server is not yet in a production state, so if a major flaw affects courier-imap in the future, I could react more quickly. And indeed I'm encountering problems with the make process (Since I initialy build courier-imap

Hi all, I'm having some trouble with inline asm expressions, more specifically how to create the right FunctionType for a given constraint set. So far it has worked well for inputs, but not for outputs. The inline asm support in this language (which is D, LLVMDC[1]) is through asm *statements*. I never have inline asm *expressions*, and outputs are always via memory. I D my test looks like

? Fri, 9 May 2025 11:09:22 +1000 Stephen Wade <stephematician at gmail.com> ?????: > inlined from ?std::vector<double> literanger::adjust_pvalues(const > std::vector<double>&)? at ../src/literanger/utility_math.h:99:48: > /usr/include/c++/13/bits/stl_algobase.h:437:30: warning: ?void* > __builtin_memmove(void*, const void*, long unsigned int)? writing >

Hi, I double checked the configuration with xm and the "w!" option seems to be configured :-( I also upgraded to build 123, but also no change in behaviour. Thus is this a RAC 11.2 problem or is there a general problem using zvols as as shared disks for xVM domains ? (device (vbd (protocol x86_64-abi) (uuid 048d282d-da4c-2e0b-b9f4-f3f4cc0811c7)

The literanger package is no longer passing on CRAN (https://CRAN.R-project.org/package=literanger) due to array-bound warnings in GCC 13.3 and 14.2 (more details below). This _looks_ to me like one of either a) a compiler bug, b) a false positive, or c) (very unlikely) something in the standard library implementation. Have others seen warnings like this recently, and if so, what have you done

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 How can I use std::string in my winemaker project? If I do a #include <string> along with an #include <windows.h>, I get the following errors: - --- In file included from /usr/include/c++/3.3/i486-linux/bits/c++io.h:35, from /usr/include/c++/3.3/bits/fpos.h:44, from

Hopefully a member of the CRAN team will tell me I'm wrong, but I think whether or not there is a compiler bug is ultimately irrelevant -- packages on CRAN must compile cleanly even with potentially-buggy development versions of compilers. So, whether or not there is a bug in gcc is moot -- you'll need to find a way to avoid triggering this issue in your package code. Best, Kevin On

Hi, I am new to LLVM, so I am sorry if the question I am going to ask has already been raised before. I will be thankful if anyone can describe me a quick way to search relevant topics within the list archive, When I am trying to compile a simple code, containing access to std::string, with clang: #include <string> int main() { std::string s; return

I do have an opinion, but don't have enough time to comment in much depth. The approximate approach I had in mind sounds like what you describe, though, the JITObjectWriter is the core piece, the other pieces probably fall into place as it becomes obvious if they are needed. It should be pretty straightforward to bring up something which works for running code with no external symbols, if you

Hi all, I get this warning during compilation: make[3]: Entering directory `/home/wendling/llvm/llvm/lib/ExecutionEngine/JIT' Compiling Emitter.cpp Emitter.cpp:44:1: warning: "_POSIX_MAPPED_FILES" redefined In file included from /usr/include/unistd.h:171, from /usr/include/c++/3.3.1/i586-mandrake-linux-gnu/bits/gthr-default.h:38, from

I get the error below when trying to build clang with expensive checks. Works fine w/o these. Is this a known problem? This is on Ubuntu Hardy using this compiler: regehr at john-home:~$ g++ --version g++ (GCC) 4.2.4 (Ubuntu 4.2.4-1ubuntu4) Thanks, John Regehr make[4]: Entering directory `/home/regehr/z/tmp/llvm-r80385/tools/clang/lib/Basic' llvm[4]: Compiling Builtins.cpp for

Hello It looks like Ubuntu 13.04 has changed the include files directories structure Now we get the following error in many of our programs that compile fine on Ubuntu 12.04 > clang++ -c -x c++ -emit-llvm > ../../libsimsoc/processors/ppc/ppc_llvm_lib.cpp -DNDEBUG > -I/home/vania/systemc-2.3.0/include -I/home/vania/tlm2.0/include/tlm > -DSC_INCLUDE_DYNAMIC_PROCESSES

Hi ! > Sorry I missed responding to this email sooner. No problem, I was not in a hurry. :) > The approximate approach I had in mind sounds like what you describe, Ok Cool ! > I have been meaning to do this, but won't have time for a couple weeks I suspect. So I will give it a try. :) I was able to quickly hack a JITObjectWriter and I am able to execute simple functions (with