Notes by djb on using Fil-C (2025) - \u30dd\u30b1\u30b3\u30f3<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/cr.yp.to\/2025\/fil-c.html\" \/>\n<meta property=\"og:locale\" content=\"ja_JP\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Notes by djb on using Fil-C (2025) - \u30dd\u30b1\u30b3\u30f3\" \/>\n<meta property=\"og:description\" content=\"I’m impressed with the level of compatibility of the new memory-safe C\/C++ compiler Fil-C (filcc, fil++) […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/cr.yp.to\/2025\/fil-c.html\" \/>\n<meta property=\"og:site_name\" content=\"\u30dd\u30b1\u30b3\u30f3\" \/>\n<meta property=\"article:published_time\" content=\"2025-11-03T04:47:50+00:00\" \/>\n<meta name=\"author\" content=\"info@pokecon.jp\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"\u57f7\u7b46\u8005\" \/>\n\t<meta name=\"twitter:data1\" content=\"info@pokecon.jp\" \/>\n\t<meta name=\"twitter:label2\" content=\"\u63a8\u5b9a\u8aad\u307f\u53d6\u308a\u6642\u9593\" \/>\n\t<meta name=\"twitter:data2\" content=\"17\u5206\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/cr.yp.to\\\/2025\\\/fil-c.html#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/pokecon.jp\\\/job\\\/22049\\\/\"},\"author\":{\"name\":\"info@pokecon.jp\",\"@id\":\"https:\\\/\\\/pokecon.jp\\\/job\\\/#\\\/schema\\\/person\\\/16c9f07b1ba984d165d9aee259bda997\"},\"headline\":\"Notes by djb on using Fil-C (2025)\",\"datePublished\":\"2025-11-03T04:47:50+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/pokecon.jp\\\/job\\\/22049\\\/\"},\"wordCount\":2320,\"articleSection\":[\"\u306f\u3066\u306a\u30d6\u30ed\u30b0\"],\"inLanguage\":\"ja\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/pokecon.jp\\\/job\\\/22049\\\/\",\"url\":\"https:\\\/\\\/cr.yp.to\\\/2025\\\/fil-c.html\",\"name\":\"Notes by djb on using Fil-C (2025) - \u30dd\u30b1\u30b3\u30f3\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/pokecon.jp\\\/job\\\/#website\"},\"datePublished\":\"2025-11-03T04:47:50+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/pokecon.jp\\\/job\\\/#\\\/schema\\\/person\\\/16c9f07b1ba984d165d9aee259bda997\"},\"breadcrumb\":{\"@id\":\"https:\\\/\\\/cr.yp.to\\\/2025\\\/fil-c.html#breadcrumb\"},\"inLanguage\":\"ja\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/cr.yp.to\\\/2025\\\/fil-c.html\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/cr.yp.to\\\/2025\\\/fil-c.html#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"\u30db\u30fc\u30e0\",\"item\":\"https:\\\/\\\/pokecon.jp\\\/job\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Notes by djb on using Fil-C (2025)\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/pokecon.jp\\\/job\\\/#website\",\"url\":\"https:\\\/\\\/pokecon.jp\\\/job\\\/\",\"name\":\"\u30dd\u30b1\u30b3\u30f3\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/pokecon.jp\\\/job\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"ja\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/pokecon.jp\\\/job\\\/#\\\/schema\\\/person\\\/16c9f07b1ba984d165d9aee259bda997\",\"name\":\"info@pokecon.jp\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"ja\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/2b0549cd9f7907c092ca5fbb283baf72337f235726e4b46fa39ec0b701ac2fe2?s=96&d=wavatar&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/2b0549cd9f7907c092ca5fbb283baf72337f235726e4b46fa39ec0b701ac2fe2?s=96&d=wavatar&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/2b0549cd9f7907c092ca5fbb283baf72337f235726e4b46fa39ec0b701ac2fe2?s=96&d=wavatar&r=g\",\"caption\":\"info@pokecon.jp\"},\"url\":\"https:\\\/\\\/pokecon.jp\\\/job\\\/author\\\/infopokecon-jp\\\/\"}]}<\/script>\n","yoast_head_json":{"title":"Notes by djb on using Fil-C (2025) - \u30dd\u30b1\u30b3\u30f3","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/cr.yp.to\/2025\/fil-c.html","og_locale":"ja_JP","og_type":"article","og_title":"Notes by djb on using Fil-C (2025) - \u30dd\u30b1\u30b3\u30f3","og_description":"I’m impressed with the level of compatibility of the new memory-safe C\/C++ compiler Fil-C (filcc, fil++) […]","og_url":"https:\/\/cr.yp.to\/2025\/fil-c.html","og_site_name":"\u30dd\u30b1\u30b3\u30f3","article_published_time":"2025-11-03T04:47:50+00:00","author":"info@pokecon.jp","twitter_card":"summary_large_image","twitter_misc":{"\u57f7\u7b46\u8005":"info@pokecon.jp","\u63a8\u5b9a\u8aad\u307f\u53d6\u308a\u6642\u9593":"17\u5206"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/cr.yp.to\/2025\/fil-c.html#article","isPartOf":{"@id":"https:\/\/pokecon.jp\/job\/22049\/"},"author":{"name":"info@pokecon.jp","@id":"https:\/\/pokecon.jp\/job\/#\/schema\/person\/16c9f07b1ba984d165d9aee259bda997"},"headline":"Notes by djb on using Fil-C (2025)","datePublished":"2025-11-03T04:47:50+00:00","mainEntityOfPage":{"@id":"https:\/\/pokecon.jp\/job\/22049\/"},"wordCount":2320,"articleSection":["\u306f\u3066\u306a\u30d6\u30ed\u30b0"],"inLanguage":"ja"},{"@type":"WebPage","@id":"https:\/\/pokecon.jp\/job\/22049\/","url":"https:\/\/cr.yp.to\/2025\/fil-c.html","name":"Notes by djb on using Fil-C (2025) - \u30dd\u30b1\u30b3\u30f3","isPartOf":{"@id":"https:\/\/pokecon.jp\/job\/#website"},"datePublished":"2025-11-03T04:47:50+00:00","author":{"@id":"https:\/\/pokecon.jp\/job\/#\/schema\/person\/16c9f07b1ba984d165d9aee259bda997"},"breadcrumb":{"@id":"https:\/\/cr.yp.to\/2025\/fil-c.html#breadcrumb"},"inLanguage":"ja","potentialAction":[{"@type":"ReadAction","target":["https:\/\/cr.yp.to\/2025\/fil-c.html"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/cr.yp.to\/2025\/fil-c.html#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"\u30db\u30fc\u30e0","item":"https:\/\/pokecon.jp\/job\/"},{"@type":"ListItem","position":2,"name":"Notes by djb on using Fil-C (2025)"}]},{"@type":"WebSite","@id":"https:\/\/pokecon.jp\/job\/#website","url":"https:\/\/pokecon.jp\/job\/","name":"\u30dd\u30b1\u30b3\u30f3","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/pokecon.jp\/job\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"ja"},{"@type":"Person","@id":"https:\/\/pokecon.jp\/job\/#\/schema\/person\/16c9f07b1ba984d165d9aee259bda997","name":"info@pokecon.jp","image":{"@type":"ImageObject","inLanguage":"ja","@id":"https:\/\/secure.gravatar.com\/avatar\/2b0549cd9f7907c092ca5fbb283baf72337f235726e4b46fa39ec0b701ac2fe2?s=96&d=wavatar&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/2b0549cd9f7907c092ca5fbb283baf72337f235726e4b46fa39ec0b701ac2fe2?s=96&d=wavatar&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/2b0549cd9f7907c092ca5fbb283baf72337f235726e4b46fa39ec0b701ac2fe2?s=96&d=wavatar&r=g","caption":"info@pokecon.jp"},"url":"https:\/\/pokecon.jp\/job\/author\/infopokecon-jp\/"}]}},"_links":{"self":[{"href":"https:\/\/pokecon.jp\/job\/wp-json\/wp\/v2\/posts\/22049","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pokecon.jp\/job\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/pokecon.jp\/job\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/pokecon.jp\/job\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/pokecon.jp\/job\/wp-json\/wp\/v2\/comments?post=22049"}],"version-history":[{"count":1,"href":"https:\/\/pokecon.jp\/job\/wp-json\/wp\/v2\/posts\/22049\/revisions"}],"predecessor-version":[{"id":22050,"href":"https:\/\/pokecon.jp\/job\/wp-json\/wp\/v2\/posts\/22049\/revisions\/22050"}],"wp:attachment":[{"href":"https:\/\/pokecon.jp\/job\/wp-json\/wp\/v2\/media?parent=22049"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/pokecon.jp\/job\/wp-json\/wp\/v2\/categories?post=22049"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/pokecon.jp\/job\/wp-json\/wp\/v2\/tags?post=22049"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}

