# linker A linker is a tool that combines object files into an executable or dynamic library. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## The Underrust: Rust's assembly output DevFeed: [The Underrust: Rust's assembly output]() Original publisher: [Read original article]() Author: Graham King Published: 2022-08-31T07:00:00Z Content type: tutorial Language: en Sources: [Graham King]() Topics: [Rust](), [Assembly](), [Compiler](), [LLVM](), [cpu](), [Linux](), [linker]() Tags: [assembly](), [compiler](), [cpu](), [linker](), [linux](), [llvm](), [optimize](), [performance](), [rust](), [software](), [underrust]() ### AI overview This article introduces the Underrust series, which examines Rust programs through their generated assembly. It explains a repeatable setup using Rust on Linux with an Intel processor, a stripped-down program, LLVM optimizations, a custom entry point, and release builds to make assembly easier to inspect. ### Source excerpt Assembly: In all the world of the programmer, there is no more important output. ## 10 LDFLAGS I Love DevFeed: [10 LDFLAGS I Love]() Original publisher: [Read original article]() Published: 2016-07-18T20:00:14Z Content type: article Language: en Sources: [Jessie Frazelle]() Topics: [linker](), [Programming]() Tags: [binaries](), [debug](), [linker](), [map](), [symbols]() ### AI overview A sarcastic programming article presents ten favorite LDFLAGS and briefly explains their linker behavior, including static linking, symbol export, archive inclusion, link-map generation, symbol stripping, tracing, library search restrictions, and unresolved symbols. ### Source excerpt Hello and welcome to what will become the most sarcastic post on my blog. This is going to be a series of "buzzfeed" style programming articles and after this post I very happily pass the baton to Filippo Valsorda to continue. And I urge you to write your own as well. @jessfraz "We asked Jess for her top 10 ldflags; you won't believe what happened next" -- adg (@enneff) July 17, 2016 So here they are: -static I would be an embarassment to myself if I didn't start with the flag that tells the linker to not link against shared libraries. This is the best flag. STATIC BINARIES FTW. --export-dynamic This flag tells the linker to add all the symbols to the dynamic symbol table. This is especially important if you want to do "The Macgyver of Dlopening" and dlopen yourself. --whole-archive This is another flag that comes in handy when you want to dlopen yourself. See most linkers will only take into account the things it knows it needs. But with this flag, you tell it "YOLO, I want it all" so that later you can dlopen yourself with that symbol that was never actually used until runtime. FUN! --no-whole-archive This flag un-sets the --whole-archive flag which is nice for when you only want the whole archive of one library but not all the others you are linking to. --print-map This flag is just dope. It prints a link map to stdout. This gives you information about object files, common symbols, and the values assigned to symbols. --strip-all This flag strips all the symbol information from the artifact produced. If say you are a few KB/MB off from your binary fitting on a floppy disk, this flag is your friend. --strip-debug This flag is very similar to --strip-all except it only strips the debug symbol information. This all really depends on how much you need to shave off to fit that binary on a floppy disk. --trace This flag is great for debugging. It prints the names of the input files as ld processes them. -nostdlib This flag forces the linker to only search the libraries y ## ReactOS Newsletter 71: USB stack development and build tool fixes DevFeed: [ReactOS Newsletter 71: USB stack development and build tool fixes]() Original publisher: [Read original article]() Published: 2010-04-23T00:00:00Z Content type: news Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [USB](), [gcc](), [linker](), [Windows](), [Xen]() Tags: [build-tools](), [c-plus-plus](), [compiler](), [free](), [gcc](), [linker](), [open-source](), [os](), [react](), [reactos](), [usb](), [win32](), [winapi]() ### AI overview This ReactOS newsletter reports work on lower-level USB stack components, including a basic usbehci driver tested in Windows XP, and describes GCC, linker, library, and binutils fixes needed for interoperability with Microsoft's C/C++ compiler. ### Source excerpt NT USB Stack Pre-Vista, the USB architecture started with a very low level usbport driver. This driver was the one that created device objects for each USB controller and received I/O Request Packets (IRP). Depending on which USB standard the controllers were for, usbport would call into one of three helper drivers, usbehci, usbohci, and usbuhci. The one actually sending those IRPs was usbhub, and these components constitute the lower levels of the USB stack.