技術広報 on Open Source Project

Open Source Projectの技術広報は大事な役割がある。　

技術的な動向は、技術指導者が語るとよい。　

技術広報は、指導者の背景となる情報を整理し、　
Open Source Projectの参加者が道に迷わないようにするとよい。　

GCCとClang/LLVMを例に考えて見る。

||GCC|LLVM|
|:--|:--|:--|　
|home| 60|70|
|usage|70|60|
|Publicity|20|30|

プログラマとしてこの表紙に不満はない。　
まっとうな文章と、まっとうなリンク。　

プログラマ以外に何か訴えるものがあってもいいかもしれない。　

<この項は書きかけです。順次追記します。>

例：

今日から写経でコンパイラを書こう。

最短ビルド時間申告。　

コンパイラ最適化競争。　

いくらでも、お金をかけない広報企画は思いつく。　

open Source Projectには、技術広報が必要だ。

GCC

右端のリンク一覧が何のためにあるかはわかりにくい。　

GCC, the GNU Compiler Collection

The GNU Compiler Collection includes front ends for C, C++, Objective-C, Fortran, Ada, Go, and D, as well as libraries for these languages (libstdc++,...). GCC was originally written as the compiler for the GNU operating system. The GNU system was developed to be 100% free software, free in the sense that it respects the user's freedom.
We strive to provide regular, high quality releases, which we want to work well on a variety of native and cross targets (including GNU/Linux), and encourage everyone to contribute changes or help testing GCC. Our sources are readily and freely available via Git and weekly snapshots.
Major decisions about GCC are made by the steering committee, guided by the mission statement.

About GCC

Mission
Releases
Snapshots
Mailing lists
Contributors
@gnutools on Twitter@gnutools
Donate to GNU Toolchain Fund

Documentation

Installation
· Platforms
Manual
FAQ
Wiki
Pointers

Download

Mirrors
Binaries

Sources

Git
...write access
Rsync

Development

Plan & Timeline
Contributing
Why contribute?
Open projects
Front ends
Back ends
Extensions
Benchmarks
Translations

Bugs

Known bugs
How to report
Bug tracker
· Management

footnote

For questions related to the use of GCC, please consult these web pages and the GCC manuals. If that fails, the [e-mail] mailing list might help. Comments on these web pages and the development of GCC are welcome on our developer list at [e-mail]. All of our lists have public archives.
Copyright (C) Free Software Foundation, Inc. Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved.
These pages are maintained by the GCC team. Last modified 2022-11-14.

LLVM/clang

The LLVM Compiler Infrastructure

LLVM Overview

