search for: fpconstants

On Thu, Nov 26, 2009 at 2:31 PM, Nick Lewycky <nicholas at mxc.ca> wrote: > Hi Devang, > > Before I get to the contents of this particular patch, I have a higher-level > design question. Why is metadata stored off the LLVMContext? Why do we have FPConstants, IntConstants etc.. in LLVMContext ? :) > That seems like > the wrong place to me, this data is all specific to the particular module. > Specifically, a single MDNode may not cross modules, and if a module is > destroyed we should eliminate all the metadata that came with it. Metadata...

Hi Devang, Before I get to the contents of this particular patch, I have a higher-level design question. Why is metadata stored off the LLVMContext? That seems like the wrong place to me, this data is all specific to the particular module. Specifically, a single MDNode may not cross modules, and if a module is destroyed we should eliminate all the metadata that came with it. So, why

...On Thu, Nov 26, 2009 at 2:31 PM, Nick Lewycky <nicholas at mxc.ca> wrote: > > Hi Devang, > > > > Before I get to the contents of this particular patch, I have a > higher-level > > design question. Why is metadata stored off the LLVMContext? > > Why do we have FPConstants, IntConstants etc.. in LLVMContext ? :) > So you can build up Constants and Instructions before inserting them where they'll be used. I suppose that sounds reasonable to do for metadata too. > That seems like > > the wrong place to me, this data is all specific to the particular...

Hi All, Now, in llvm trunk we support custom metadata, which can be attached with llvm instructions. One of the user is "debugging information". This user is special (not just because it is in llvm svn tree:) because whenever debug info is available, it is likely that corresponding metadata is attached with almost all instructions. In other words, usually it is all or nothing. This

Ok, here is the patch again... I also included fixes for the bits that originally gave my mailer fits... Two votes for orange, so I went with orange... Doing diffs in .: --- ./lib/AsmParser/LLLexer.cpp.~1~ 2007-12-14 22:09:06.000000000 -0800 +++ ./lib/AsmParser/LLLexer.cpp 2007-12-15 13:02:47.000000000 -0800 @@ -54,7 +54,7 @@ static uint64_t HexIntToVal(const char * Result +=

All, Here is the second revision of the proposal for a complex type in LLVM. It clarifies a few things that came up during discussion and adds additional operations for complex types. -David Proposal to Support Complex Operations in LLVM ---------------------------------------------- Revision History v1 - Initial proposal [1] v2 - This proposal - Added complex of

Ahead of the Wednesday’s roundtable at the developers’ conference, here is version three of the proposal for first-class complex types in LLVM. I was not able to add Krzysztof Parzyszek’s suggestion of a “cunzip” intrinsic returning two vectors as I could not find examples of intrinsics that return two values at the IR level. The Hexagon intrinsics declared to return two values do not actually

Hi, There’s growing interest among our users to make better use of dedicated hardware instructions for complex math and I would like to re-start the discussion on the topic. Given that this original thread was started a while ago apologies if I missed anything already discussed earlier on the list or the round-table. The original mail is quoted below. In particular, I’m interested in the AArch64