Andre Weissflog floooh

Symbol Servers

I'm assuming you are familiar with symbol servers - you might not have one set up yourself for your own projects, but you probably use Microsoft's public symbol server for downloading symbols for system DLLs.

For your own projects it might be useful to set up a symbol server - I won't go into how you do that here since it's well documented elsewhere, but basically you just set up a folder somewhere - say X:\symbols\ or \servername\symbols or even http://servername.foo/symbols/ which has a defined tree structure:

symbols/
symbols/mymodule.pdb/
symbols/mymodule.pdb/123456789012345678901234567890122/

This is my little Christmas-break experiment trying to (among other things) reduce the amount of generated code for containers.

THIS CODE WILL CONTAIN BUGS AND IS ONLY PRESENTED AS AN EXAMPLE.

The C++ STL is still an undesirable library for many reasons I have extolled in the past. But it's also a good library. Demons lie in this here debate and I have no interest in revisiting it right now.

The goals that I have achieved with this approach are:

Memory Optimization (Christer Ericson, GDC 2003)
http://realtimecollisiondetection.net/pubs/GDC03_Ericson_Memory_Optimization.ppt

Cache coherency primer (Fabian Giesen)
https://fgiesen.wordpress.com/2014/07/07/cache-coherency/

Code Clinic 2015: How to Write Code the Compiler Can Actually Optimize (Mike Acton)
http://gdcvault.com/play/1021866/Code-Clinic-2015-How-to

	#include "mu.h"

	#define _CRT_SECURE_NO_WARNINGS
	#include <malloc.h>
	#define _USE_MATH_DEFINES
	#include <math.h>
	#define _NO_CRT_STDIO_INLINE
	#include <stdio.h>
	#include <stdarg.h>
	#define NO_STRICT

	# Pre requisites
	- Enable DRI3 as described in https://vulkan.lunarg.com/app/docs/v1.0.3.1/getting_started_linux
	- Install a library for SHA, e.g. sudo apt-get install libgcrypt11-dev (if not already present)
	- Otherwise the driver may throw an error with "_mesa_sha1_compute" when loading SPIR-V shaders

	# Building
	- Clone Mesa Master : git clone git://anongit.freedesktop.org/mesa/mesa -b Master
	- cd mesa
	- autoreconf -vfi
	- ./configure --with-dri-drivers=i965 --with-gallium-drivers= --with-sha1= --with-vulkan-drivers=intel

	/*

	Twisting Pool Allocator
	=======================
	written by Leonard Ritter ([email protected])

	This file is in the public domain

	I don't know if I was the first one to stumble upon this technique, so
	I can't guarantee there's no patent on it, but let's hope there's not,

	"""This tool queries undefined symbols in a lib, then queries defined
	symbols, and then diffs the two sets so we know what the actual
	externals for the purpose of the lib are."""
	import os
	import re
	import subprocess

	libname = 'libbink2.a' # command line parsing? please.

	def parse_def_sym(str):

	int maxAASamplesConst; // gles2 img/apple/ext extensions all use different constants (facepalm)
	int halfConst; // gles2 and gles3 have different constants for half float type
	int texSRGBAConst; // gles2 (without 'internal format' ext) and gles3 have different constants for SRGB RGBA texture type
	int texSRGBConst; // gles2 (without 'internal format' ext) and gles3 have different constants for SRGB RGB texture type
	int etcFormatConst; // gles2/gles3 have different standard etc formats

	bool isPvrGpu;
	bool isMaliGpu;
	bool isAdrenoGpu;
	bool isTegraGpu;

	Below I collected relevant links and papers more or less pertaining to the subject of tetrahedral meshes.
	It's an ever-growing list.

	------------------------------
	Relevant links:

	http://en.wikipedia.org/wiki/Types_of_mesh
	http://en.wikipedia.org/wiki/Tetrahedron
	http://en.wikipedia.org/wiki/Simplicial_complex

	Code (and Windows binary) here: https://github.com/rygorous/atomic_ops_test

	I'd appreciate it if some people could run this and post their results here in a
	comment, with a short description of what CPU they're using.

	UPDATE: I have recent Intel CPUs (released within the last 3 years) pretty well covered
	by now, so if that's what you have in your machine, don't bother running the test. But
	I'd love to get some more data points for older Intel CPUs and AMD parts!

	Results so far: