similar to: [LLVMdev] [PATCH] Add support for coldcc to clang

On 23 Feb 2013, at 00:26, John McCall <rjmccall at apple.com> wrote: > On Feb 20, 2013, at 7:52 PM, John McCall <rjmccall at apple.com> wrote: >> On Feb 20, 2013, at 7:49 PM, Peter Collingbourne <peter at pcc.me.uk> wrote: >>> On Wed, Feb 20, 2013 at 06:30:53PM -0800, John McCall wrote: >>>> On Feb 20, 2013, at 6:24 PM, Richard Smith <richard at

On Wed, 7 Nov 2007, Nicolas Geoffray wrote: > Thanks BGB, but at this point I can handle it ;-). The problem is not > how in theory (patch the caller), but how in the LLVM code generation > process. There are three steps for that: > > 1) How to represent the stub in the IR? An intrinsic? An external field > with a ghost linkage? Probably an intrinsic. The trick is making it

It seems a little backwards to me to check the landingpad's type as the first check, since the personality dictates the landingpad's type. That said, yes I see how #4 is expedient in allowing personalities using the two main types to lump themselves into EHPersonality::Unknown. As for supporting selector and exception pointer extraction for landingpad of token type, I think you'll

BGB wrote: > > for x86: > I presume LLVM supports inline assembler, and also uses the traditional > frame pointer-based stack layout, but I don't know the details (people who > know LLVM could probably be more helpful here). > > ok, maybe here is an option: > after getting the value (in the created stub), execute a chunk of inline > assembler to modify the caller

