similar to: undefined symbol EnableABIBreakingChecks

> On Nov 16, 2016, at 12:05 PM, Jonathan Roelofs <jonathan at codesourcery.com> wrote: > > > > On 11/16/16 11:48 AM, Mehdi Amini via llvm-dev wrote: >> Hi all, >> >> An issue that come up from time to time and has cost hours for debug for >> many of us and users of LLVM is that an assert build isn’t ABI >> compatible with a release build.

Hi all, An issue that come up from time to time and has cost hours for debug for many of us and users of LLVM is that an assert build isn’t ABI compatible with a release build. The CMake flags that controls this behavior is LLVM_ABI_BREAKING_CHECKS ( LLVM_ABI_BREAKING_CHECKS:STRING Used to decide if LLVM should be built with ABI breaking checks or not. Allowed values are WITH_ASSERTS (default),

Hi, I am very excited to take the awesome tutorial of implementing *Kaleidoscope*. But I got stuck here... I have done the AST parsing, however, when I introduce these 'llvm/IR/*' headers, I got a compiling error... But if I delete these headers it runs well ... """headers #include "llvm/IR/BasicBlock.h" #include "llvm/IR/Constants.h" #include

Hello List like described in the topic I have a problem with starting the libvirtd. I'm a complete newbie with libvirtd, today I heard the first time that such a daemon exists after I get the message that our webserver isn't running (a former colleague has installed this system). We have the following configuration: A Ubuntu based host on which our webserver runs within a qemu virtual

Hi, I am brand new to LLVM, or more precisely, trying to be. I'm getting stuck on compiling LLVM. - I tried installing on a Mint 18.1 VM with 6GB RAM, and the builds of some large executables were killed by the OOM killer. I finally realized that I needed to build using shared libraries, and succeeded. This was in November. - I put aside my LLVM project, and just got back to it. I got stuck

I just built up a server running CentOS 4.3, and trying to boot from a 3Ware 9550SX-16ML, 16 port card. This system has 9x500GB drives, AMD Opteron, Tyan K8SD mobo and 1 GB of ram. I downloaded the latest (9.3.0.4) driver from 3Ware, and after a couple of botched attempts, I got CentOS installed. In my two botched attempts, the problem was X hanging during the formatting of the drives, so I

The use case is getting the short name for backtraces. There are other options, but I figured it was worth a shot trying to access from the DWARF structure because what we need is already stored there anyway. Thanks, Isaiah On Wed, May 7, 2014 at 12:24 PM, Alexey Samsonov <samsonov at google.com>wrote: > Yeah, public API of DebugInfo library is quite minimalistic. But I agree >

On Tue, Dec 13, 2016 at 4:57 PM, Grang, Mandeep Singh via llvm-dev <llvm-dev at lists.llvm.org> wrote: > Everyone, > > The following patch to reverse iterate SmallPtrSet's has now been merged: > https://reviews.llvm.org/D26718 > > This is how LLVM behavior will change due to this patch: > - In LLVM builds with assertions enabled, SmallPtrSet's would always be

hello everyone! i have a problem checking out the icecast cvs. the checkout stalls after pulling timing/timing.h (no matter which module, they all seem to depend on it). i have to kill it after a while. am i doing anything wrong, or is your cvs botched ? for now, i'm using a nightly snapshot, but i can't find ices2 in it, so i tried to pull cvs. btw, the chroot feature is cool. i

Hi, I am looking for a way to get unmangled subprogram names from a DWARFContext. The name I want is available in the attribute `DW_AT_name` [1], but as far as I can tell this is only returned as a fallback in `DWARFDebugInfoEntryMinimal::getSubroutineName` when the linkage name is not available [2]. If this is not currently possible, is there any interest in adding such access to the public

On Wed, May 7, 2014 at 11:33 AM, Eric Christopher <echristo at gmail.com>wrote: > Have you checked out llvm-symbolize? It's what the asan folk > (including Alexey) have created for backtrace symbolication. > Yeah, we potentially can add some kind of option: "llvm-symbolizer -print-short-function-names", I don't yet see why this would be valuable. What's wrong

On Thu, Jul 5, 2012 at 12:10 AM, <bigcheesegs at gmail.com> wrote: > On Jul 5, 2012, at 1:08 AM, Chandler Carruth <chandlerc at google.com> wrote: > > In the same way that the core LLVM libraries have support routines for > DWARF, I think that both mangling and demangling should be provided as well. > > > How would LLVM provide support for mangling? And what tools

Hi everyone, we have several header files in which the NDEBUG macro is being used. In some of these, the NDEBUG macro changes the size, the interface, or the layout of a type. One example is AssertingVH, which turns into a flat, transparent Value* wrapper in Release build. Now everywhere you use these headers, the state of the NDEBUG flag must be the same, or else bad things could happen. This

On Tue, Dec 13, 2016 at 6:39 PM, Hans Wennborg <hans at chromium.org> wrote: > On Tue, Dec 13, 2016 at 4:57 PM, Grang, Mandeep Singh via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> Everyone, >> >> The following patch to reverse iterate SmallPtrSet's has now been merged: >> https://reviews.llvm.org/D26718 >> >> This is how LLVM

Sorry, I botched a commit and broke the build. I've just committed a fix. So expect to see some buildbot churning. -Dave

On Monday 15 February 2010 11:54:25 Óscar Fuentes wrote: > David Greene <dag at cray.com> writes: > > Sorry, I botched a commit and broke the build. I've just committed a > > fix. > > > > So expect to see some buildbot churning. > > Don't hurry. A buildbot already decided that I am the only culprit of > the breakage. :-/ Hmm...given that

I think I botched syslinux-6.04-pre3. There are two fundamental problems with the build: a) The selection of what pieces of the library gets included in the core is done manually whereas it really should be automatic; b) The build doesn't fail if there are unresolved dependencies between the libraries and the core. I will fix these. (b) is IMO fundamental to avoid this error in the

Naturally, you tinker around with stuff long enough and you break it. I am running Samba 2.2.2 on a Corel linux box and am attempting to connect to a share on a windows XP system. At one point, this was working fine. Then I spent time trying to reconfigure my kernel so that I could attach a floppy tape drive and now I can connect with smbclient to the share, but I cannot with smbmount. I have

That doesn't seem possible with the public API or am I mistaking? On Wed, May 7, 2014 at 12:13 AM, Eric Christopher <echristo at gmail.com>wrote: > On Tue, May 6, 2014 at 8:09 PM, Isaiah Norton <isaiah.norton at gmail.com> > wrote: > > Hi, > > > > I am looking for a way to get unmangled subprogram names from a > > DWARFContext. The name I want is

When having a project that's partially bitcode and partially native code, should lld allow linking a native .o to a bitcode .o? specifically in my case, I've got an stdcall function in bitcode, called by native code, but it can't find the symbol (bitcode has it unmangled, native code with _ and @20)