search for: blockchains

Hi, there! I?m Suzana Joel from Lumos Labs. I?d like to invite you to attend the Think with Terra Tech Talk - Back to Blockchain Basics, that?s scheduled to take place on *Monday, 5 October at 5:30 p.m. IST. * The Tech Talk will feature three sessions to help anyone get a working understanding of - - blockchain technology, - Smart Contracts, - Building on the Terra

On Oct 19, 2011, at 5:50 AM, Chandler Carruth wrote: > Ok, wow that wasn't hard at all. Awesome ;-) > This is still *very* much a rough draft, but it's probably better to review that the previous patch. One big caveat, I know I have an iteration bug in here somewhere that is inf-looping. Just ran out of steam debugging it, will pick it back up again later today to shake it out.

This RFC is to ask whether the community is interested in further discussion of iN bytes support. Last time the issue was on the agenda in May and the discussion was triggered by Jesper Antonsson's patches (see <https://lists.llvm.org/pipermail/llvm-dev/2019-May/132080.html> https://lists.llvm.org/pipermail/llvm-dev/2019-May/132080.html). It seems that, while some downstream areas

Hi, After building out project in release mode, caught an assertion, which we have not seen before: hello_f: /tmp/rpmbuild_debug/BUILD/llvm/build/include/llvm/ADT/DenseMap.h:126: void llvm::DenseMap<KeyT, ValueT, KeyInfoT>::clear() [with KeyT = llvm::MachineBasicBlock*, ValueT = <unnamed>::BlockChain*, KeyInfoT = llvm::DenseMapInfo<llvm::MachineBasicBlock*>]: Assertion

...;t remember that being in the published algorithm. > I would like to see a more explicit handling of loop layout. There is a tradeoff between entering the loop with a branch, and having the exit block last. It is not clear to me that this algorithm handles that properly. How do you ensure that BlockChains start at loop headers? How do you ensure that loop exits are laid out following the loop body, especially in the presence of critical edges? Why not layout blocks according to MachineLoopInfo? The SCC abstraction seems overly generic and unnecessary. When you merge chains, why don't you dele...

Dear NVPTX community, I've create a bug http://llvm.org/bugs/show_bug.cgi?id=13521 with reprocase for this issue. Please, help us to fix it. Last 1,5 months we regularly encounter & workaround or fix 1-2 bugs per week in NVPTX backend. This is definitely not the amount of work we can completely serve ourselves... We would really really appreciate some collaboration. Thanks, - D.

...Pointers, Alias & ModRef Analyses - Point-Free Templates *Session 11 (Tuesday, 2:00-3:25PM, Bristol 2)* - Organising benchmarking LLVM-based compiler: Arm experience - Protecting the code: Control Flow Enforcement Technology *Session 12 (Tuesday, 4:30-5:15PM, Bristol 1 & 2)* - LLVM x Blockchains = A new Ecosystem of Decentralized Applications Thanks, Arnaud -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180409/0874f41f/attachment.html>

Unfortunately, I cannot reproduce this. Based on your bugzilla comment, it does look like a mis-compile with your system compiler. Does the same issue occur if you build LLVM as static libraries? On 08/03/2012 12:24 AM, Dmitry N. Mikushin wrote: > Dear NVPTX community, > > I've create a bug http://llvm.org/bugs/show_bug.cgi?id=13521 with > reprocase for this issue. > >

On Wed, Oct 19, 2011 at 3:24 AM, Chandler Carruth <chandlerc at google.com>wrote: > On Tue, Oct 18, 2011 at 6:58 PM, Jakob Stoklund Olesen <stoklund at 2pi.dk>wrote: > >> >> On Oct 18, 2011, at 5:22 PM, Chandler Carruth wrote: >> >> As for why it should be an IR pass, mostly because once the selection >>> dag runs through the code, we can never

On Tue, Oct 18, 2011 at 6:58 PM, Jakob Stoklund Olesen <stoklund at 2pi.dk>wrote: > > On Oct 18, 2011, at 5:22 PM, Chandler Carruth wrote: > > As for why it should be an IR pass, mostly because once the selection dag >> runs through the code, we can never recover all of the freedom we have at >> the IR level. To start with, splicing MBBs around requires known about

..., and so would be laid out exactly as they came into this pass, modulo fallthrough branches that for some reason we have probability information that says aren't likely to be taken. That said, I haven't done a thorough investigation of this... See below... > > How do you ensure that BlockChains start at loop headers? > > How do you ensure that loop exits are laid out following the loop body, > especially in the presence of critical edges? > These are really interesting questions. I'm not sure how to answer them. Is this something we could continue to iterate on? Maybe you...

...> - Point-Free Templates > > *Session 11 (Tuesday, 2:00-3:25PM, Bristol 2)* > - Organising benchmarking LLVM-based compiler: Arm experience > - Protecting the code: Control Flow Enforcement Technology > > *Session 12 (Tuesday, 4:30-5:15PM, Bristol 1 & 2)* > - LLVM x Blockchains = A new Ecosystem of Decentralized Applications > > Thanks, > Arnaud >

Pete Biggs wrote: > >> We've been using pxeboot to pull up a menu, to build or rebuild >> machines for years. We have this new server, and it fails. Times out. >> What's happening is that it tries in this order >> .../pxelinux.cfg/b8945908-d6a6-41a9-611d-74a6ab80b83d >> .../pxelinux.cfg/01-88-99-aa-bb-cc-dd >> .../pxelinux.cfg/C0A8025B

David, just to clarify a misconception I might have introduced, we do not have linear memory in the sense that all data is stored as a trie. We do support arrays, structures and GEPs, however, as well as all relevant features in C by modeling memory. So regarding concepts of byte, all 5 statements you gave are true for our target. Either due to the specification or because of performance (gas

On 24/10/2019 14:21, JF Bastien via llvm-dev wrote: > I’d like to understand what programming model you see programmers using. > You don’t need 257 bits per byte if you only offer 257 bit integers. > Rather, bytes aren’t really a thing at that point. LLVM kinda handles iN > already, and your backend would legalize everything to exactly this type > and nothing else, right? Would

<http://callingketti.cf/lists/lt.php?id=YUgNCAdSGAFUXR1QWlQKVF0F> <http://callingketti.cf/lists/lt.php?id=YUgMAAZRGAFUXR1QWlQKVF0F> Normally I start this message off with the whole "this is what Exodus is all about <http://callingketti.cf/lists/lt.php?id=YUgMAg9SGAFUXR1QWlQKVF0F> " and "the election is not to die bold

"Beth <http://bethesday.gq/lists/lt.php?id=YUgFAQVcUU9RVlkdU1wDX1cNVg> esda" reads as "the house is the..." in Spanglishrew ... CITY Who knows whose ... *Adamic language* is, according to Jewish <http://bethesday.gq/lists/lt.php?id=YUgFAQVcUk9RVlkdU1wDX1cNVg> tradition (as recorded in the /midrashim

<cursi.ve.lamc.la> You are in The Matrix <http://isiti.gq/lists/lt.php?id=YUgNAAVdGAFSXB1QWlQKVF0F> . That's a significantly better thing than implied by the movie, but it's a good introduction to the reason for Creation, and why we are here trying to help an entire civilization transition from ?simulated reality? to Heaven. The New Testament is our guide, and seeing it's