The LLVM Project is a collection of modular and reusable compiler and toolchain technologies. Despite its name, LLVM has little to do with traditional virtual machines. The name "LLVM" itself is not an acronym; it is the full name of the project.
LLVM began as a research project at the University of Illinois, with the goal of providing a modern, SSA-based compilation strategy capable of supporting both static and dynamic compilation of arbitrary programming languages. Since then, LLVM has grown to be an umbrella project consisting of a number of subprojects, many of which are being used in production by a wide variety of commercial and open source projects as well as being widely used in academic research. Code in the LLVM project is licensed under the "Apache 2.0 License with LLVM exceptions"
The primary sub-projects of LLVM are:
The LLVM Core libraries provide a modern source- and target-independent optimizer, along with code generation support for many popular CPUs (as well as some less common ones!) These libraries are built around a well specified code representation known as the LLVM intermediate representation ("LLVM IR"). The LLVM Core libraries are well documented, and it is particularly easy to invent your own language (or port an existing compiler) to use LLVM as an optimizer and code generator.
Clang is an "LLVM native" C/C++/Objective-C compiler, which aims to deliver amazingly fast compiles, extremely useful error and warning messages and to provide a platform for building great source level tools. The Clang Static Analyzer and clang-tidy are tools that automatically find bugs in your code, and are great examples of the sort of tools that can be built using the Clang frontend as a library to parse C/C++ code.
The LLDB project builds on libraries provided by LLVM and Clang to provide a great native debugger. It uses the Clang ASTs and expression parser, LLVM JIT, LLVM disassembler, etc so that it provides an experience that "just works". It is also blazing fast and much more memory efficient than GDB at loading symbols.
The libc++ and libc++ ABI projects provide a standard conformant and high-performance implementation of the C++ Standard Library, including full support for C++11 and C++14.
The compiler-rt project provides highly tuned implementations of the low-level code generator support routines like "__fixunsdfdi" and other calls generated when a target doesn't have a short sequence of native instructions to implement a core IR operation. It also provides implementations of run-time libraries for dynamic testing tools such as AddressSanitizer, ThreadSanitizer, MemorySanitizer, and DataFlowSanitizer.
The MLIR subproject is a novel approach to building reusable and extensible compiler infrastructure. MLIR aims to address software fragmentation, improve compilation for heterogeneous hardware, significantly reduce the cost of building domain specific compilers, and aid in connecting existing compilers together.
The OpenMP subproject provides an OpenMP runtime for use with the OpenMP implementation in Clang.
The polly project implements a suite of cache-locality optimizations as well as auto-parallelism and vectorization using a polyhedral model.
The libclc project aims to implement the OpenCL standard library.
The klee project implements a "symbolic virtual machine" which uses a theorem prover to try to evaluate all dynamic paths through a program in an effort to find bugs and to prove properties of functions. A major feature of klee is that it can produce a testcase in the event that it detects a bug.
The LLD project is a new linker. That is a drop-in replacement for system linkers and runs much faster.
The BOLT project is a post-link optimizer. It achieves the improvements by optimizing application's code layout based on execution profile gathered by sampling profiler.
In addition to official subprojects of LLVM, there are a broad variety of other projects that use components of LLVM for various tasks. Through these external projects you can use LLVM to compile Ruby, Python, Haskell, Rust, D, PHP, Pure, Lua, Julia, and a number of other languages. A major strength of LLVM is its versatility, flexibility, and reusability, which is why it is being used for such a wide variety of different tasks: everything from doing light-weight JIT compiles of embedded languages like Lua to compiling Fortran code for massive super computers.
As much as everything else, LLVM has a broad and friendly community of people who are interested in building great low-level tools. If you are interested in getting involved, a good first place is to skim the LLVM Blog and join LLVM Discourse. For information on how to send in a patch, get commit access, and copyright and license topics, please see the LLVM Developer Policy.

Countdown Calendar 2022

今年企画した6つのCountdown Calendarと、それぞれの記事一つをご紹介します。

AUTOSAR Countdown Calendar 2022

AUTOSAR References to ISO, IEC, ITU, IEEE, RFC and SEA etc.

Automotive Handbook Countdown Calendar 2022

Basic principles, ボッシュ自動車handbook(英語)11版まとめ<2>

2022 いいねをいただいた記事ランキング(O.K.版) Countdown Calendar 2022

2022年１月下旬　いいねをいただいた記事　16

AdCale(O.K.) Countdown Calendar 2022

「会議は15分未満」に。小耳にはさんだ話。

ABC language (O.K.版） Advent Calendar 2022

LLVMソースコードのコンパイルをしようと思ってハマった罠とそこから脱出するための努力

ABC maker(O.K版） Advent Calendar 2022

JAXA/IPA クリティカルソフトウェアワークショップ WOCS言語関連発表(改定版)

CountdownCalendar2022 報告

誤差の評価が苦手（専門分野以外）

＜この記事は個人の過去の経験に基づく個人の感想です。現在所属する組織、業務とは関係がありません。＞

文書履歴(document history)

ver. 0.01 初稿 20221229
ver. 0.02 URL追記　20221231

最後までおよみいただきありがとうございました。

いいね　💚、フォローをお願いします。

Thank you very much for reading to the last sentence.

Please press the like icon 💚　and follow me for your happy life.