similar to: [LLVMdev] ParamAttr patch

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

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.

On Sunday 27 April 2008 01:33:31 Gordon Henriksen wrote: > On Apr 26, 2008, at 19:09, Anders Johnsen wrote: > > On Sunday 27 April 2008 00:48:00 Gordon Henriksen wrote: > >> On Apr 26, 2008, at 17:41, Anders Johnsen wrote: > >>> +void LLVMSetInstrParamAlignment(LLVMValueRef Instr, unsigned index, > >>> unsigned align) { > >>> + CallSite Call =

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

On Apr 26, 2008, at 19:09, Anders Johnsen wrote: > On Sunday 27 April 2008 00:48:00 Gordon Henriksen wrote: > >> On Apr 26, 2008, at 17:41, Anders Johnsen wrote: >> >> >>> +void LLVMSetInstrParamAlignment(LLVMValueRef Instr, unsigned index, >>> unsigned align) { >>> + CallSite Call = CallSite(unwrap<Instruction>(Instr)); >>> +

Hi again, I found some errors straight after Mailing it - sorry about that! Anders Johnsen -------------- next part -------------- A non-text attachment was scrubbed... Name: ParamAttr.patch Type: text/x-diff Size: 7207 bytes Desc: not available URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20080424/ec006fbb/attachment.patch>

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>

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

On Apr 28, 2008, at 11:07, Anders Johnsen wrote: > Should hopefully be the last one :) Looks great. Applied r50360: http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20080428/061696.html Thansk Anders! — Gordon

I tried the version you used, too. the resulting executable was still broken. I guess the reason is due to fastcall on function pointers, which Clang does not recognize. Consider the following snippet. #include <stdio.h> void __attribute__((fastcall)) f(int i) { printf("%d\n", i); } typedef void (*__attribute__((fastcall)) f_t)(int i); //typedef void

Hello, Anders > Small patch to fix enum values - have been changed while patch have > been updated. Applied, thanks -- With best regards, Anton Korobeynikov. Faculty of Mathematics & Mechanics, Saint Petersburg State University.

On Tuesday 29 April 2008 14:52:49 David J.A. Koogler wrote: > Everyone, > > I would like to build the LLVM toolchain and the GCC front end as > statically linked executables, but I do not see a configure > option to set this. A quick check of the FAQ and build documents > comes up empty. Is there a linker switch setting or environment > variable for the Makefile? > >

Anders Johnsen wrote: > I think there is a > > ./configure --enable-static > > switch - have you tried that? Yes, but that only seems to force building static libraries, not statically linked tools. Kenneth Boyd wrote: > The --disable-shared option to configure should work (like it does for > most configure-scripted projects). No, I tried that and still got

I think you need to call "llvm::Function::deleteBody() first" On Tue, Mar 23, 2010 at 15:49, Reid Kleckner <rnk at mit.edu> wrote: > On Tue, Mar 23, 2010 at 7:04 AM, Gabi <bugspynet at gmail.com> wrote: >> Hi >> I get huge memory leaks using LLVM IRBuilder (trunk version) >> >> Basically I recreate a function over and over again, and pretty sure

What version of clang are you using? It could be a regression between head and the version I used. (some days old) - Anders On Fri, Apr 3, 2009 at 6:37 PM, Xi Wang <xi.wang at gmail.com> wrote: > On Fri, Apr 3, 2009 at 12:07 PM, Chris Lattner <clattner at apple.com> wrote: >> It is impossible to tell with this amount of detail.  Does it work >> correctly if you build

Hi, I downloaded the file here, and used the same commands. This is what I got: Number of tests : 9537 5371 Tests skipped : 4166 ( 43.7%) -------- Tests warned : 0 ( 0.0%) ( 0.0%) Tests failed : 7 ( 0.1%) ( 0.1%) Expected fail : 3 ( 0.0%) ( 0.1%) Tests passed : 5361 ( 56.2%) ( 99.8%) I'm on linux x86_64 with clang version: "clang version 1.0

Throwing this C++ code at the online demo: struct S { double d; unsigned u; }; S foo() { return S(); } produces this LLVM C++ API code: (...) PAListPtr func__Z3foov_PAL = 0; { SmallVector<ParamAttrsWithIndex, 4> Attrs; ParamAttrsWithIndex PAWI; PAWI.index = 0; PAWI.attrs = 0 | ParamAttr::NoUnwind; Attrs.push_back(PAWI); PAWI.index = 1; PAWI.attrs = 0 |

On Fri, Apr 3, 2009 at 12:07 PM, Chris Lattner <clattner at apple.com> wrote: > It is impossible to tell with this amount of detail.  Does it work > correctly if you build with -O0 ? Yes, with -O0 the resulting executable looks fine. --enable-debug actually sets -O0 (otherwise -O2). Clang can build/test php 5.2.9 with either -O0 or -O2, but not for php 5.3RC0 with -O2. I further

No. The demo is using 2.3. I update it personally after every release. Yes, it incorrectly says llvm2cpp, but its really using llc. I'll change this when I update it. The ReleaseNotes in TOT are for 2.4. -Tanya On Oct 17, 2008, at 10:52 PM, Óscar Fuentes wrote: > Throwing this C++ code at the online demo: > > struct S { > double d; > unsigned u; > }; > > S

pypy-0.7.0: first PyPy-generated Python Implementations ============================================================== What was once just an idea between a few people discussing on some nested mailing list thread and in a pub became reality ... the PyPy development team is happy to announce its first public release of a fully translatable self contained Python implementation. The 0.7 release