Displaying 18 results from an estimated 18 matches for "blockchain".
2020 Oct 01
0
Invitation to register for the Think with Terra Blockchain Tech Talk
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 Blockchain
Register: https://www.air...
2011 Oct 19
3
[LLVMdev] Question regarding basic-block placement optimization
...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.
Maybe splicing a block into it current position will create a loop?
Some random notes:
- Please add a description of the algorithm.
- Please add a comment to the BlockChain class.
- Use a separate anonymous namespace per class, and don't indent for the namespace.
+BlockChain *BlockPlacement2::CreateChain(MachineBasicBlock *BB) {
+ Chains.push_back(BlockChain(BlockToChain, BB));
+ BlockToChain[BB] = &Chains.back();
+ assert(ActiveChains.insert(&Chains.b...
2019 Oct 23
2
RFC: On non 8-bit bytes and the target for it
...is barely maintainable given the lack of utilization
targets in the upstream. The reason why I would like to again raise the
matter is that we, the TON Labs team, would like to upstream our backend
solution.
The backend generates code for TON virtual machine designed to run smart
contracts in TON blockchain (see the original specifications for TVM and
TON respectively at <https://test.ton.org/tvm.pdf>
https://test.ton.org/tvm.pdf and at <https://test.ton.org/tblkch.pdf>
https://test.ton.org/tblkch.pdf).
The target has the following key particularities:
- stack-based virtual machine...
2012 Aug 02
2
[LLVMdev] [NVPTX] Strange assertion around BlockToChain.clear(); in Release+Asserts build
...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 `NumEntries
== 0 && "Node count imbalance!"' failed.
Program received signal SIGABRT, Aborted.
0x00007ffff785c945 in raise () from /lib64/libc.so.6
(gdb) bt
#0 0x00007ffff785c945 in raise () from /li...
2011 Oct 20
0
[LLVMdev] Question regarding basic-block placement optimization
...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.
>
> Some random notes:
>
> - Please add a description of the algorithm.
> - Please add a comment to the BlockChain class.
> - Use a separate anonymous namespace per class, and don't indent for the namespace.
>
...
> Note that MachineFunction::iterator decays into an MBB pointer, so you can say FI->canFallThrough() and AnalyzeBranch(*FI...)
>
> + WeightedEdge WE = { BaseFrequency * M...
2012 Aug 03
0
[LLVMdev] [NVPTX] Strange assertion around BlockToChain.clear(); in Release+Asserts build
...ct 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 `NumEntries
> == 0 && "Node count imbalance!"' failed.
>
> Program received signal SIGABRT, Aborted.
> 0x00007ffff785c945 in raise () from /lib64/libc.so.6
> (gdb) bt
> #0 0x000...
2018 Apr 09
1
EuroLLVM'18 : moderators needed!
...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>
2012 Aug 03
1
[LLVMdev] [NVPTX] Strange assertion around BlockToChain.clear(); in Release+Asserts build
...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 `NumEntries
>> == 0 && "Node count imbalance!"' failed.
>>
>> Program received signal SIGABRT, Aborted.
>> 0x00007ffff785c945 in raise () from /lib64/libc.so.6
>>...
2011 Oct 19
0
[LLVMdev] Question regarding basic-block placement optimization
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
2011 Oct 19
3
[LLVMdev] Question regarding basic-block placement optimization
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
2011 Oct 20
2
[LLVMdev] Question regarding basic-block placement optimization
...gt;
> > - Please add a description of the algorithm.
>
There is more described now in various comments, but I'm going to work on an
overview in the file comments. Not done yet, but wanted to get it back out
for review in a more polished state.
> > - Please add a comment to the BlockChain class.
>
Done.
> > - Use a separate anonymous namespace per class, and don't indent for the
> namespace.
>
Done.
> >
> ...
> > Note that MachineFunction::iterator decays into an MBB pointer, so you
> can say FI->canFallThrough() and AnalyzeBranch(*FI......
2018 Apr 09
0
EuroLLVM'18 : moderators needed!
...> - 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
>
2017 Apr 11
3
CentOS 6 and pxeboot
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
2019 Oct 31
2
RFC: On non 8-bit bytes and the target for it
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
2019 Oct 24
4
RFC: On non 8-bit bytes and the target for it
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
2018 Oct 07
0
Come Hell or High Treason
...f" to
help people be smarter, happier, safer, and ... well, to do it yourselves
so you're happy with it and get all the credit (lol).
<http://callingketti.cf/lists/lt.php?id=YUgMAAZRGAFUXR1QWlQKVF0F>
Over the course of the last few years new little additions have popped up,
"/BLOCKCHAIN/" for instance connected to the great chain of Revelation 20:1
(which is already the other half of "the e
<http://callingketti.cf/lists/lt.php?id=YUgNCAdSGAFUXR1QWlQKVF0F>
lection is not to die bold" and the basic idea of building a better
"overnet" ... a place where...
2018 Aug 19
0
The House of .... BETHESDAY ... and stripping in a Fishbowl. #nipoolsoparmleg
...become smarter and happier rather than
... "not ourselves."
It is an emancipation, and it seems pretty clear that there's a tangible
lack of desire on the ground here to "make the sword of Arthur" which is
tied through these messages to the chain or Revelation 20:1 and the
BLOCKCHAIN as well as another microcosm etched
into my youth
<http://bethesday.gq/lists/lt.php?id=YUgDBwdSGAFQXR1QWlQKVF0F>
that this thing revolves around free speech and free thought and building a
system of self-governance that utilizes available technologies to help
self-governance. I'm not sure...
2018 May 20
0
You say #nothing... I say "Hello. Hello! Hello?" Moving forward with this will stop this violence, it will also stop murder, and then death. (... in that order)
...s/lt.php?id=YUgMAA5VGAFSXB1QWlQKVF0F>
voat <http://isiti.gq/lists/lt.php?id=YUgMAA5WGAFSXB1QWlQKVF0F>
; see "null vote" and how it connects to "empeopled
<http://isiti.gq/lists/lt.php?id=YUgMAA5XGAFSXB1QWlQKVF0F>
." Creating a working prototype to show how "/*blockchain*/" is a divinely
given name for a way to block the chain of censorship held in the hand of
the angel of Revelation 20:1 is not a difficult task--it's fucking insane
that nobody is calling or emailing me to work on that. I mean, it's
"destiny" and "inevitable" that t...