- 2011 - A trip through the Graphics Pipeline 2011
- 2015 - Life of a triangle - NVIDIA's logical pipeline
- 2015 - Render Hell 2.0
- 2016 - How bad are small triangles on GPU and why?
- 2017 - GPU Performance for Game Artists
- 2019 - Understanding the anatomy of GPUs using Pokémon
- 2020 - GPU ARCHITECTURE RESOURCES
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
//----------------------------------------------- | |
// | |
// Copyright (C) 2022 RYOSKATE | |
// | |
// Licensed under the MIT License. | |
// | |
//----------------------------------------------- | |
#pragma once | |
# include <Siv3D.hpp> // OpenSiv3D v0.6.5 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#include <Siv3D.hpp> | |
#include <imgui.h> | |
#include "imgui_impl_s3d.h" | |
#include "DearImGuiAddon.hpp" | |
/// @brief アドオンの登録時の初期化処理を記述します。 | |
/// @remark この関数が false を返すとアドオンの登録は失敗します。 | |
/// @return アドオンの初期化に成功した場合 true, それ以外の場合は false | |
bool DearImGuiAddon::init() |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
// Copyright (c) 2019, Conor Williams | |
// Permission to use, copy, modify, and/or distribute this software for any | |
// purpose with or without fee is hereby granted, provided that the above | |
// copyright notice and this permission notice appear in all copies. | |
// Compiling on gcc 9.2 with: -std=c++2a -O3 -fconcepts | |
#ifndef ZIP_CPP | |
#define ZIP_CPP |
Putting cryptographic primitives together is a lot like putting a jigsaw puzzle together, where all the pieces are cut exactly the same way, but there is only one correct solution. Thankfully, there are some projects out there that are working hard to make sure developers are getting it right.
The following advice comes from years of research from leading security researchers, developers, and cryptographers. This Gist was [forked from Thomas Ptacek's Gist][1] to be more readable. Additions have been added from