When zig updated to llvm 5 we started hitting this assertion: zig: /home/andy/downloads/llvm-project/llvm/include/llvm/Support/Casting.h:106: static bool llvm::isa_impl_cl<To, const From*>::doit(const From*) [with To = llvm::Instruction; From = llvm::Value]: Assertion `Val && "isa<> used on a null pointer"' failed. I wonder if however this was caused by an

Can you please open a bug on bugzilla and attach the ir testcase? Your fix doesn't look right (just hiding the assertion failure) On Sep 17, 2017 10:45 AM, "Andrew Kelley via llvm-dev" < llvm-dev at lists.llvm.org> wrote: > What do you think about this patch? > > --- a/llvm/lib/Transforms/Scalar/NewGVN.cpp > +++ b/llvm/lib/Transforms/Scalar/NewGVN.cpp > @@

Hi all, I'm interested in fixing PR14481 (http://llvm.org/PR14481), regarding teaching LLVM that coldcc functions do not clobber any registers. As a brief motivation why: this can have a significant performance benefits and is very useful for instrumenting code with many calls that are executed only very rarely. Ubsan's runtime calls are a good example of this. Attached is my attempt

On Feb 7, 2012, at 4:04 PM, Kostya Serebryany wrote: > On Tue, Feb 7, 2012 at 3:46 PM, John McCall <rjmccall at apple.com> wrote: > On Feb 7, 2012, at 2:07 PM, Kostya Serebryany wrote: > > Slightly formatted/commented patch. > > WDYT? > > This seems to work fine, except that reading a field from a const > AttrConst is not a constant expression in C++03, so the

> I dont have a concrete design right now and I am happy to take any other ideas Three ideas come to mind, none of which are perfect: 1) I'm tempted to say that now that we have token type, landingpad should generally produce a token, the pointer should be extracted with the @llvm.eh.exceptionpointer intrinsic instead of an extractvalue, and the selector should likewise be extracted with

On Tue, Feb 7, 2012 at 4:55 PM, John McCall <rjmccall at apple.com> wrote: > On Feb 7, 2012, at 4:04 PM, Kostya Serebryany wrote: > > On Tue, Feb 7, 2012 at 3:46 PM, John McCall <rjmccall at apple.com> wrote: > >> On Feb 7, 2012, at 2:07 PM, Kostya Serebryany wrote: >> > Slightly formatted/commented patch. >> > WDYT? >> >> This seems to

So, 90% of the time I've seen this, it was memory corruption, usually use after free. I know I fixed one after 5.0 branched. You should compile with address sanitizer enabled, and I suspect you will find the issue quicky. If not, we really need ir that reproduces it. On Sun, Sep 17, 2017, 12:27 PM Andrew Kelley via llvm-dev < llvm-dev at lists.llvm.org> wrote: > I think I forgot to

On Oct 3, 2011, at 4:42 AM, Somorjai, Akos wrote: > I'm trying to use this warning to check the vtable problem. Here's an example > > In mem.hpp > > class > AA { > // Construction / destruction: > protected: > AA (); > AA (const AA&); // Disabled > public: > virtual ~AA (); > }; > > In mem.cpp > > #include "mem.hpp" >

Apple clang version 3.0 (tags/Apple/clang-211.9) (based on LLVM 3.0svn) Target: x86_64-apple-darwin10.8.0 It's part of the Xcode 4.2b7 package. Shall I try to compile it on my own? Thanks, Akos From: John McCall <rjmccall at apple.com<mailto:rjmccall at apple.com>> Date: Mon, 3 Oct 2011 10:19:04 -0700 To: Ákos Somorjai <asomorjai at graphisoft.com<mailto:asomorjai at

On Feb 7, 2012, at 4:56 PM, Kostya Serebryany wrote: > > > On Tue, Feb 7, 2012 at 4:55 PM, John McCall <rjmccall at apple.com> wrote: > On Feb 7, 2012, at 4:04 PM, Kostya Serebryany wrote: >> On Tue, Feb 7, 2012 at 3:46 PM, John McCall <rjmccall at apple.com> wrote: >> On Feb 7, 2012, at 2:07 PM, Kostya Serebryany wrote: >> > Slightly

On 01/08/2010 02:10 PM, John McCall wrote: > 'llc' is an IR-to-assembly compiler; at -O3 it does some pretty neat > machine-code and object-file optimizations, but it does not apply > high-level optimizations like CSE or inlining. 'opt' is the tool > which does IR-to-IR optimization. A vital clue, but I'm still not getting it: --- gemini:~/Projects/Nil/nil(0)$

On 24 August 2010 00:19, John McCall <rjmccall at apple.com> wrote: > Note that llvm-diff is meant solely as a tool for debugging IR;  pretty much all > details of the output, from formatting to actual information, is subject to change. Hi John, This is fine, I'll not use it on any production system nor rely on its output for anything, it's also mainly for IR debugging. I

On 28 February 2011 18:00, John McCall <rjmccall at apple.com> wrote: > I have no objections to any of that. Thanks! Will try something this week... Btw, I want to use a graph data structure (like Boost's) to put the metadata in and be able to assert A == B and recurse the graph to make sure everything is equals in A to B, but avoiding re-reading cycles (recursive types).

John McCall <rjmccall at apple.com> writes: >> git branch --contains <sha1>, on the other hand, will tell you. > > Of course, this doesn't actually help if you've cherry-picked commits > over to your branch (e.g. because it's a release branch). How is that different from SVN? If revision 1234 fixes a bug is some branch, and the last revision in your trunk

On Oct 19, 2010, at 11:40 AM, Roland Scheidegger wrote: > So I saw that the code is doing lots of register spilling/reloading. Now > I understand that due to calling conventions, there's not really a way > to avoid this - I tried using coldcc but apparently the backend doesn't > implement it and hence this is ignored. Yes, unfortunately the list of call-clobbered registers is

Thanks for giving it a look! On 19.10.2010 23:21, Jakob Stoklund Olesen wrote: > On Oct 19, 2010, at 11:40 AM, Roland Scheidegger wrote: > >> So I saw that the code is doing lots of register >> spilling/reloading. Now I understand that due to calling >> conventions, there's not really a way to avoid this - I tried using >> coldcc but apparently the backend