similar to: [LLVMdev] fix for typo in llvm-c/Core.h

Displaying 20 results from an estimated 1000 matches similar to: "[LLVMdev] fix for typo in llvm-c/Core.h"

2008 Apr 26
2
[LLVMdev] ParamAttr Patch - Alignment fix
Hi Gordon, Thanks a lot for the feedback. I can see I've been way to concentrated on how llvm is build, then on this particular patch. I've done the changes you have suggested and it's now a lot nicer and cleaner! Please do say, if there is anything else. Anders Johnsen On Saturday 26 April 2008 22:02:45 Gordon Henriksen wrote: > Hi Anders, > > Thanks for the patch.
2008 Apr 26
0
[LLVMdev] ParamAttr Patch - Alignment fix
Hi Anders, Thanks for the patch. I'd like you to incorporate some feedback before I apply it, though. > Index: include/llvm/Argument.h > =================================================================== > --- include/llvm/Argument.h (revision 50213) > +++ include/llvm/Argument.h (working copy) > @@ -60,7 +60,16 @@ > + > + /// setByValAttr - Set true to give the
2008 Apr 26
0
[LLVMdev] ParamAttr Patch - Alignment fix
On Apr 26, 2008, at 17:41, Anders Johnsen wrote: > Hi Gordon, > > Thanks a lot for the feedback. I can see I've been way to > concentrated on how > llvm is build, then on this particular patch. I've done the changes > you have > suggested and it's now a lot nicer and cleaner! > > Please do say, if there is anything else. Nice. Just a few small
2010 Apr 11
0
[LLVMdev] darwin dragon-egg build issues
On 04/10/2010 08:01 PM, Jack Howarth wrote: > > bash-3.2$ GCC=/sw/bin/gcc-4 CC=gcc-4 CXX=g++-4 CFLAGS=-I/sw/include CXXFLAGS=-I/sw/include LLVM_CONFIG=/sw/lib/llvm/bin/llvm-config make > g++-4 -c -I/sw/lib/llvm/include -D_DEBUG -D_GNU_SOURCE -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -MD -MP -DIN_GCC -DREVISION=\"100954M\"
2008 Apr 26
2
[LLVMdev] ParamAttr Patch - Alignment fix
On Sunday 27 April 2008 00:48:00 Gordon Henriksen wrote: > On Apr 26, 2008, at 17:41, Anders Johnsen wrote: > > Hi Gordon, > > > > Thanks a lot for the feedback. I can see I've been way to > > concentrated on how > > llvm is build, then on this particular patch. I've done the changes > > you have > > suggested and it's now a lot nicer and
2009 Oct 08
2
[LLVMdev] Some additions to the C bindings
On Tue, Oct 6, 2009 at 5:47 PM, Kenneth Uildriks <kennethuil at gmail.com> wrote: > On Tue, Oct 6, 2009 at 2:13 PM, Kenneth Uildriks <kennethuil at gmail.com> wrote: > > LLVMGetAttribute had a bug in it.  Here's the revised version of the patch Hi Kenneth! I wouldn't say that I'm the best reviewer, but I've been doing some work with the c bindings recently so
2012 Apr 25
2
[LLVMdev] Crash in JIT
Hello, [Using LLVM r155315, according to `svn log | head`] I am experimenting with programatically building and jitting functions in a module, and I seem to be coming across a crash in some generated code. Using the llvm-c interface I build up the module which dumps like this: ; ModuleID = 'MyModule' target datalayout = "i686-apple-darwin11" target triple =
2012 Apr 25
0
[LLVMdev] Crash in JIT
Hi David, I'm not certain, but to me the "LLVMSetTarget(module, "i686-apple-darwin11");" line looks suspicious. I'm not familiar with all the ins and outs of how target triples get handled, but it looks to me like that's requesting 32-bit code. I think that if you omit that line completely then the target will be inferred from the execution environment. My best
2009 Dec 29
1
[LLVMdev] LLVM{Add,Remove}FunctionAttr totally broken
The LLVMAddFunctionAttr and LLVMRemoveFunctionAttr are busted: they actually set the return value's attributes, not the function's attributes. There seems to be no C API for actually setting the function attributes. LLVMGetFunctionAttr, however, does correctly return the function attributes, not the return value's attributes. There is no C API for getting the return value
2009 Oct 11
3
[LLVMdev] Some additions to the C bindings
On Oct 6, 2009, at 5:47 PM, Kenneth Uildriks wrote: > On Tue, Oct 6, 2009 at 2:13 PM, Kenneth Uildriks > <kennethuil at gmail.com> wrote: >> My front-end is sync'd with the trunk now, and working well, but it >> required some additional functions exposed in the C bindings. I >> hereby submit them for review and approval for inclusion in the >> trunk.
2000 Feb 07
1
demo(nlm) error under R 0.99.0
I can't seem to get the demo(nlm) to run under R version 0.99.0 Anyone know a solution? > fgh <- function(x) { gr <- function(x1, x2) { c(-400 * x1 * (x2 - x1 * x1) - 2 * (1 - x1), 200 * (x2 - x1 * x1)) } h <- function(x1, x2) { a11 <- 2 - 400 * (x2 - x1 * x1) + 800 * x1 * x1 a21 <- -400 * .... [TRUNCATED] > nlm(fgh,
2000 Feb 15
1
R installation
I've decided to install in R in a directory other than /usr/local, but I'm having difficulty in setting the correct paths, i.e. PATH or path. I've set my R_HOME, and sure enough there's a bin and lib directory there but R just won't execute (something like GUI 'X11' is not supported. However when R is installed in /usr/local then everything is OK...Any help or comments
2020 Apr 15
2
question on the signature of malloc
Hi all, consider the following function from Core.cpp in LLVM 9.0.0: LLVMValueRef LLVMBuildMalloc(LLVMBuilderRef B, LLVMTypeRef Ty, const char *Name) { Type* ITy = Type::getInt32Ty(unwrap(B)->GetInsertBlock()->getContext()); Constant* AllocSize = ConstantExpr::getSizeOf(unwrap(Ty)); AllocSize = ConstantExpr::getTruncOrBitCast(AllocSize, ITy);
2012 Oct 18
2
[LLVMdev] [RFC] LLVM C-API Change
I recently reimplemented the Attributes class. It now hides the data representation inside of an opaque class. In the near future, we will be extending this class to encompass many other attributes. The changes pose one problem, however. The C-API still uses the old data representation for passing along the Attributes class. In particular, these two functions: LLVMAttribute
2002 Oct 10
1
make check when installing R-1.6.0
This is the result of my make check, could anyone help me out on this one? Formats: text example running code in 'base-Ex.R' ...*** Error code 1 make: Fatal error: Command failed for target `base-Ex.Rout' Current working directory /apps/R/R-1.6.0/tests/Examples *** Error code 1 make: Fatal error: Command failed for target `test-Examples-Base' Current working directory
2005 Nov 16
1
PPC package-ppc.read.raw.nobatch (PR#8316)
Full_Name: Martin O'Gorman Version: OS: Submission from: (NULL) (84.176.63.149) I have been looking at the PPC package and have a question. As the input data is comma separated, shouldn?t the command to read in the raw (no batch) mass spec data indicate that sep=?,? (marked below) ? Otherwise, the data read in is the pair of values (m/z,intensity). It is not obvious why that should be.
2010 Apr 11
7
[LLVMdev] darwin dragon-egg build issues
On Sat, Apr 10, 2010 at 01:52:18PM +0200, Duncan Sands wrote: > Hi Jack, > > > Is anyone building dragon-egg on darwin? > > Anton built it once. There were some problems with dynamic libraries: gcc's > plugin support requires the use of dynamic libraries, and the configure logic > it uses thinks that darwin does not support dynamic libraries! So it is >
2008 Apr 24
2
[LLVMdev] ParamAttr Patch - Alignment fix
Hi.. Updated so you now set alignment through LLVMInstrSetAlignment. Anders Johnsen -------------- next part -------------- A non-text attachment was scrubbed... Name: ParamAttr.patch Type: text/x-diff Size: 7420 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20080424/cb72b4bb/attachment.patch>
2010 May 27
2
[LLVMdev] Manipulating basic blocks with the C bindings
I'm writing a frontend with the LLVM C bindings for a language that has a goto statement, similar to C's. I'm having some trouble figuring out what to do for the case where the label is declared after the goto, like this: goto label; ... label: ... When I generate the code for the goto, I'd like to create a basic block that's not inserted anywhere in particular and then put
2019 Apr 11
2
128 bit float constant
Hi Tim, Thanks for the hint. I tried the following, (it's a C interface since that's what I need it for) where a and b are the top and bottom halves of the 128 bit value, LLVMValueRef TestConst(LLVMContextRef C, uint64_t a, uint64_t b) { Type *ty = Type::getFP128Ty(*unwrap(C)); ArrayRef<uint64_t> ar[2] = {a,b}; APInt ai(128,*ar); APFloat quad(APFloat::IEEEquad(), ai);