\n
\n
\n<\/p>\n

<\/head>
\n<\/p>\n

\nI’m impressed with the level of compatibility
\nof the new memory-safe C\/C++ compiler
\nFil-C<\/a>
\n(filcc, fil++).
\nMany libraries and applications that I’ve tried
\nwork under Fil-C without changes, and the exceptions haven’t been hard to get working.\n<\/p>\n

\nI’ve started accumulating miscellaneous notes on this page regarding usage of Fil-C.
\nMy selfish objective here is to protect various machines that I manage
\nby switching them over to code compiled with Fil-C,
\nbut maybe you’ll find something useful here too.\n<\/p>\n

\nTimings below are from a mini-PC named phoenix<\/tt> except where otherwise mentioned. \nThis mini-PC has a 6-core (12-thread) AMD Ryzen 5 7640HS (Zen 4) CPU, 12GB RAM, and 36GB swap. \nThe OS is Debian 13. \n(I normally run LTS software, \nperiodically upgrading from software that’s 4\u20135 years old such as Debian 11 today \nto software that’s 2\u20133 years old such as Debian 12 today; \nbut some of the packages included in Fil-C expect newer utilities to be available.)\n<\/p>\n

\nRelated:\n<\/p>\n

\n

\nI’ve posted a \nscript<\/a> \nto help auditors see how Fil-C differs from upstream sources (clang, glibc, …).\n<\/li>\n \nI’ve posted a self-contained \nfilian-install-compiler<\/tt><\/a> \nscript \n(replacing the \n20251029 version<\/a>) \nto download+compile+install Fil-C on Debian 13 in what I think are Debian-appropriate locations, \nalong with glibc and binutils compiled with Fil-C. \nA run took 86 minutes real time (for 477 minutes user time and 52 minutes system time).\n<\/li>\n \nI’ve posted the start of a \nfilian-install-packages<\/tt><\/a> \nscript to download+compile+install Debian source packages, using Fil-C as the compiler \n(after filian-install-compiler<\/tt> has finished). \nThis script has various limitations that need fixing, \nbut it does work for a few packages already \n(e.g., .\/filian-install-packages bzip2<\/tt>), \nafter the installation of dh-exec<\/tt> etc. described below.\n<\/li>\n \nI’ve posted a \ngraph<\/a> \nshowing nearly 9000 microbenchmarks of Fil-C vs. clang on cryptographic software (each run pinned to 1 core on the same Zen 4). \nTypically code compiled with Fil-C takes between 1x and 4x as many cycles as the same code compiled with clang.\n<\/li>\n<\/ul>\n\nAnother way to run Fil-C is via \nFilnix<\/a> \nfrom Mikael Brockman. \nFor example, \nan unprivileged user under Debian 12 with about 10GB of free disk space \ncan download, compile, and install Fil-C, \nand run a Fil-C-compiled Nethack, as follows:\n<\/p>\n unshare --user --pid echo YES # just to test\ngit clone https:\/\/github.com\/nix-community\/nix-user-chroot\ncd nix-user-chroot\ncargo build --release\nmkdir -m 0755 ~\/nix\n~\/nix-user-chroot\/target\/release\/nix-user-chroot ~\/nix \\\n bash -c 'curl -L https:\/\/nixos.org\/nix\/install | sh'\nenv TERM=vt102 \\\n ~\/nix-user-chroot\/target\/release\/nix-user-chroot ~\/nix \\\n ~\/nix\/store\/*-nix-2*\/bin\/nix \\\n --extra-experimental-features 'nix-command flakes' \\\n run 'github:mbrock\/filnix#nethack'\n<\/code><\/pre>\n\nCurrent recommendations for things to do at the beginning as root<\/tt>:\n<\/p>\nmkdir -p \/var\/empty\napt install \\\n autoconf-dickey build-essential bison clang cmake flex gawk \\\n gettext ninja-build patchelf quilt ruby texinfo time\n<\/code><\/pre>\n\nI created an unprivileged filc<\/tt> user. \nEverything else is as that user.\n<\/p>\n \nI downloaded the Fil-C source package:\n<\/p>\ngit clone https:\/\/github.com\/pizlonator\/fil-c.git\ncd fil-c\n<\/code><\/pre>\n\nThis isn’t just the compiler; \nthere’s also glibc and quite a few higher-level libraries and applications. \nThere are also binary Fil-C packages, \nbut I’ve worked primarily with the source package at this point.\n<\/p>\n \nI compiled Fil-C and glibc:\n<\/p>\ntime .\/build_all_fast_glibc.sh\n<\/code><\/pre>\n\nThere are also options to use musl instead of glibc, \nbut musl is incompatible with some of the packages shipped with Fil-C: \nattr<\/tt> needs basename<\/tt>, \nelfutils<\/tt> needs argp_parse<\/tt>, \nsed<\/tt>‘s test suite needs the glibc variant of calloc<\/tt>, \nand \nvim<\/tt>‘s build needs iconv<\/tt> \nto be able to convert from CP932 to UTF-8.\n<\/p>\n \nI had originally configured the server phoenix<\/tt> with only 12GB swap. \nI then had to restart .\/build_all_fast_glibc.sh<\/tt> a few times \nbecause the Fil-C compilation ran out of memory. \nSwitching to 36GB swap made everything work with no restarts; \nmonitoring showed that almost 19GB swap (plus 12GB RAM) was used at one point. \nA larger server, 128 cores with 512GB RAM, took 8 minutes for Fil-C plus 6 minutes for musl, \nwith no restarts needed.\n<\/p>\n\nFil-C includes a \n.\/build_all_slow.sh<\/tt> \nthat builds many more libraries and applications \n(sometimes with patches from the Fil-C author). \nI wrote a replacement script \nhttps:\/\/cr.yp.to\/2025\/build-parallel-20251023.py<\/a> \nwith the following differences:\n<\/p>\n \nThe build-parallel<\/tt> script \n runs through everything, putting results into build\/logs\/*<\/tt>, \n whereas build_all_slow<\/tt> stops at the first error.\n<\/li>\n The build-parallel<\/tt> script tries to use multiple cores, \n while build_all_slow<\/tt> runs through targets serially, \n parallelizing only to the extent that each target’s build mechanism is parallelized.\n<\/li>\nThe build-parallel<\/tt> script might produce wrong results if it’s parallelizing things \n that shouldn’t be parallelized. \n But this should be easy to fix via tweaking the dependencies listed in the script.\n<\/li>\n<\/ul>\n\nOn phoenix<\/tt>, \nrunning \ntime PATH=\"$HOME\/bin:$HOME\/fil-c\/build\/bin:$HOME\/fil-c\/pizfix\/bin:$PATH\" .\/build-parallel.py<\/tt> \nwent through 61 targets in 101 minutes real time (467 minutes user time, 55 minutes system time), \nsuccessfully compiling 60 of them.\n<\/p>\n \nlibcap.<\/b> \nThis is the one that didn’t compile: \n\/home\/filc\/fil-c\/pizfix\/bin\/ld: \/usr\/libexec\/gcc\/x86_64-linux-gnu\/14\/liblto_plugin.so: error loading plugin: libc.so.6: cannot open shared object file: No such file or directory<\/tt>\n<\/p>\n \nutil-linux.<\/b> \nI skipped this one. \nIt does compile, \nbut the compiled taskset<\/tt> utility needs to be patched to use \nsched_getaffinity<\/tt> and sched_setaffinity<\/tt> \nas library functions rather than via syscall<\/tt>, \nor Fil-C needs to be patched for those syscalls. \nThis is an issue for build-parallel<\/tt> \nsince build-parallel<\/tt> relies on taskset<\/tt>; \nmaybe build-parallel<\/tt> should instead use Python’s affinity functions.\n<\/p>\n \n \nattr, bash, benchmarks, binutils, bison, brotli, bzip2, bzip3, check, cmake, coreutils, cpython, curl, dash, diffutils, elfutils, emacs, expat, ffi, gettext, git, \ngmp, grep, icu, jpeg-6b, libarchive, libcap, libedit, libevent, libpipeline, libuev, libuv, lua, lz4, m4, make, mg, ncurses, nghttp2, openssh, openssl, pcre2, pcre, \nperl, pkgconf, procps, quickjs, sed, shadow, simdutf, sqlite, tcl, tmux, toybox, vim, wg14_signals, xml_parser, xz, zlib, zsh, zstd.<\/b> \nNo problems encountered so far \n(given whatever patches were already applied from the Fil-C author!). \nThe benchmarks package is supplied with Fil-C and does a few miscellaneous measurements.\n<\/p>\n \nI did \nexport PATH=\"$HOME\/bin:$HOME\/fil-c\/build\/bin:$HOME\/fil-c\/pizfix\/bin:$PATH\"<\/tt> \nbefore these.\n<\/p>\n \nboost 1.89.0<\/b>: \nSeems to mostly work. \nMost of the package is header-only; \na few simple tests worked fine.\n<\/p>\n \nI also looked a bit at the compiled parts. \nRunning \n.\/bootstrap.sh --with-toolset=clang --prefix=$HOME<\/tt> \nran into vfork<\/tt>, \nwhich Fil-C doesn’t support, \nbut editing \ntools\/build\/src\/engine\/execunix.cpp<\/tt> \nto use defined(__APPLE__) || defined(__FILC__)<\/tt> \nfor the no-fork test got past this.\n<\/p>\n \nRunning .\/b2 install --prefix=$HOME toolset=clang address-model=64 architecture=x86_64 binary-format=elf<\/tt> \nproduced an error message since I should have said x86<\/tt> instead of x86_64<\/tt>; \nFil-C said it caught a safety issue in the b2<\/tt> program after the error message: \nfilc safety error: argument size mismatch (actual = 8, expected = 16)<\/tt>. \nI didn’t compile with debugging so Fil-C didn’t say where this is in b2<\/tt>.\n<\/p>\n \ncdb-20251021<\/b>: \nSeems to work. \nOne regression test, an artificial out-of-memory regression test, \ncurrently produces a different error message with Fil-C: \nfilc panic: src\/libpas\/pas_compact_heap_reservation.c:65: pas_aligned_allocation_result pas_compact_heap_reservation_try_allocate(size_t, size_t): \nassertion page_result.result failed.<\/tt>\n<\/p>\n \nlibcpucycles-20250925<\/b>: \nSeems to work. \nI commented out the first three lines of cpucycles\/options<\/tt>.\n<\/p>\n\nlibgc<\/b>: \nI replaced this with a small gcshim package \n(https:\/\/cr.yp.to\/2025\/gcshim-20251022.tar.gz<\/a>) \nthat simply calls malloc<\/tt> etc. \nSo far this seems to be an adequate replacement. \n(Fil-C includes a garbage collector.)\n<\/p>\n \nlibntruprime-20241021<\/b>: \nSeems to work after a few tweaks but I didn’t collect full notes yet. \nchmod +t crypto_hashblocks\/sha512\/avx2<\/tt> disables assembly and makes things compile; \nconfigured with --no-valgrind<\/tt> since Fil-C doesn’t support valgrind; \ndid a bit more tweaking to make cpuid<\/tt> work.\n<\/p>\n \nlpeg-1.1.0:<\/b> \nCompiles, maybe works (depends on lua, dependency of neovim):\n<\/p>\n cd\nPREFIX=$(dirname $(dirname $(which lua)))\nwget https:\/\/www.inf.puc-rio.br\/~roberto\/lpeg\/lpeg-1.1.0.tar.gz\ntar -xf lpeg-1.1.0.tar.gz\ncd lpeg-1.1.0\nmake CC=`which filcc` DLLFLAGS='-shared -fPIC' test\ncp lpeg.so $PREFIX\/lib\n<\/code><\/pre>\n\nluv-1.51.0:<\/b> \nCompiles, maybe works (depends on lua, dependency of neovim):\n<\/p>\ncd\nPREFIX=$(dirname $(dirname $(which lua)))\nwget https:\/\/github.com\/luvit\/luv\/releases\/download\/1.51.0-1\/luv-1.51.0-1.tar.gz\ntar -xf luv-1.51.0-1.tar.gz\ncd luv-1.51.0-1\nmkdir build\ncd build\nLUA_DIR=$HOME\/fil-c\/projects\/lua-5.4.7\n# lua install should probably do this:\ncp $LUA_DIR\/lua.h $PREFIX\/include\/\ncp $LUA_DIR\/lauxlib.h $PREFIX\/include\/\ncp $LUA_DIR\/luaconf.h $PREFIX\/include\/\ncp $LUA_DIR\/lualib.h $PREFIX\/include\/\n# and then:\ncmake -DCMAKE_C_COMPILER=`which filcc` -DCMAKE_INSTALL_PREFIX=$PREFIX -DWITH_LUA_ENGINE=Lua -DLUA_DIR=$HOME\/fil-c\/projects\/lua-5.4.7\/ ..\nmake test\nmake install\n<\/code><\/pre>\n\nmutt-2-2-15-rel<\/b> (depends on ncurses):\n<\/p>\nwget https:\/\/github.com\/muttmua\/mutt\/archive\/refs\/tags\/mutt-2-2-15-rel.tar.gz\ntar -xf mutt-2-2-15-rel.tar.gz\ncd mutt-mutt-2-2-15-rel\nCC=`which clang` .\/prepare --prefix=$HOME\/fil-c\/pizfix --with-homespool\nmake -j12 install\n<\/code><\/pre>\nSeems to work, at least for reading email.<\/p>\n \ntig<\/b> (depends on ncurses and maybe more):\n<\/p>\nwget https:\/\/github.com\/jonas\/tig\/releases\/download\/tig-2.6.0\/tig-2.6.0.tar.gz\ntar -xf tig-2.6.0.tar.gz\ncd tig-2.6.0\nCC=`which filcc` .\/configure --prefix=$(dirname $(dirname $(which git)))\nmake -j12\nmake test\nmake -j12 install\n<\/code><\/pre>\nSeems to work, at least for viewing the Fil-C repo.<\/p>\n \nw3m<\/b> (depends on gcshim and ncurses): \nSeems to work. \nI tried the Debian version: \ngit clone https:\/\/salsa.debian.org\/debian\/w3m.git<\/tt>. \nI used CFLAGS=-Wno-incompatible-function-pointer-types<\/tt> \n(which is probably needed for clang anyway even without Fil-C).\n<\/p>\n \nI’ve built and installed some replacement Debian packages using Fil-C as the compiler on a Debian 13 machine, \nas explained below. \nHopefully this can rapidly scale to many packages, \ntaking advantage of the basic compile-install-test knowledge already built into Debian source packages, \nalthough some packages will take more work because they need extra patches to work with Fil-C.\n<\/p>\n \nStructure.<\/b> \nDebian already understands how to have packages for multiple architectures (ABIs; Debian “ports”) installed at once. \nFor example, \ndpkg --add-architecture i386; apt update; apt install bash:i386<\/tt> \ninstalls a 32-bit version of bash, \nreplacing the usual 64-bit version; \nyou can do apt install bash:amd64<\/tt> to revert to the 64-bit version. \nMeanwhile the 32-bit libraries and 64-bit libraries are installed in separate locations, \nbasically \n\/lib\/i386-linux-gnu<\/tt> \nor \n\/usr\/lib\/i386-linux-gnu<\/tt> \nvs. \n\/lib\/x86_64-linux-gnu<\/tt> \nor \n\/usr\/lib\/x86_64-linux-gnu<\/tt>. \n(On Debian 11 and newer, and on Ubuntu 22.04 and newer, \n\/lib<\/tt> is symlinked to \/usr\/lib<\/tt>.)\n<\/p>\n \nI’m following this model for plugging Fil-C into Debian: \nthe goal is for apt install bash:amd64fil0<\/tt> \nto install a Fil-C-compiled (amd64fil0<\/tt>) version of bash, \nreplacing the usual (amd64<\/tt>) version of bash, \nwhile the amd64<\/tt> and amd64fil0<\/tt> libraries are installed in separate locations.\n<\/p>\n\nThe include-file complication.<\/b> \nDebian \nexpects<\/a> \nlibrary packages compiled for multiple ABIs \nto all provide the same include files: \nfor example, \/usr\/include\/ncurses.h<\/tt> \nis provided by libncurses-dev:i386<\/tt>, libncurses-dev:amd64<\/tt>, etc. \nThis is safe because Debian forces \nlibncurses-dev:i386<\/tt> and libncurses-dev:amd64<\/tt> and so on \nto all have the same version. \nAn occasional package with ABI-dependent include files \ncan still use \/usr\/include\/x86_64-linux-gnu<\/tt> etc.\n<\/p>\n \nFil-C instead omits \/usr\/include<\/tt> \nin favor of a Fil-C-specific directory \n(which will typically be different from \/usr\/include<\/tt>: \neven if Fil-C is compiled with glibc, \nprobably the glibc version won’t be the same as in \/usr\/include<\/tt>). \nThis difference is the top source of messiness below. \nI’m planning to tweak the Fil-C driver to use \/usr\/include<\/tt> on Debian. \n[This is done in the filian-install-compiler<\/tt> script.]\n<\/p>\n \nSomething else I’m planning to tweak is Fil-C’s glibc compilation, \nso that it uses the final system prefix. \n[This is also done in the filian-install-compiler<\/tt> script.]\nThe approach described below instead requires \n\/home\/filian\/fil-c<\/tt> to stay in place \nfor compiling and running programs.\n<\/p>\n \nBuilding Debian packages.<\/b> \nHow does Debian package building work? \nFirst, more packages to install as root:\n<\/p>\n apt install dpkg-dev devscripts docbook2x \\\n dh-exec dh-python python3-setuptools fakeroot \\\n sbuild mmdebstrap uidmap piuparts\n<\/code><\/pre>\n\nDebian has \nmultiple options<\/a> \nfor building a package. \nThe option that has the best isolation, \nand that Debian uses to continually build new packages for distribution, \nis sbuild, \nbut for fast development I’ll focus on directly using the lower-level \ndpkg-buildpackage.\n<\/p>\n \nBaseline 1: using sbuild without Fil-C.<\/b> \nIn case you do want to try sbuild, \nhere’s the basic setup, \nand then an example of building a small package (tinycdb):\n<\/p>\n mkdir -p ~\/shared\/sbuild\ntime mmdebstrap --include=ca-certificates --skip=output\/dev --variant=buildd unstable ~\/shared\/sbuild\/unstable-amd64.tar.zst https:\/\/deb.debian.org\/debian\n\nmkdir -p ~\/.config\/sbuild\ncat ~\/.config\/sbuild\/config.pl\n$chroot_mode=\"unshare\";\n$external_commands = { \"build-failed-commands\" => [ [ '%SBUILD_SHELL' ] ] };\n$build_arch_all = 1;\n$build_source = 1;\n$source_only_changes = 1;\n$run_lintian = 1;\n$lintian_opts = ['--display-info', '--verbose', '--fail-on', 'error,warning', '--info'];\n$run_autopkgtest = 1;\n$run_piuparts = 1;\n$piuparts_opts = ['--no-eatmydata', '--distribution=%r', '--fake-essential-packages=systemd-sysv'];\nEOF\n\nmkdir -p ~\/shared\/packages\ncd ~\/shared\/packages\napt source tinycdb\ncd tinycdb-*\/\ntime sbuild\n<\/code><\/pre>\n\nBaseline 2: using dpkg-buildpackage without Fil-C.<\/b> \nHere’s what it looks like compiling the same small package with dpkg-buildpackage:\n<\/p>\nmkdir -p ~\/shared\/packages\ncd ~\/shared\/packages\napt source tinycdb\ncd tinycdb-*\/\ntime dpkg-buildpackage -us -uc -b\n<\/code><\/pre>\n\nThe goal: Using dpkg-buildpackage with Fil-C.<\/b> \nAs root, teach dpkg basic features of the new architecture, \nimitating the current line \namd64 x86_64 (amd64|x86_64) 64 little<\/tt> \nin the same file:\n<\/p>\necho amd64fil0 x86_64+fil0 amd64fil0 64 little >> \/usr\/share\/dpkg\/cputable\n<\/code><\/pre>\n\nAlso, allow apt<\/tt> to install packages compiled for this architecture \n(beware that this will also later make apt update<\/tt> look for that architecture on servers, \nand whimper a bit for not finding it, \nbut nothing breaks):\n<\/p>\ndpkg --add-architecture amd64fil0\n<\/code><\/pre>\n\nAlso, teach autoconf<\/tt> to accept amd64fil0 \n(the third of these lines is what’s critical for Debian builds):\n<\/p>\nsed -i '\/| x86_64 \/ a| x86_64+fil0 \\\\' \/usr\/share\/autoconf\/build-aux\/config.sub\nsed -i '\/| x86_64 \/ a| x86_64+fil0 \\\\' \/usr\/share\/libtool\/build-aux\/config.sub\nsed -i '\/| x86_64 \/ a| x86_64+fil0 \\\\' \/usr\/share\/misc\/config.sub\n<\/code><\/pre>\n\n[Not necessary if you’ve used filian-install-compiler<\/tt>:]\nAs a filian<\/tt> user, \ncompile Fil-C and its standard library:\n<\/p>\ncd\ngit clone https:\/\/github.com\/pizlonator\/fil-c.git\ncd fil-c\ntime .\/build_all_fast_glibc.sh\n<\/code><\/pre>\n\n[Not necessary if you’ve used filian-install-compiler<\/tt>:]\nAs root, \ncopy Fil-C and its standard library into system locations:\n<\/p>\nmkdir -p \/usr\/libexec\/fil\/amd64\/compiler\ntime cp -r \/home\/filian\/fil-c\/pizfix \/usr\/libexec\/fil\/amd64\/\nrm -rf \/usr\/lib\/x86_64+fil0-linux-gnu\nmv \/usr\/libexec\/fil\/amd64\/pizfix\/lib \/usr\/lib\/x86_64+fil0-linux-gnu\nln -s \/usr\/lib\/x86_64+fil0-linux-gnu \/usr\/libexec\/fil\/amd64\/pizfix\/lib\nrm -rf \/usr\/include\/x86_64+fil0-linux-gnu\nmv \/usr\/libexec\/fil\/amd64\/pizfix\/include \/usr\/include\/x86_64+fil0-linux-gnu\nln -s \/usr\/include\/x86_64+fil0-linux-gnu \/usr\/libexec\/fil\/amd64\/pizfix\/include\ntime cp -r \/home\/filian\/fil-c\/build\/bin \/usr\/libexec\/fil\/amd64\/compiler\/\ntime cp -r \/home\/filian\/fil-c\/build\/include \/usr\/libexec\/fil\/amd64\/compiler\/\ntime cp -r \/home\/filian\/fil-c\/build\/lib \/usr\/libexec\/fil\/amd64\/compiler\/\n( echo '#!\/bin\/sh'\n echo 'exec \/usr\/libexec\/fil\/amd64\/compiler\/bin\/filcc \"$@\"' ) > \/usr\/bin\/x86_64+fil0-linux-gnu-gcc\nchmod 755 \/usr\/bin\/x86_64+fil0-linux-gnu-gcc\n( echo '#!\/bin\/sh'\n echo 'exec \/usr\/libexec\/fil\/amd64\/compiler\/bin\/fil++ \"$@\"' ) > \/usr\/bin\/x86_64+fil0-linux-gnu-g++\nchmod 755 \/usr\/bin\/x86_64+fil0-linux-gnu-g++\nln -s \/usr\/libexec\/fil\/amd64\/compiler\/bin\/llvm-objdump \/usr\/bin\/x86_64+fil0-linux-gnu-objdump\nln -s x86_64+fil0-linux-gnu-gcc \/usr\/bin\/filcc\nln -s x86_64+fil0-linux-gnu-g++ \/usr\/bin\/fil++\n<\/code><\/pre>\n\nNow, as user filian<\/tt> (or whichever other user), \nlet’s make a little helper script to adjust a Debian source package:\n<\/p>\nmkdir -p $HOME\/bin\n( echo '#!\/bin\/sh'\n echo 'sed -i '\\''s\/^ \$[^\"]*\$$\/ pizlonated_\\1\/'\\'' debian\/*.symbols'\n echo 'find . -name '\\''*.map'\\'' | while read fn'\n echo 'do'\n echo ' awk '\\''{'\n echo ' if ($1 == \"local:\") global = 0'\n echo ' if ($1 == \"}\") global = 0'\n echo ' if (global && NF > 0 && !index($0,\"c++\")) $1 = \"pizlonated_\"$1'\n echo ' if ($1 == \"global:\") global = 1'\n echo ' print'\n echo ' }'\\'' $fn.tmp'\n echo ' mv $fn.tmp $fn'\n echo 'done'\n echo 'find debian -name '\\''*.install'\\'' | while read fn'\n echo 'do'\n echo ' awk '\\''{'\n echo ' if (NF == 2 && $2 == \"usr\/include\") $2 = $2\"\/${DEB_HOST_MULTIARCH}\"'\n echo ' if (NF == 1 && $1 == \"usr\/include\") { $2 = $1\"\/${DEB_HOST_MULTIARCH}\"; $1 = $1\"\/*\" }'\n echo ' print'\n echo ' }'\\'' $fn.tmp'\n echo ' mv $fn.tmp $fn'\n echo 'done'\n) > $HOME\/bin\/fillet\nchmod 755 $HOME\/bin\/fillet\n<\/code><\/pre>\nAnd now let’s try building a small package:<\/p>\nmkdir -p ~\/shared\/packages\ncd ~\/shared\/packages\napt source tinycdb\ncd tinycdb-*\/\n$HOME\/bin\/fillet\ntime env DPKG_GENSYMBOLS_CHECK_LEVEL=0 \\\n DEB_BUILD_OPTIONS='crossbuildcanrunhostbinaries nostrip' \\\n dpkg-buildpackage -d -us -uc -b -a amd64fil0\n<\/code><\/pre>\n\nExplanation of the differences from a normal build:\n<\/p>\n \n\nDEB_BUILD_OPTIONS=nostrip<\/tt> skips removing symbols from binaries, \nin part because Debian’s dh_dwz<\/tt> utility doesn’t currently work with Fil-C, \nin part because we’ll look at symbols later.\n<\/li>\n \nDEB_BUILD_OPTIONS=crossbuildcanrunhostbinaries<\/tt> silences a warning \nabout cross-compilation not necessarily working with tests.\n<\/li>\n \n-a amd64fil0<\/tt> specifies the amd64fil0<\/tt> ABI, \nwhich triggers using the x86_64+fil0-linux-gnu-gcc<\/tt> compiler.\n<\/li>\n \n-d<\/tt> stops dpkg-buildpackage<\/tt> \nfrom checking for dependencies. \n(This doesn’t matter for this package.)\n<\/li>\n \n[Superseded by the binutils<\/tt> patch in in filian-install-compiler<\/tt> starting with version 20251030:]\nThe tweak to *.map<\/tt> in the helper script \ntries to stop Debian from hiding the shared-library symbols after Fil-C mangling.\n<\/li>\n \nThe tweak to *.symbols<\/tt> in the helper script \ntries to notify Debian regarding the expected shared-library symbols after Fil-C mangling. \n[Not necessary given DPKG_GENSYMBOLS_CHECK_LEVEL=0<\/tt>.]\n<\/li>\n \nDPKG_GENSYMBOLS_CHECK_LEVEL=0<\/tt> \nshould stop Debian from complaining that there are wrong symbols.\n<\/li>\n \n[Not necessary if you’ve used filian-install-compiler<\/tt>:]\nThe tweak to *.install<\/tt> in the helper script \ninstalls \/usr\/include\/x86_64+fil0\/cdb.h<\/tt> \n(where Fil-C will see it for programs using this library) \ninstead of \/usr\/include\/cdb.h<\/tt>.\n<\/li>\n<\/ul>\n\nFor me this worked and produced three ..\/*.deb<\/tt> packages. \nInstalling them as root also worked:\n<\/p>\n apt install \/home\/filian\/shared\/packages\/*.deb\n# some sanity checks:\napt list | grep tinycdb\n# prints \"tinycdb\/stable 0.81-2 amd64\" (available package)\n# and prints \"tinycdb\/now 0.81-2 amd64fil0 [installed,local]\"\ndpkg -L tinycdb:amd64fil0\n# lists various files such as \/usr\/bin\/cdb\nnm \/usr\/bin\/cdb\n# shows various symbols including \"pizlonated\" (Fil-C) symbols\nldd \/usr\/bin\/cdb\n# shows dependence on libraries in \/usr\/libexec\/fil\n\/usr\/bin\/cdb -h\n# prints a help message: \"cdb: Constant DataBase\" etc.\n<\/code><\/pre>\n\nCompiling a deliberately wrong test program \nwith the newly installed library also works, \nand triggers Fil-C’s run-time protection:\n<\/p>\n cd \/root\n( echo '#include '\n echo 'int main() { cdb_init(0,0); return 0; }' ) > usecdb.c\nfilcc -o usecdb usecdb.c -lcdb\n.\/usecdb <\/cdb.h><\/code><\/pre>\n\nlibc-dev.<\/b> \nSome packages depend on libc-dev, \nso let’s build a fake libc-dev package \n(probably there’s an easier way to do this):\n<\/p>\n FAKEPACKAGE=libc-dev\nmkdir -p ~\/shared\/packages\/$FAKEPACKAGE\/debian\ncd ~\/shared\/packages\/$FAKEPACKAGE\n( echo $FAKEPACKAGE' (0.0) unstable; urgency=medium'\n echo ''\n echo ' * Initial Release.'\n echo ''\n echo ' -- djb Sun, 26 Oct 2025 16:05:17 +0000'\n) > debian\/changelog\n( echo 'Source: '$FAKEPACKAGE\n echo 'Build-Depends: debhelper-compat (= 13)'\n echo 'Maintainer: djb '\n echo ''\n echo 'Package: '$FAKEPACKAGE\n echo 'Architecture: any'\n echo 'Multi-Arch: same'\n echo 'Description: fake '$FAKEPACKAGE\n) > debian\/control\n( echo '#!\/usr\/bin\/make -f'\n echo ''\n echo 'build-arch build-indep build \\'\n echo 'install-arch install-indep install \\'\n echo 'binary-arch binary-indep binary \\'\n echo ':'\n echo 'Xdh $@' | tr X '\\011'\n echo ''\n echo 'clean:'\n echo 'Xdh_clean' | tr X '\\011'\n) > debian\/rules\ntime env DPKG_GENSYMBOLS_CHECK_LEVEL=0 \\\n DEB_BUILD_OPTIONS='crossbuildcanrunhostbinaries nostrip' \\\n dpkg-buildpackage -d -us -uc -b -a amd64fil0\n<\/djb><\/djb><\/code><\/pre>\n\nncurses.<\/b>\n<\/p>\n mkdir -p ~\/shared\/packages\ncd ~\/shared\/packages\napt source ncurses\ncd ncurses-*\/\n$HOME\/bin\/fillet\ntime env DPKG_GENSYMBOLS_CHECK_LEVEL=0 \\\n DEB_BUILD_OPTIONS='crossbuildcanrunhostbinaries nostrip' \\\n dpkg-buildpackage -d -us -uc -b -a amd64fil0\nrm ..\/ncurses-*deb # apt won't let us touch the binaries\n<\/code><\/pre>\n\nAs root, install the above libraries:\n<\/p>\n apt install \/home\/filian\/shared\/packages\/lib*.deb\n<\/code><\/pre>\n\nlibmd.<\/b> \nSeems to work. \nAt first this didn’t install \nsince the compiled version (for amd64fil0) was 1.1.0-2 \nwhile the installed version (for amd64) was 1.1.0-2+b1. \nDebian requires the same version number across architectures \n(see above regarding include-file compatibility), \nso apt<\/tt> said that 1.1.0-2+b1 breaks 1.1.0-2. \nI resolved this by compiling and installing 1.1.0-2 for both amd64 and amd64fil0. \nThis is a downgrade since “+b” refers to \na “binNMU”, a “binary-only non-maintainer upload”, \na patch beyond the official source; \nI don’t know what the patch is.\n<\/p>\n \nreadline.<\/b> \nNeeds \nln -s \/usr\/include\/readline \/usr\/include\/x86_64+fil0-linux-gnu\/readline<\/tt> \nafter installation. \nCould have tweaks in debian\/rules<\/tt> \n(which seems to predate *.install<\/tt>), \nbut this is in any case an example of the messiness that I’m planning to get rid of.\n<\/p>\n \nlua5.4.<\/b> \nSeems to work. \nDepends on readline.\n<\/p>\n <\/body>\n<\/div>\n\n \u5143\u306e\u8a18\u4e8b\u3092\u78ba\u8a8d\u3059\u308b <\/a><\/p>\n","protected":false},"excerpt":{"rendered":"I’m impressed with the level of compatibility of the new memory-safe C\/C++ compiler Fil-C (filcc, fil++) […]","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[2],"tags":[],"class_list":["post-22049","post","type-post","status-publish","format-standard","hentry","category-hatena-blog"],"acf":[],"yoast_head":"\nNotes by djb on using Fil-C (2025) - \u30dd\u30b1\u30b3\u30f3<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/cr.yp.to\/2025\/fil-c.html\" \/>\n<meta property=\"og:locale\" content=\"ja_JP\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Notes by djb on using Fil-C (2025) - \u30dd\u30b1\u30b3\u30f3\" \/>\n<meta property=\"og:description\" content=\"I’m impressed with the level of compatibility of the new memory-safe C\/C++ compiler Fil-C (filcc, fil++) […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/cr.yp.to\/2025\/fil-c.html\" \/>\n<meta property=\"og:site_name\" content=\"\u30dd\u30b1\u30b3\u30f3\" \/>\n<meta property=\"article:published_time\" content=\"2025-11-03T04:47:50+00:00\" \/>\n<meta name=\"author\" content=\"info@pokecon.jp\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"\u57f7\u7b46\u8005\" \/>\n\t<meta name=\"twitter:data1\" content=\"info@pokecon.jp\" \/>\n\t<meta name=\"twitter:label2\" content=\"\u63a8\u5b9a\u8aad\u307f\u53d6\u308a\u6642\u9593\" \/>\n\t<meta name=\"twitter:data2\" content=\"17\u5206\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/cr.yp.to\\\/2025\\\/fil-c.html#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/pokecon.jp\\\/job\\\/22049\\\/\"},\"author\":{\"name\":\"info@pokecon.jp\",\"@id\":\"https:\\\/\\\/pokecon.jp\\\/job\\\/#\\\/schema\\\/person\\\/16c9f07b1ba984d165d9aee259bda997\"},\"headline\":\"Notes by djb on using Fil-C (2025)\",\"datePublished\":\"2025-11-03T04:47:50+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/pokecon.jp\\\/job\\\/22049\\\/\"},\"wordCount\":2320,\"articleSection\":[\"\u306f\u3066\u306a\u30d6\u30ed\u30b0\"],\"inLanguage\":\"ja\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/pokecon.jp\\\/job\\\/22049\\\/\",\"url\":\"https:\\\/\\\/cr.yp.to\\\/2025\\\/fil-c.html\",\"name\":\"Notes by djb on using Fil-C (2025) - \u30dd\u30b1\u30b3\u30f3\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/pokecon.jp\\\/job\\\/#website\"},\"datePublished\":\"2025-11-03T04:47:50+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/pokecon.jp\\\/job\\\/#\\\/schema\\\/person\\\/16c9f07b1ba984d165d9aee259bda997\"},\"breadcrumb\":{\"@id\":\"https:\\\/\\\/cr.yp.to\\\/2025\\\/fil-c.html#breadcrumb\"},\"inLanguage\":\"ja\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/cr.yp.to\\\/2025\\\/fil-c.html\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/cr.yp.to\\\/2025\\\/fil-c.html#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"\u30db\u30fc\u30e0\",\"item\":\"https:\\\/\\\/pokecon.jp\\\/job\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Notes by djb on using Fil-C (2025)\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/pokecon.jp\\\/job\\\/#website\",\"url\":\"https:\\\/\\\/pokecon.jp\\\/job\\\/\",\"name\":\"\u30dd\u30b1\u30b3\u30f3\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/pokecon.jp\\\/job\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"ja\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/pokecon.jp\\\/job\\\/#\\\/schema\\\/person\\\/16c9f07b1ba984d165d9aee259bda997\",\"name\":\"info@pokecon.jp\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"ja\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/2b0549cd9f7907c092ca5fbb283baf72337f235726e4b46fa39ec0b701ac2fe2?s=96&d=wavatar&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/2b0549cd9f7907c092ca5fbb283baf72337f235726e4b46fa39ec0b701ac2fe2?s=96&d=wavatar&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/2b0549cd9f7907c092ca5fbb283baf72337f235726e4b46fa39ec0b701ac2fe2?s=96&d=wavatar&r=g\",\"caption\":\"info@pokecon.jp\"},\"url\":\"https:\\\/\\\/pokecon.jp\\\/job\\\/author\\\/infopokecon-jp\\\/\"}]}<\/script>\n","yoast_head_json":{"title":"Notes by djb on using Fil-C (2025) - \u30dd\u30b1\u30b3\u30f3","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/cr.yp.to\/2025\/fil-c.html","og_locale":"ja_JP","og_type":"article","og_title":"Notes by djb on using Fil-C (2025) - \u30dd\u30b1\u30b3\u30f3","og_description":"I’m impressed with the level of compatibility of the new memory-safe C\/C++ compiler Fil-C (filcc, fil++) […]","og_url":"https:\/\/cr.yp.to\/2025\/fil-c.html","og_site_name":"\u30dd\u30b1\u30b3\u30f3","article_published_time":"2025-11-03T04:47:50+00:00","author":"info@pokecon.jp","twitter_card":"summary_large_image","twitter_misc":{"\u57f7\u7b46\u8005":"info@pokecon.jp","\u63a8\u5b9a\u8aad\u307f\u53d6\u308a\u6642\u9593":"17\u5206"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/cr.yp.to\/2025\/fil-c.html#article","isPartOf":{"@id":"https:\/\/pokecon.jp\/job\/22049\/"},"author":{"name":"info@pokecon.jp","@id":"https:\/\/pokecon.jp\/job\/#\/schema\/person\/16c9f07b1ba984d165d9aee259bda997"},"headline":"Notes by djb on using Fil-C (2025)","datePublished":"2025-11-03T04:47:50+00:00","mainEntityOfPage":{"@id":"https:\/\/pokecon.jp\/job\/22049\/"},"wordCount":2320,"articleSection":["\u306f\u3066\u306a\u30d6\u30ed\u30b0"],"inLanguage":"ja"},{"@type":"WebPage","@id":"https:\/\/pokecon.jp\/job\/22049\/","url":"https:\/\/cr.yp.to\/2025\/fil-c.html","name":"Notes by djb on using Fil-C (2025) - \u30dd\u30b1\u30b3\u30f3","isPartOf":{"@id":"https:\/\/pokecon.jp\/job\/#website"},"datePublished":"2025-11-03T04:47:50+00:00","author":{"@id":"https:\/\/pokecon.jp\/job\/#\/schema\/person\/16c9f07b1ba984d165d9aee259bda997"},"breadcrumb":{"@id":"https:\/\/cr.yp.to\/2025\/fil-c.html#breadcrumb"},"inLanguage":"ja","potentialAction":[{"@type":"ReadAction","target":["https:\/\/cr.yp.to\/2025\/fil-c.html"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/cr.yp.to\/2025\/fil-c.html#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"\u30db\u30fc\u30e0","item":"https:\/\/pokecon.jp\/job\/"},{"@type":"ListItem","position":2,"name":"Notes by djb on using Fil-C (2025)"}]},{"@type":"WebSite","@id":"https:\/\/pokecon.jp\/job\/#website","url":"https:\/\/pokecon.jp\/job\/","name":"\u30dd\u30b1\u30b3\u30f3","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/pokecon.jp\/job\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"ja"},{"@type":"Person","@id":"https:\/\/pokecon.jp\/job\/#\/schema\/person\/16c9f07b1ba984d165d9aee259bda997","name":"info@pokecon.jp","image":{"@type":"ImageObject","inLanguage":"ja","@id":"https:\/\/secure.gravatar.com\/avatar\/2b0549cd9f7907c092ca5fbb283baf72337f235726e4b46fa39ec0b701ac2fe2?s=96&d=wavatar&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/2b0549cd9f7907c092ca5fbb283baf72337f235726e4b46fa39ec0b701ac2fe2?s=96&d=wavatar&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/2b0549cd9f7907c092ca5fbb283baf72337f235726e4b46fa39ec0b701ac2fe2?s=96&d=wavatar&r=g","caption":"info@pokecon.jp"},"url":"https:\/\/pokecon.jp\/job\/author\/infopokecon-jp\/"}]}},"_links":{"self":[{"href":"https:\/\/pokecon.jp\/job\/wp-json\/wp\/v2\/posts\/22049","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pokecon.jp\/job\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/pokecon.jp\/job\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/pokecon.jp\/job\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/pokecon.jp\/job\/wp-json\/wp\/v2\/comments?post=22049"}],"version-history":[{"count":1,"href":"https:\/\/pokecon.jp\/job\/wp-json\/wp\/v2\/posts\/22049\/revisions"}],"predecessor-version":[{"id":22050,"href":"https:\/\/pokecon.jp\/job\/wp-json\/wp\/v2\/posts\/22049\/revisions\/22050"}],"wp:attachment":[{"href":"https:\/\/pokecon.jp\/job\/wp-json\/wp\/v2\/media?parent=22049"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/pokecon.jp\/job\/wp-json\/wp\/v2\/categories?post=22049"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/pokecon.jp\/job\/wp-json\/wp\/v2\/tags?post=22049"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}