search for: sloc

...------------------------------------------------------------- ========================================================= Command line: clang -c -g -gmacro -O0 -DM3=Value3 -include myfile2.h mainfile.c AST ========================================================= MacroDecl 0xd6c5c0 <<invalid sloc>> <invalid sloc> __llvm__ defined MacroDecl 0xd6c618 <<invalid sloc>> <invalid sloc> __clang__ defined ... <More compiler macros> ... MacroDecl 0x11c01b0 <<invalid sloc>> <invalid sloc> M3 defined FileIncludeDecl 0x11c0208 <mainfile.c:1:1&g...

...er reported a problem with the current llvm 3.9 trunk version (I tested with r261262). Our problem is that the AST contains some declarations which were not there before. Using "clang -Xclang -ast-dump” on a c++ file, I get the following result: TranslationUnitDecl 0x8e41ab0 <<invalid sloc>> <invalid sloc> |-TypedefDecl 0x8e41fe8 <<invalid sloc>> <invalid sloc> implicit __int128_t '__int128' | `-BuiltinType 0x8e41d00 '__int128' |-TypedefDecl 0x8e42048 <<invalid sloc>> <invalid sloc> implicit __uint128_t 'unsigned __i...

...------------------------------------------------------------- ========================================================= Command line: clang -c -g -gmacro -O0 -DM3=Value3 -include myfile2.h mainfile.c AST ========================================================= MacroDecl 0xd6c5c0 <<invalid sloc>> <invalid sloc> __llvm__ defined MacroDecl 0xd6c618 <<invalid sloc>> <invalid sloc> __clang__ defined … <More compiler macros> … MacroDecl 0x11c01b0 <<invalid sloc>> <invalid sloc> M3 defined FileIncludeDecl 0x11c0208 <mainfile.c:1:1> c...

...------------------------------------------------------------- ========================================================= Command line: clang -c -g -gmacro -O0 -DM3=Value3 -include myfile2.h mainfile.c AST ========================================================= MacroDecl 0xd6c5c0 <<invalid sloc>> <invalid sloc> __llvm__ defined MacroDecl 0xd6c618 <<invalid sloc>> <invalid sloc> __clang__ defined … <More compiler macros> … MacroDecl 0x11c01b0 <<invalid sloc>> <invalid sloc> M3 defined FileIncludeDecl 0x11c0208 <mainfile.c:1:1> c...

...------------------------------------------------------------- ========================================================= Command line: clang -c -g -gmacro -O0 -DM3=Value3 -include myfile2.h mainfile.c AST ========================================================= MacroDecl 0xd6c5c0 <<invalid sloc>> <invalid sloc> __llvm__ defined MacroDecl 0xd6c618 <<invalid sloc>> <invalid sloc> __clang__ defined … <More compiler macros> … MacroDecl 0x11c01b0 <<invalid sloc>> <invalid sloc> M3 defined FileIncludeDecl 0x11c0208 <mainfile.c:1:1> c...

...========================================== > > > > Command line: > > clang -c -g -gmacro -O0 -DM3=Value3 -include myfile2.h mainfile.c > > > > > > AST > > ========================================================= > > MacroDecl 0xd6c5c0 <<invalid sloc>> <invalid sloc> __llvm__ defined > > MacroDecl 0xd6c618 <<invalid sloc>> <invalid sloc> __clang__ defined > > > > … <More compiler macros> … > > > > MacroDecl 0x11c01b0 <<invalid sloc>> <invalid sloc> M3 defined &g...

...;> >> Command line: >> >> clang -c -g -gmacro -O0 -DM3=Value3 -include myfile2.h mainfile.c >> >> >> >> >> >> AST >> >> ========================================================= >> >> MacroDecl 0xd6c5c0 <<invalid sloc>> <invalid sloc> __llvm__ defined >> >> MacroDecl 0xd6c618 <<invalid sloc>> <invalid sloc> __clang__ defined >> >> >> >> … <More compiler macros> … >> >> >> >> MacroDecl 0x11c01b0 <<invalid sloc&gt...

...t;> clang -c -g -gmacro -O0 -DM3=Value3 -include myfile2.h mainfile.c >>> >>> >>> >>> >>> >>> AST >>> >>> ========================================================= >>> >>> MacroDecl 0xd6c5c0 <<invalid sloc>> <invalid sloc> __llvm__ defined >>> >>> MacroDecl 0xd6c618 <<invalid sloc>> <invalid sloc> __clang__ defined >>> >>> >>> >>> … <More compiler macros> … >>> >>> >>> >>> Mac...

