Skip to content

Instantly share code, notes, and snippets.

View jiayihu's full-sized avatar
:octocat:
Nyaning in O(1)

Jiayi Hu jiayihu

:octocat:
Nyaning in O(1)
View GitHub Profile
@japaric
japaric / README.md
Created August 6, 2016 22:34
How-to: figure out which compiler-rt intrinsics are *needed* to link `rustc`

Last updated: 2016-08-06

Summary: We'll modify the rustc-builtins crate to make all the intrinsics "undefined", then we'll proceed to bootstrap rustc normally. This will cause a linker error while linking rustc because the intrinsics are "undefined". The linker error message will list the intrinsics that are required to link rustc but the linker couldn't "find".

  1. First, we avoid building .so versions of std, rustc et al. because those will also fail to link but the linker error message will list all the intrinsics instead of only the ones that are actually needed to build a Rust program (binary). We do this by removing "dylib" from the
@Jakobud
Jakobud / bootstrap-ms.scss
Last active June 15, 2022 12:42 — forked from andyl/bootstrap_ms.css.scss
Adds in the missing 480px-797px breakpoint range to Bootstrap 3 for SASS
// Bootstrap Mid-Small - col-ms-* - the missing grid set for Bootstrap3.
//
// This is a hack to fill the gap between 480 and 767 pixels - a missing range
// in the bootstrap responsive grid structure. Use these classes to style pages
// on cellphones when they transition from portrait to landscape.
//
// Contains:
// Columns, Offsets, Pushes, Pulls for the Mid-Small layout
// Visibility classes for the Mid-Small layout
// Redefined visibility classes for the Extra Small layout