| page ,132 | |
| title memcpy - Copy source memory bytes to destination | |
| ;*** | |
| ;memcpy.asm - contains memcpy and memmove routines | |
| ; | |
| ; Copyright (c) Microsoft Corporation. All rights reserved. | |
| ; | |
| ;Purpose: | |
| ; memcpy() copies a source memory buffer to a destination buffer. | |
| ; Overlapping buffers are not treated specially, so propogation may occur. |
This is the final part of a series about Algebraic Effects and Handlers.
So we've come to the core topic. The reality is that we've already covered most of it in the previous parts. Especially, in the third part, where we saw delimited continuations at work.
Here's a list of mildly interesting things about the C language that I learned mostly by consuming Clang's ASTs. Although surprises are getting sparser, I might continue to update this document over time.
There are many more mildly interesting features of C++, but the language is literally known for being weird, whereas C is usually considered smaller and simpler, so this is (almost) only about C.
struct foo {
struct bar {
int x;
why doesn't radfft support AVX on PC?
So there's two separate issues here: using instructions added in AVX and using 256-bit wide vectors. The former turns out to be much easier than the latter for our use case.
Problem number 1 was that you positively need to put AVX code in a separate file with different compiler settings (/arch:AVX for VC++, -mavx for GCC/Clang) that make all SSE code emitted also use VEX encoding, and at the time radfft was written there was no way in CDep to set compiler flags for just one file, just for the overall build.
[There's the GCC "target" annotations on individual funcs, which in principle fix this, but I ran into nasty problems with this for several compiler versions, and VC++ has no equivalent, so we're not currently using that and just sticking with different compilation units.]
The other issue is to do with CPU power management.
I think I’ve figured out most parts of the cubical type theory papers; I’m going to take a shot to explain it informally in the format of Q&As. I prefer using syntax or terminologies that fit better rather than the more standard ones.
Q: What is cubical type theory?
A: It’s a type theory giving homotopy type theory its computational meaning.
Q: What is homotopy type theory then?
A: It’s traditional type theory (which refers to Martin-Löf type theory in this Q&A) augmented with higher inductive types and the univalence axiom.
| /* @flow */ | |
| const KEY_KIND_STRING = 1; | |
| const KEY_KIND_NUMBER = 2; | |
| const KEY_KIND_BOOL = 3; | |
| const KEY_KIND_RECORD = 4; | |
| type KeyKind = 1 | 2 | 3 | 4; | |
| class KeyValue<K, V> { | |
| key: ?K; |
| #[derive(Copy, Clone, PartialEq, Eq, Debug)] | |
| pub struct True; | |
| #[derive(Copy, Clone, PartialEq, Eq, Debug)] | |
| pub struct False; | |
| pub trait Bool { | |
| fn new() -> Self; | |
| } | |
| impl Bool for True { |
| [ | |
| { | |
| "name":"ABAP", | |
| "type":"programming", | |
| "extensions":[ | |
| ".abap" | |
| ] | |
| }, | |
| { | |
| "name":"AGS Script", |
Translated to Markdown from this ancient TeX file. I’m not sure who made the original.
Hover over a link to see the place structure. Click it to view gismu info on Wiktionary.
girzu (group)