similar to: help needed: How to get during compile time the base class of casted C++ object inside static_cast<> and dynamic_cast<> and the pointer of the casted object

I want to detect bad casts in C++ code by using the Clang compiler. The approach is similar to what Caver and TypeSan do but without using the compiler-rt. Caver and TypeSan: https://www.usenix.org/system/files/conference/usenixsecurity15/sec15-paper-lee.pdf https://nebelwelt.net/publications/files/16CCS2.pdf For example if I have the following C++ code snippet where I want to cast object b into

Hi Paul, It is the 4th time in two weeks that you repost the exact same two emails, that’s a bit high repost rate for the mailing-list, especially considering that you already got answers that you ignored previously: - http://lists.llvm.org/pipermail/llvm-dev/2016-December/108060.html - http://lists.llvm.org/pipermail/llvm-dev/2016-December/108051.html Adding an alternate email in case you

> On Dec 21, 2016, at 8:38 AM, Paul <paul at sec.in.tum.de> wrote: > > Hi Mehdi, > > thanks a lot for your email. Actually I was disappointed by the fact that I was not able to get a useful answer to my two questions. > As I observed that the questions move down along the list with time passing I decided to re-post them in the hope that the questions > will have a

I want to detect bad casts in C++ code by using the Clang compiler. The approach is similar to what Caver and TypeSan do but without using the compiler-rt. Caver and TypeSan: https://www.usenix.org/system/files/conference/usenixsecurity15/sec15-paper-lee.pdf https://nebelwelt.net/publications/files/16CCS2.pdf For example if I have the following C++ code snippet where I want to cast object b into

Hi Mehdi, thanks a lot for your email. Actually I was disappointed by the fact that I was not able to get a useful answer to my two questions. As I observed that the questions move down along the list with time passing I decided to re-post them in the hope that the questions will have a better visibility. Could you help me with the two questions? Finding an expert in this area would be of great

Hi all, We are advertising a position for a research assistant / research associate at the University of Cambridge Computer Lab, working with LLVM targeting the Loki (http://www.cl.cam.ac.uk/~rdm34/loki/) architecture. For full details please see http://www.jobs.cam.ac.uk/job/9756/, though the 'meat' of the advert is pasted below. The Loki project has been my main focus for a number of

<font face="Verdana,Arial,Helvetica,sans-serif" size="2"> <span><div>Hi,<br>There was a mention of optimizing away C++ dynamic_casts in LTO in this presentation: <a href="https://www.youtube.com/watch?v=Fd3afoM3UOE&t=1306" target="_blank">https://www.youtube.com/watch?v=Fd3afoM3UOE&t=1306</a><br>I

Hi Akos, you should send this to the clang mailing list instead. Ciao, Duncan. > I'm trying to convert our code base from GCC 4.0 to LLVM (on mac OS X), and ran > into a problem. In the past we used mach_override and the dynamic_cast source to > override the built-in dynamic_cast operator to detect shared library issues > (http://gcc.gnu.org/faq.html#dso). Basically we'd

LLVM has a relatively large number of proprietary replacements for standard C++ functions and classes. One of these is dyn_cast to replace dynamic_cast. The two calls appear to be semantically equivalent; the only difference that I can see is that dyn_cast reportedly works on classes that have no v-table [1]. Could someone please explain why I should use dyn_cast instead of dynamic_cast?

Hi all, I'm trying to convert our code base from GCC 4.0 to LLVM (on mac OS X), and ran into a problem. In the past we used mach_override and the dynamic_cast source to override the built-in dynamic_cast operator to detect shared library issues (http://gcc.gnu.org/faq.html#dso). Basically we'd assert at runtime when a duplicated RTTI is found, giving us a chance to backtrace the offending

Trevor Harmon <Trevor.W.Harmon at nasa.gov> writes: [snip] > Could someone > please explain why I should use dyn_cast instead of dynamic_cast? (I > thought all classes have v-tables...) Thanks, For reducing executable size, LLVM builds with RTTI disabled where possible.

On Nov 12, 2010, at 5:57 PM, Óscar Fuentes wrote: >> Could someone >> please explain why I should use dyn_cast instead of dynamic_cast? (I >> thought all classes have v-tables...) Thanks, > > For reducing executable size, LLVM builds with RTTI disabled where > possible. Right, but how does that relate to dyn_cast? I thought v-tables were present even when RTTI is not

Hello, Following statement from LLVM Programmer's Manual is not compiling. CallInst* callInst = dyn_cast<CallInst>(&*basic_block_iterator_1); The gcc version is : gcc (GCC) 4.0.2 20051125 (Red Hat 4.0.2-8) ============ Error message ============ llvm/include/llvm/Support/Casting.h: In function 'bool llvm::isa_impl(const From&) [with To = llvm::CallInst, From =

Hi, It's been a little while, but I'd like to include a paper that uses and extends LLVM for more precise and declarative dynamic taint-tracking: Compiler-instrumented, Dynamic Secret-Redaction of Legacy Processes for Attacker Deception Frederico Araujo, Kevin W. Hamlen *Proceedings of the 24th USENIX Security Symposium, August* 2015. Link:

Or use cut(): > Num <- c(2.2, 2.4, 3.5, 5, 7) > cut(Num, breaks=c(0,2,4,6), labels=c("Low","Medium","High")) [1] Medium Medium Medium High <NA> Levels: Low Medium High Bill Dunlap TIBCO Software wdunlap tibco.com On Mon, Apr 9, 2018 at 10:00 AM, Bert Gunter <bgunter.4567 at gmail.com> wrote: > Just cast it! > > ?factor > Bert

On Friday 18 December 2009 19:56, Chris Lattner wrote: > > +// -debug-buffer-size - This is a command line op0tion to set the > > size > > +// of the debug stream circular buffer. The value is the number of > > +// characters to save. > > +static cl::opt<unsigned> > > +DebugBufferSize("debug-buffer-size", > > +

On Dec 18, 2009, at 6:36 PM, David Greene wrote: >>> +// Signal handlers - dump debug output on termination. >>> +static void debug_user_sig_handler(void *Cookie) >>> +{ >>> + llvm::circular_raw_ostream *logout = >>> + dynamic_cast<llvm::circular_raw_ostream *>(&llvm::dbgs()); >> >> Please do not use dynamic_cast, we're

The bug number is 13619. Oh, apparently it crashes if you substitute "reinterpret_cast" with "static_cast" or "dynamic_cast" as well. > > Hey everyone, > > > > first of all I just wanted to say thanks :) I've been using libclang for > building my own C/C++ IDE and its great. I have, however discovered a bug > (which I already submitted

On Thu, Jul 10, 2008 at 02:10:18PM +0530, Mahadevan R wrote: I was just wondering if anyone had been able to look at Mahadevan's patch? It makes LLVM compile again on OpenBSD with gcc 3, and doesn't seem to cause any regressions. It would definitely make some of our lives easier if this was in SVN rather than having to be applied manually each time :) > The custom allocator-related

I ran into an LLVM/Clang crash when attempting to do the following: 1. Build Clang from the release/9.x branch source. 2. Use the Clang from (1) to build clangd on the release/9.x branch, with LLVM_ENABLE_MODULES=On. I wrote a script to reproduce the crash: https://gist.github.com/modocache/ac366ca9673b93bb21e75d3e72162608 At the above URL, you'll find a script `repro.sh` that reproduces