| using TAstTask = TExpectedTask<TExprPtr, TParserError, TLoc>; | |
| // factor ::= Number | Ident | '(' Expr ')' | 'fun' ... | |
| TAstTask factor(TTokenStream& s) { | |
| auto tok = co_await s.Next(); | |
| if (tok.Type == TToken::Number) | |
| co_return std::make_shared<TNumberExpr>(tok.Loc, tok.Value.i64); | |
| if (tok.Type == TToken::Identifier) | |
| co_return std::make_shared<TIdentExpr>(tok.Loc, tok.Name); | |
| if (tok.Type == TToken::Keyword && tok.Value == (int)TToken::Fun) |
This profile achieves 50% - 80% release profile performance, while also provides a reasonable amount of safety checks and debugging support. This should also be the profile for your CI build.
-Og -Wall -Wextra -D_FORTIFY_SOURCE=2 -fstack-protector-strong -g -D_GLIBCXX_ASSERTIONS
| #!/usr/bin/env bash | |
| # WARNING!! | |
| # This will obliterate all the data in your partition!! (not actually true, but act as if it was) | |
| # Do NOT execute this script if you don't fully understand it! | |
| # create directories | |
| mkdir -p /mnt/gentoo |
| #!/bin/bash | |
| # !!WARNING!! | |
| # This will DELETE all efforts you have put into configuring nix | |
| # Have a look through everything that gets deleted / copied over | |
| nix-env -e '.*' | |
| rm -rf $HOME/.nix-* | |
| rm -rf $HOME/.config/nixpkgs |
⚠️ Note 2023-01-21
Some things have changed since I originally wrote this in 2016. I have updated a few minor details, and the advice is still broadly the same, but there are some new Cloudflare features you can (and should) take advantage of. In particular, pay attention to Trevor Stevens' comment here from 22 January 2022, and Matt Stenson's useful caching advice. In addition, Backblaze, with whom Cloudflare are a Bandwidth Alliance partner, have published their own guide detailing how to use Cloudflare's Web Workers to cache content from B2 private buckets. That is worth reading,
This document was originally written several years ago. At the time I was working as an execution core verification engineer at Arm. The following points are coloured heavily by working in and around the execution cores of various processors. Apply a pinch of salt; points contain varying degrees of opinion.
It is still my opinion that RISC-V could be much better designed; though I will also say that if I was building a 32 or 64-bit CPU today I'd likely implement the architecture to benefit from the existing tooling.
Mostly based upon the RISC-V ISA spec v2.0. Some updates have been made for v2.2
The RISC-V ISA has pursued minimalism to a fault. There is a large emphasis on minimizing instruction count, normalizing encoding, etc. This pursuit of minimalism has resulted in false orthogonalities (such as reusing the same instruction for branches, calls and returns) and a requirement for superfluous instructions which impacts code density both in terms of size and
Recently I came across a web service that required two-factor authentication using the Symantec VIP Access App. I already manage all of my OTP tokens in a different app (If you are on iOS I highly recommend using OTP Auth by Roland Moers.) and did not want to have to use yet another app to generate the TOTP.
There is a way to generate a Symantec VIP Access compatible token very easily if you have access to an environment which can run Python PIP. I happen to have Ubuntu Windows Subsystem Linux running on my machine. (If you are running Windows 10 and don't have this you should really check it out.) Let's get started...
Here we install python3-pip and qrencode so we can generate our secret, I
| /** from http://www.reddit.com/r/programming/comments/mlbna/scala_feels_like_ejb_2/c31z0co */ | |
| interface Pong<T> {} | |
| class Ping<T> implements Pong<Pong<? super Ping<Ping<T>>>> { | |
| static void Ping() { | |
| Pong<? super Ping<Long>> Ping = new Ping<Long>(); | |
| } | |
| } | |
| > javac Ping.java |
