similar to: Status of docs/BitCodeFormat.rst?

I think it just changed formats which prompted a change in ID -- the code now uses TYPE_BLOCK_ID_NEW (= 17). I haven’t looked deeply to see how different it is. Ismail > On Oct 13, 2016, at 2:02 PM, Mehdi Amini <mehdi.amini at apple.com> wrote: > > >> On Oct 13, 2016, at 10:24 AM, Ismail Badawi (ibadawi) via llvm-dev <llvm-dev at lists.llvm.org> wrote: >>

Thanks for notifying me. Yes, this was a recent change. Taking a look now. On Wed, Jul 20, 2016 at 1:49 PM, Michael Kuperstein <mkuper at google.com> wrote: > +Sanjay, who touched this last. :-) > > On Wed, Jul 20, 2016 at 12:44 PM, Ismail Badawi (ibadawi) via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> Hi folks, >> >> I'm hitting the

I wrote in a few weeks ago about writing an independent implementation of Bitcode and updating the docs to be more complete. Attached is a patch to docs/BitCodeFormat.html that adds a lot of information that was previously only available by reading the source code. It also corrects some errors. Josh -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi folks, I'm hitting the below assertion failure when compiling this small piece of C code (repro.c, attached). My command line is: bin/clang --target=aarch64-linux-gnu -c -O2 repro.c clang is built from top of trunk as of this morning. It only happens at -O2, and it doesn't happen with the default target (x86_64). I tried to reproduce using just 'llc -O2' but didn't

Sanjay: let me know if this is something that will apply to 3.9. Thanks, Hans On Wed, Jul 20, 2016 at 5:59 PM, Sanjay Patel via llvm-dev <llvm-dev at lists.llvm.org> wrote: > Quick update - the bug existed before I refactored that chunk in > InstSimplify with: > https://reviews.llvm.org/rL275911 > > In fact, as discussed in https://reviews.llvm.org/D22537 - because we have a

The enclosed patch adds documentation for the PARAMATTR_BLOCK, TYPE_BLOCK, and TYPE_SYMTAB_BLOCK records in the LLVM IR bitcode format. I have started documenting CONSTANTS_BLOCK and FUNCTION_BLOCK and will send patches when they are complete. -Peter- -------------- next part -------------- An HTML attachment was scrubbed... URL:

Sure. David, what do you think about merging this to 3.9? Sanjay: are you saying I'd just apply that diff to InstructionSimplify.cpp, not InstCombineSelect.cpp? On Fri, Jul 22, 2016 at 7:08 AM, Sanjay Patel <spatel at rotateright.com> wrote: > Hi Hans - > > Yes, I think this is a good patch for 3.9 (cc'ing David Majnemer as code > owner). The functional change was

David, Sanjay: ping? On Mon, Jul 25, 2016 at 11:07 AM, Hans Wennborg <hans at chromium.org> wrote: > Sure. David, what do you think about merging this to 3.9? > > Sanjay: are you saying I'd just apply that diff to > InstructionSimplify.cpp, not InstCombineSelect.cpp? > > On Fri, Jul 22, 2016 at 7:08 AM, Sanjay Patel <spatel at rotateright.com> wrote: >> Hi

LGTM On Wednesday, July 27, 2016, Hans Wennborg <hans at chromium.org> wrote: > David, Sanjay: ping? > > On Mon, Jul 25, 2016 at 11:07 AM, Hans Wennborg <hans at chromium.org > <javascript:;>> wrote: > > Sure. David, what do you think about merging this to 3.9? > > > > Sanjay: are you saying I'd just apply that diff to > >

The enclosed patch contains a number of wording and clarity improvements to BitCodeFormat.html, and documents in detail the record types used within MODULE blocks. I plan to continue documenting the rest of the record types, but I wanted to submit patches in reasonably-sized pieces. -Peter S. Housel- housel at acm.org -------------- next part -------------- A non-text attachment was scrubbed...

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

As discussed in the high-level ThinLTO RFC ( http://lists.cs.uiuc.edu/pipermail/llvmdev/2015-May/086211.html), we would like to add support for native object wrapped bitcode and ThinLTO information. Based on comments on the mailing list, I am adding support for ThinLTO in both normal bitcode files, as well as native-object wrapped bitcode. The following RFC describes the planned file format of

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 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

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 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 all, I need help in this problem. - i have a model class named Photo, a controller Photos. - when typing the URL http://localhost:3000/photos Rails calls the default index method. - but when typing http://localhost:3000/photos/index error saying "Couldn''t find Photo with ID=index" pops up, i cant even imagine why. - my Rails version is 2.1.0 thanks in advance yours,

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

Hi, This might be interesting since it seems to be the only LLVM test failing with VS 2015: FAIL: LLVM :: DebugInfo/PDB/pdbdump-symbol-format.test (7377 of 14212) ******************** TEST 'LLVM :: DebugInfo/PDB/pdbdump-symbol-format.test' FAILED ******************** Script: -- llvm-pdbdump -symbols C:\cygwin64\home\ismail\src\llvm\test\DebugInfo\PDB/Inputs/symbolformat.pdb |