| /* | |
| MIT License | |
| Copyright 2019 Foster T. Brereton | |
| Permission is hereby granted, free of charge, to any person obtaining a copy of this software and | |
| associated documentation files (the "Software"), to deal in the Software without restriction, | |
| including without limitation the rights to use, copy, modify, merge, publish, distribute, | |
| sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is | |
| furnished to do so, subject to the following conditions: |
This is a short post that explains how to write a high-performance matrix multiplication program on modern processors. In this tutorial I will use a single core of the Skylake-client CPU with AVX2, but the principles in this post also apply to other processors with different instruction sets (such as AVX512).
Matrix multiplication is a mathematical operation that defines the product of
| package statuscode | |
| import ( | |
| "fmt" | |
| "strconv" | |
| "strings" | |
| ) | |
| // Code are the status codes that define the stage of the transaction | |
| type Code uint |
What is strict aliasing? First we will describe what is aliasing and then we can learn what being strict about it means.
In C and C++ aliasing has to do with what expression types we are allowed to access stored values through. In both C and C++ the standard specifies which expression types are allowed to alias which types. The compiler and optimizer are allowed to assume we follow the aliasing rules strictly, hence the term strict aliasing rule. If we attempt to access a value using a type not allowed it is classified as undefined behavior(UB). Once we have undefined behavior all bets are off, the results of our program are no longer reliable.
Unfortunately with strict aliasing violations, we will often obtain the results we expect, leaving the possibility the a future version of a compiler with a new optimization will break code we th
| // https://github.com/michael-ciniawsky/postcss-load-config | |
| // | |
| const webpackConfig = require('./build/webpack.base.conf.js') | |
| // 使用 postcss-import-webpack-resolver 就可以识别别名了。 | |
| const createResolver = require('postcss-import-webpack-resolver') | |
| module.exports = { | |
| "plugins": { | |
| // to edit target browsers: use "browserslist" field in package.json | |
| // https://www.npmjs.com/package/postcss-import-webpack-resolver |
| #!/usr/bin/env python | |
| """ | |
| An example of how to remove comments and trailing commas from JSON before | |
| parsing. You only need the two functions below, `remove_comments()` and | |
| `remove_trailing_commas()` to accomplish this. This script serves as an | |
| example of how to use them but feel free to just copy & paste them into your | |
| own code/projects. Usage:: | |
| json_cleaner.py some_file.json |
| get_latest_release() { | |
| curl --silent "https://api.github.com/repos/$1/releases/latest" | # Get latest release from GitHub api | |
| grep '"tag_name":' | # Get tag line | |
| sed -E 's/.*"([^"]+)".*/\1/' # Pluck JSON value | |
| } | |
| # Usage | |
| # $ get_latest_release "creationix/nvm" | |
| # v0.31.4 |
Authorization and Authentication are hard. when you only have to implement them once (as you do within a monolith) instead of over and over again, it makes the developer happy :-), and maybe leads to less implementation failures.
When you have a bunch of microservices, this is something that has to be considered.
Implement it once or in every microservice, or something in between?
| #include <iostream> | |
| #include <vector> | |
| using namespace std; | |
| void print(const vector<int>& vec) { | |
| vector<int>::const_iterator it = vec.begin(); | |
| while(it < (vec.end() - 1)) { | |
| cout << *it << ','; | |
| advance(it, 1); | |
| } |