...st as to how to extract information from cursors- when I AST dump my class I can see the information I need is all there (see the last line): |-ObjCMethodDecl 0x112790f90 <line:32:1, line:34:1> - testAddConcreteDataModel: 'void' | |-ImplicitParamDecl 0x112791960 <<invalid sloc>> self 'DFDataModelContainer *const __strong' | |-ImplicitParamDecl 0x1127919c0 <<invalid sloc>> _cmd 'SEL':'SEL *' | |-ParmVarDecl 0x112791040 <line:32:35, col:55> helpmeh 'DFDemoDataModelOne *__strong' | `-CompoundStmt 0x112791bf0...

On Thu, Jun 09, 2011 at 08:47:26PM -0400, Jack Howarth wrote: > Duncan, > Here are the complete benchmarks rerun against gcc 4.5.4 built with... > > Using built-in specs. > COLLECT_GCC=gfortran-fsf-4.5 > COLLECT_LTO_WRAPPER=/sw/lib/gcc4.5/libexec/gcc/x86_64-apple-darwin11.0.0/4.5.4/lto-wrapper > Target: x86_64-apple-darwin11.0.0 > Configured with:

Hello everyone, We are in the process of formalizing the governance model of the GlusterFS project. Historically, the governance of the project has been loosely structured. This is an invitation to all of you to participate in this discussion and provide your feedback and suggestions on how we should evolve a formal model. Feedback from this thread will be considered to the extent possible in

...ting: <http://www.microsoft.com/technet/community/newsgroups/dgbrowser/en-us/def ault.mspx?query=microsoft.public.windows.server.scripting&dg=&cat=en-us-te chnet-appcenter&lang=en&cr=US&pt=&catlist=328BAFD2-1A81-4558-B1DE-B6EB49F3 1B7E&dglist=&ptlist=&exp=&sloc=en-us> * Get the latest scoop on Monad on the blogs by Monad MVPs and team members. Here's a list of some of the ones out there: Monad Team Blog: <http://blogs.msdn.com/monad> Arul Kumaravel's Blog: <http://blogs.msdn.com/arulk> Keith Hil...

...now about the new exception types generated. This changeset has been passing xm-test for the past couple weeks so I''m rather confident that it doesn''t introduce any major regressions. One thing to notice (from the attached diffstat output) is that there is a net reduction in SLOCs even though no functionality was removed. This is because XendClient was greatly simplified by using XML-RPC. b/tools/python/xen/util/xmlrpclib2.py | 109 +++++++ b/tools/python/xen/xend/server/XMLRPCServer.py | 97 ++++++ tools/python/xen/xend/XendClient.py | 369 ++...

Will there be a german translation of lartc? ________________________________________________________________________ Sebastian Spies <sspies@sloc.de> <sspies@rbg.informatik.tu-darmstadt.de> 6bone-PERSON-HDL: SP24-6BONE feel free to send me encrypted mails (GPG): 0x4AE404F3 available from: subkey.pgp.net

...leaf 30: rate 64Kbit cell 8b (isolated) prio no-transmit/8 weight 819bps allot 1500b level 0 ewma 5 avpkt 1000b maxidle 45584us Sent 68718965 bytes 47597 pkts (dropped 0, overlimits 0) borrowed 47589 overactions 0 avgidle -5.67627e+06 undertime 5.57184e +06 Greets Sebastian Spies <sspies@sloc.de>

I was looking for an R-package that would reduce matrices to row-echelon form, but Google was not my friend; any leads? If not, I wonder if the problem could be expressed in terms of constraint satisfaction...

Cross-posted to the blog (at http://lylejohnson.name/blog/2010/08/04/moving-on/): When Jamis Buck wrote last year about ceasing development on Capistrano, his post really struck a chord with me. If this post reminds you of that one, it''s because I re-read it before sitting down to compose this one. It was the next best thing to having Jamis on hand to give me a pep talk before I had to

...unning on > ppc/os x? Is it just a matter of taking some tree/rtl form stuff and > emitting ppc code instead of x86 code? Basically a new code generator would need to be written. The current X86 code generator (ignoring the experimental instruction selectors) is about 8-9000 LOC (about 4800 SLOC, as reported by sloccount) in the lib/Target/X86 directory, which should give you an idea of how much work it currently is to implement a code generator. The X86 backend also has a bunch of little optimizations in it, so a simple code generator would probably be a lot less code. We are slowly wor...

So Reid came across a case where the current strategy (dropping locations when they move across basic blocks) proves to be at odds with another precept we have: inlinable calls must have locations, so that if/when they are inlined the location can be accurately described (due to the nature of our IR representation of inlining, a location must be given for the call site so that the DIEs for the

> > There are two problems with this: 1) there is no JIT for PPC yet, so > LLVM will use the interpreter (which is intolerably slow and has other > issues). 2) Spec compiles the executables in one place and them moves > them to another, but it only copies the shell script and not the > bytecode file, so you get that error message. > > The normal solution to this problem