similar to: [LLVMdev] Parsing C++ headers with Clang bindings for Python

Answering my own question: On Fri, Oct 18, 2013 at 8:51 PM, Elliott Slaughter < elliottslaughter at gmail.com> wrote: > I'd like to parse a C++ header file (say, math.h) with the Clang bindings > for Python. (Yes, I know math.h is technically a C header, but for my > purposes I want to pretend that it is C++.) For some reason, Clang is able > to parse the file as C, but not

Hi Elliott, On Oct 18, 2013, at 9:29 PM, Elliott Slaughter <elliottslaughter at gmail.com> wrote: > Answering my own question: > > On Fri, Oct 18, 2013 at 8:51 PM, Elliott Slaughter <elliottslaughter at gmail.com> wrote: > I'd like to parse a C++ header file (say, math.h) with the Clang bindings for Python. (Yes, I know math.h is technically a C header, but for my

Hello, I'm trying to use the python libclang bindings to write a C++ style-checker, and I'd like to detect all the typedefs to recommend switching to using. I'm using libclang 3.8, with the python bindings provided with it. When I parse a file with index = clang.cindex.Index.create() tu = index.parse(f, ['-x', 'c++', '-std=c++11', '-fsyntax-only',

Hi, I am parsing a C++ file using cindex.py and want to get the template parameters to a specific node. However, the tree seems to be different depending on if the template parameter is a struct/class or a simple type such as int or float. In the first case the template type is appended as a child to the VAR_DECL node (the TYPE_REF node seen in the example below), but this is not the case with

Hi Rich, I find it more readable (and safer to review) to avoid lines longer than 80 columns. When reviewing changes that wrap, I've noticed that it is harder to spot certain types of mistakes in the wrapped portion of a long line. >From 930118b380b35bb33e7719b0eb2ab6b31fa2d7e4 Mon Sep 17 00:00:00 2001 From: Jim Meyering <meyering at redhat.com> Date: Wed, 13 Apr 2011 16:08:57

On Mon, 11 Sep 2006, [UTF-8] Rafael Esp?ndola wrote: > I am trying to build llvm-gcc4 on a amd64. I had to add the attached > patch to get the build system to select the correct library. Now the Applied. > build fails while compiling a code that has __builtin_va_copy. The > attached test.i fails with: > > cc1: ../../trunk/gcc/llvm-convert.cpp:443: llvm::Value* >

--- hivex/hivexsh.pod | 9 ++++++++- 1 files changed, 8 insertions(+), 1 deletions(-) diff --git a/hivex/hivexsh.pod b/hivex/hivexsh.pod index 277e3ae..9336798 100644 --- a/hivex/hivexsh.pod +++ b/hivex/hivexsh.pod @@ -100,7 +100,14 @@ or even: Path elements (node names) are matched case insensitively, and characters like space, C<*>, and C<?> have I<no> special

This is, hopefully, a full fix for handling of li-records. See: https://bugzilla.redhat.com/show_bug.cgi?id=717583 https://bugzilla.redhat.com/show_bug.cgi?id=987463 Rich.

I am trying to build llvm-gcc4 on a amd64. I had to add the attached patch to get the build system to select the correct library. Now the build fails while compiling a code that has __builtin_va_copy. The attached test.i fails with: cc1: ../../trunk/gcc/llvm-convert.cpp:443: llvm::Value* TreeToLLVM::Emit(tree_node*, llvm::Value*): Assertion `(isAggregateType(((exp)->common.type)) == (DestLoc

On Dec 4, 2009, at 12:40 PM, Duncan Sands wrote: > Hi Bill, > >> Here's what I get with TOT compiling with -Os. The orig.ll is what >> I get before r72619. Notice that orig.ll has only one function in >> it. Both the one you sent and duncan.ll have more than one >> function. It's not the fact that more than one function is showing >> up, but

Oh noes! What do I do? Just installed RoR and SQLite3 yesterday, watched a screencast that said the db_schema_dump will slaughter my enemies and make my poop smell like rainbows. Now I get rake telling me that it doesn''t know how to. Any help? -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are

I tried both hivex-1.2.5 and hivex-1.2.7, same result. The same software hive can be loaded using Windows regedit tool, and had no problem to access the "Classes" key. The other keys under Software (like Microsoft, Wow6432Node, etc.) are OK. Here is the hivexsh output with HIVEX_DEBUG=1 enabled:

On Fri, 1 Sep 2006, Michael McCracken wrote: > Here's what works now, and I have a separate test case for each of these: > > statement functions > intrinsic functions (print, cos, etc) > loops, goto statments > scalarized array operations > function calls with *no arguments* > simple common blocks Great! > Function calls with more than one argument don't work.

[The bug which this fixes is: https://bugzilla.redhat.com/show_bug.cgi?id=717583 ] ----- Forwarded message from Peter Fokker <peter at berestijn.nl> ----- Date: Thu, 8 Mar 2012 11:37:06 +0100 (CET) From: Peter Fokker <peter at berestijn.nl> To: rjones at redhat.com Cc: Peter Fokker <peter at berestijn.nl> Subject: hivex: patch for read support of "li"-records from

For Whom the Gaza Bell Tolls -- Part 1 By Edmund Connelly for The Occidental Observer January 16, 2008 ?The Israelis can kill whomever they want whenever they want.? --Paul Craig Roberts I sometimes think that it?s pointless for Americans to talk much about recent events in Gaza because we know how it will play out ? America will do absolutely nothing to interfere with the ongoing massacre.

The NIST F77 test suite doesn't seem to be compatible with gfortran at all, so I had to work from my own sample codes, and generate test cases from them. Here's what works now, and I have a separate test case for each of these: statement functions intrinsic functions (print, cos, etc) loops, goto statments scalarized array operations function calls with *no arguments* simple common

I want to simulate vi(vim) like operations in ListCtrl or TreeCtrl, that is, for example, when user pressed a ''j'' on keyboard,the selected item change into the next one item, just like user press a Wx::K_DOWN(arrow key down on keyboard) . but not jump to some item started with a "J" charater. evt_tree_key_down(TreeTest_Ctrl) { | e | on_tree_key_down(e) } ... def

Hi Chris, > I think this change is fine and should go into the normal apple GCC as > well. Setting TREE_READONLY means that it can go into the "constant" > section of the executable, go in ROM, etc. This is the same as the > llvm constant bit on globals. for this I think it has to be static as well as readonly. Ciao, Duncan.

I did mark it as TREE_CONSTANT. Is that enough? -bw On Jan 5, 2009, at 2:03 AM, Duncan Sands <baldrick at free.fr> wrote: > Hi Chris, > >> I think this change is fine and should go into the normal apple GCC >> as >> well. Setting TREE_READONLY means that it can go into the "constant" >> section of the executable, go in ROM, etc. This is the same

For Whom the Gaza Bell Tolls -- Part 1 By Edmund Connelly for The Occidental Observer January 16, 2008 ?The Israelis can kill whomever they want whenever they want.? --Paul Craig Roberts I sometimes think that it?s pointless for Americans to talk much about recent events in Gaza because we know how it will play out ? America will do absolutely nothing to interfere with the ongoing massacre.