A jobserver for running experiments on test machines and copying results back.
Microbenchmarks for linux memory management system
Hacky CLI Utility to help me with buses...
A toy implementation of the ISB in verilog for our toy processor.
Simple program to update the backlight brightness on my laptop
Converts any base (2 to 35) integer to any other base (2 to 35)
the home of the new rust website - now in beta!
The Rust Programming Language Blog
My collection of useful stuff for writing benchmarks on Linux ~4.4 (not very idiomatic or complete)
An experimental pure-Rust x86 bootloader
push eventmark-i-m/jobserver
commit sha 856e7ce48d0255604f9468ec99a9c0555e8db926
more robust handling of result path prefixes in client
push time in 4 days
push eventmark-i-m/jobserver
commit sha cfc9e422eecbe1029a71fc32fb661350f3b9655a
copy everything with prefix
push time in 4 days
PR opened rust-lang/team
pr created time in 4 days
push eventmark-i-m/team
commit sha 011d90afdffaed7caaf57780eef4b3d86af713d0
Make mark-i-m alumni of wg-rustc-dev-guide
push time in 4 days
PR opened rust-lang/team
pr created time in 4 days
push eventmark-i-m/team
commit sha 4849334866687d758a4fedd9697b6aa274ce0967
Remove mark-i-m from wg-prioritization
push time in 4 days
startedervandew/supertab
started time in 5 days
push eventmark-i-m/mdbook-linkcheck
commit sha cc3ef61cae3668374b5011cb8201fbab6d86e398
Change the name of the flag to "files" Co-authored-by: Camelid <[email protected]>
push time in 5 days
push eventmark-i-m/mdbook-linkcheck
commit sha ac9130783c23d720015ce0c13b58fa0f9c7b8e56
fix test
push time in 5 days
startedsharksforarms/vim-rust
started time in 5 days
issue commentrust-lang/rustc-dev-guide
Only run linkcheck on changed files
Also useful: https://docs.travis-ci.com/user/cron-jobs/#detecting-builds-triggered-by-cron
With this we can leave off the aforementioned flag in cron jobs to get the full build.
comment created time in 5 days
push eventmark-i-m/mdbook-linkcheck
commit sha c57eee60feef5051794b20e88f3275b125c13155
Merge pull request #36 from mark-i-m/master Upgrade to mdbook 0.4
commit sha 94d195db4bdb99c3e930f41af5a1d193e1b65171
(cargo-release) version 0.7.0
commit sha b6409a631f7294eeadca7cf9d77985488086ac67
(cargo-release) start next development iteration 0.7.1-alpha.0
commit sha eedb1264776ee6fcdc96bbeb3c69c7984751f18f
add option to check subset of files
push time in 5 days
issue commentrust-lang/rustc-dev-guide
Only run linkcheck on changed files
Is it possible to only check certain files with mdbook-linkcheck?
TMK, no, but it looks like it wouldn't be too hard to add... it looks like you could add a flag to mdbook-linkcheck and plumb it through to here: https://github.com/Michael-F-Bryan/mdbook-linkcheck/blob/b6409a631f7294eeadca7cf9d77985488086ac67/src/lib.rs#L160 Then, just filter out the files you don't want...
comment created time in 6 days
startedsdroege/ebur128
started time in 6 days
startedsld-columbia/esp
started time in 6 days
push eventmark-i-m/monotonic-pitch-detector
commit sha 9e92590dbfb9e0118a0db8f6bf119dfff0b62efd
play around with dft
push time in 8 days
startedawelkie/RustFFT
started time in 8 days
issue commentrust-lang/rust
Tracking issue: declarative macros 2.0
Given the ruat 2021 posts I've read so far and my vague knowledge of the state of things, it seems unlikely. There is still some design work needed and there doesn't seem to be anyone interested in pushing it over the finish line atm.
comment created time in 8 days
push eventmark-i-m/monotonic-pitch-detector
commit sha 0c60a62bc96a9efa802f7256727a963ded49269c
add readme
push time in 9 days
created repositorymark-i-m/monotonic-pitch-detector
Me playing around with audio processing to learn.
created time in 9 days
startedraspberrypi/rpi-eeprom
started time in 10 days
startedo8vm/krabs
started time in 10 days
startedmrDIMAS/rg3d
started time in 10 days
startedruuda/hound
started time in 11 days
pull request commentrust-lang/rust
[WIP] Refactor `Binder` to track bound vars
Lol, you should have seen some of the NRVO attempts: https://github.com/rust-lang/rust/pull/71003#issuecomment-613051683
comment created time in 11 days
startedgnebbia/kb
started time in 11 days
startedkohler/hotcrp
started time in 12 days
starteddropbox/pb-jelly
started time in 12 days
startedskeeto/endlessh
started time in 12 days
startedcloud-hypervisor/cloud-hypervisor
started time in 12 days
push eventmark-i-m/jobserver
commit sha dbae5de59a33a6886afa03535f673d3bf893885f
add machine mv command
push time in 12 days
PR closed rust-lang/rustc-dev-guide
cc @spastorino @jyn514
pr closed time in 14 days
pull request commentrust-lang/rustc-dev-guide
Suggest system llvm or assertions
Hmm... yeah it probably makes sense to close this PR then.
comment created time in 14 days
push eventmark-i-m/jobserver
commit sha 7b7af0cba61a66c38c99028850c2d8ebf88298cf
version and changelog
push time in 14 days
push eventmark-i-m/jobserver
commit sha 4a68637f24ef8938d432f302f38285a70d7cf4b4
fix bug with listing running processes
push time in 14 days
push eventrust-lang/rustc-dev-guide
commit sha d91788c71d86f10b478916bdf3402b0f0241e246
Add a chapter on all the identifiers used through `rustc`
commit sha a87ac24331b2df24d471910afcb42572af8cea72
Apply suggestions from code review Co-authored-by: Tshepang Lekhonkhobe <[email protected]>
commit sha 557f8063d335213a0ac95a39d47e54d2fdcddd93
Make the HIR chapter point to the new chapter on IDs
commit sha d4ae7b08a9114aa935b21858605c771b88b0096b
Fix typo Co-authored-by: Who? Me?! <[email protected]>
push time in 14 days
PR merged rust-lang/rustc-dev-guide
@rust-lang/wg-rustc-dev-guide I don't really know what's the best way organizing all of this. I'm not satisfied with the HIR IDs being described in detail in both the HIR chapter and this new one, and at the same time I'm not sure we should remove them from the HIR chapter because they are needed to understand the rest of the chapter.
Replaces #759, closes #748.
pr closed time in 14 days
issue closedrust-lang/rustc-dev-guide
Add info about IDs in the compiler
We should add the following content about IDs:
ID memo:
LocalDefId- the best variant, if you can use it for something do it. Cannot address entities in other crates and fine-grained entities like individual expressions in the current crate. Can address any items.DefId- the second choice. Can address entities in other crates, but cannot address fine-grained entities like individual expressions.HirId- Can address fine-grained entities like individual expressions in the current crate. Fine-grained entities from other crates can never be addressed in rustc.NodeId- The last choice. Can address fine-grained entities like individual expressions whenHirIds are not yet created.
Originally posted by @petrochenkov in https://github.com/rust-lang/rust/pull/73291#issuecomment-643829018
closed time in 14 days
mark-i-m
startedgoogle/perf_data_converter
started time in 14 days
push eventmark-i-m/jobserver
commit sha c495d640178fe2e0116b377045839f9c0e91f114
update changelog
push time in 14 days
push eventmark-i-m/jobserver
commit sha e4a479bd7860249d655ad49c189ac4ed404b2dcc
bump opt level a bit
commit sha 13c5d23191fd1f5e82b250e88dda9efcc338a824
update server and client to be faster at listing running jobs
commit sha aeccda579a3e8d3a280c4c9415c4ad064abb4aa3
add option to list running jobs
push time in 14 days
startedByron/gitoxide
started time in 15 days
startedtermhn/ultraviolet
started time in 15 days
Pull request review commentrust-lang/rustc-dev-guide
Add a chapter on all the identifiers used through `rustc`
+# Identifiers in the Compiler++If you have read the few previous chapters, you now know that `rustc` uses+many different intermediate representations to perform different kinds of analyses.+However, like in every data structure, you need a way to traverse the structure+and refer to other elements. In this chapter, you will find information on the+different identifiers `rustc` uses for each intermediate representation.++## In the AST++A [`NodeId`] is an identifier number that uniquely identifies an AST node within+a crate. Every node in the AST has its own [`NodeId`], including top-level items+such as structs, but also individual statements and expressions.++However, because they are absolute within in a crate, adding or removing a single+node in the AST causes all the subsequent [`NodeId`]s to change. This renders+[`NodeId`]s pretty much useless for incremental compilation, where you want as+few things as possible to change.++[`NodeId`]s are used in all the `rustc` bits that operate directly on the AST,+like macro expansion and name resolution.++[`NodeId`]: https://doc.rust-lang.org/nightly/nightly-rustc/rustc_ast/node_id/struct.NodeId.html++## In the HIR++The HIR uses a bunch of different identifiers that coexist and serve different purposes.++- A [`DefId`], as the name suggests, identifies a particular definition, or top-level+ item, in a given grate. It is composed of two parts: a [`CrateNum`] which identifies
item, in a given crate. It is composed of two parts: a [`CrateNum`] which identifies
comment created time in 16 days
push eventrust-lang/rustc-dev-guide
commit sha e7b11c1d89acd021d6c0410fb0b604f3a824814d
Document edition flag for UI tests
commit sha d333d1e74f542727510762f9b5aac0846ea79849
Note that the default is 2015
commit sha 434556f9e001773d347f2ce025e308cb0a5152b6
Address nits
push time in 16 days
PR merged rust-lang/rustc-dev-guide
Closes https://github.com/rust-lang/rustc-dev-guide/issues/854. r? @pickfire
pr closed time in 16 days
issue closedrust-lang/rustc-dev-guide
https://rustc-dev-guide.rust-lang.org/tests/adding.html
// edition:2018
closed time in 16 days
pickfire
pull request commentrust-lang/rustc-dev-guide
Suggest system llvm or assertions
Does anyone remember what the status of this PR is?
comment created time in 16 days
push eventmark-i-m/jobserver
commit sha dd15f2586118073a68724d99e8658d02c16ffdd4
Add -f to machine add subcommand
push time in 17 days
pull request commentrust-lang/rustc-dev-guide
Add a chapter on all the identifiers used through `rustc`
You might want to update the HIR chapter to point at this one. I think there is some content about identifiers there too.
comment created time in 18 days
startedalessandrod/snuffy
started time in 18 days
push eventmark-i-m/spurs
commit sha a78eaa74026e04709b0d14d036a97e8fbc71141a
bump version
push time in 18 days
push eventmark-i-m/spurs
commit sha 38b02d03a3d14926774232aafb064a7c4109cd7b
Add SshShell::with_any_key (#4) This checks every ssh key in $HOME/.ssh for a key that works with the desired host. Signed-off-by: Bijan Tabatabai <[email protected]>
push time in 18 days
PR merged mark-i-m/spurs
This function checks every ssh key in $HOME/.ssh for a key that works with the desired host.
pr closed time in 18 days
startedelves/elvish
started time in 19 days
issue openedwezm/read-rust
Please add this post:
Post URL: https://gist.github.com/mark-i-m/57b51099e02f2d1fb4d4a4bf08e92965 Author Name: mark-i-m Categories: pick one: Rust 2021
created time in 19 days
startedopencontainers/runc
started time in 20 days
startedopenjdk/jdk
started time in 20 days
pull request commentrust-lang/rustc-dev-guide
Document CGU partioning in case of generic and inline functions
I restarted it
comment created time in 21 days
issue commentrust-lang/rust
Tracking issue for renaming crates inside compiler directory
You might want to cc the original threads to make sure people see this.
I pass my cloak to you @Dylan-DPC. May the force be with you!
comment created time in 22 days
startedDataDog/scipio
started time in 25 days
push eventmultifacet/0sim-experiments
commit sha 6b283341d3fabd81a6467e75a3c81cbb01aed406
fix nightly breakage
push time in 25 days
startedsamizdatco/skia-canvas
started time in 25 days
startedhtop-dev/htop
started time in a month
pull request commentrust-lang/rustc-dev-guide
I posted on zulip too, but just so it's easy to find, here is the tex of the diagram: https://gist.github.com/mark-i-m/e0c885f7b585f02232962b5be0d457f8
comment created time in a month
startedphilberty/gccrs
started time in a month
startedgoogle/autocxx
started time in a month
push eventmark-i-m/highfive
commit sha 0a9ed0a03622c53b9bcb9c0e66670048ad96cafc
Update rust.json
push time in a month
Pull request review commentrust-lang/highfive
"library/panic_abort": ["libs"], "library/panic_unwind": ["libs"], "library/proc_macro": ["@petrochenkov"],- "src/librustc": ["compiler-team", "compiler-team-contributors"],+ "compiler/rustc_middle": ["compiler-team", "compiler-team-contributors"], "src/librustdoc": ["rustdoc"], "library/std": ["libs"], "library/term": ["libs"], "library/test": ["libs"], "src/llvm-project": ["@cuviper"],- "src/rustc": ["compiler-team", "compiler-team-contributors"],+ "compiler/rustc": ["compiler-team", "compiler-team-contributors"],
I'm pretty confused now... should I drop line 27 altogether, and just leave this line, then?
comment created time in a month
PR opened rust-lang/highfive
cc @matklad @Mark-Simulacrum
I think these are the correct changes, but I'm not super sure.
pr created time in a month
push eventmark-i-m/highfive
commit sha 735284c0f2ff0d064f962f30dbf5b52dc566da43
Update rust.json
push time in a month
pull request commentrust-lang/rust
Move almost all compiler crates to compiler/
@vandenheuvel I just made a PR to update that. It is accurate now.
comment created time in a month
push eventmark-i-m/unmaintainable-code
commit sha 7a06105a5fc20554484cf3d27041a33a2ebe01ba
Add some emphasis.
push time in a month
fork mark-i-m/unmaintainable-code
A more maintainable, easier to share version of the infamous http://mindprod.com/jgloss/unmain.html
fork in a month
startedDroogans/unmaintainable-code
started time in a month
push eventmark-i-m/rustc-guide
commit sha de8e8103c83b58959eb6be0e3753f4ad599f9250
Typo Co-authored-by: Joshua Nelson <[email protected]>
push time in a month
Pull request review commentrust-lang/rustc-dev-guide
Fix links and names after compiler mv to compiler/
Here we see the highest error code in use is `E0591`, so we _probably_ want `E0592`. To be sure, run `rg E0592` and check, you should see no references. Next, open `src/{crate}/diagnostics.rs` within the crate where you wish to issue-the error (e.g., `src/librustc_typeck/diagnostics.rs`). Ideally, you will add+the error (e.g., `compiler/rustc_typeck/src/diagnostics.rs`). Ideally, you will add
@jyn514 Ah, I see. Would you mind making a PR for this? I'm a bit low on bandwidth these days.
comment created time in a month
PR opened alexcrichton/rustc-auto-publish
cc @matklad
From a quick glance through the source, I think this should be sufficient...
pr created time in a month
push eventmark-i-m/rustc-auto-publish
commit sha aa54995a2238f96a9b9bd0fd1b327769f3cd24db
compiler moved to compiler/
push time in a month
starteddexterleng/vimac
started time in a month
startedvinayak-mehta/present
started time in a month
push eventmark-i-m/rustc-guide
commit sha cfc51d8fab62958085f290459d6dac9b28586658
fix typos
push time in a month
push eventmark-i-m/rustc-guide
commit sha f2fc4db418f7bff2323f1d386b2eaa27b59e9296
fix line lengths
push time in a month