url stringlengths 11 2.25k | text stringlengths 88 50k | ts timestamp[s]date 2026-01-13 08:47:33 2026-01-13 09:30:40 |
|---|---|---|
https://releases.llvm.org/18.1.8/projects/libcxx/docs/index.html | “libc++” C++ Standard Library — libc++ documentation libc++ documentation “libc++” C++ Standard Library Contents   ::   Libc++ 18.0.0 (In-Progress) Release Notes   » “libc++” C++ Standard Library ¶ Overview ¶ libc++ is a new implementation of the C++ standard library, targeting C++11 and above. Features and Goals Correctness as defined by the C++11 standard. Fast execution. Minimal memory use. Fast compile times. ABI compatibility with gcc’s libstdc++ for some low-level features such as exception objects, rtti and memory allocation. Extensive unit tests. Design and Implementation: Extensive unit tests Internal linker model can be dumped/read to textual format Additional linking features can be plugged in as “passes” OS specific and CPU specific code factored out Getting Started with libc++ ¶ Libc++ 18.0.0 (In-Progress) Release Notes Using libc++ Building libc++ Testing libc++ Contributing to libc++ Implementation-defined behavior Modules in libc++ Hardening Modes Release procedure libc++ C++14 Status libc++ C++17 Status libc++ C++20 Status libc++ C++23 Status libc++ C++2c Status libc++ Format Status libc++ Parallelism TS Status (N4808) libc++ Parallel STL Status libc++ Ranges Status libc++ Spaceship Operator Status (operator<=>) libc++ Zip Status (P2321R2) Current Status ¶ After its initial introduction, many people have asked “why start a new library instead of contributing to an existing library?” (like Apache’s libstdcxx, GNU’s libstdc++, STLport, etc). There are many contributing reasons, but some of the major ones are: From years of experience (including having implemented the standard library before), we’ve learned many things about implementing the standard containers which require ABI breakage and fundamental changes to how they are implemented. For example, it is generally accepted that building std::string using the “short string optimization” instead of using Copy On Write (COW) is a superior approach for multicore machines (particularly in C++11, which has rvalue references). Breaking ABI compatibility with old versions of the library was determined to be critical to achieving the performance goals of libc++. Mainline libstdc++ has switched to GPL3, a license which the developers of libc++ cannot use. libstdc++ 4.2 (the last GPL2 version) could be independently extended to support C++11, but this would be a fork of the codebase (which is often seen as worse for a project than starting a new independent one). Another problem with libstdc++ is that it is tightly integrated with G++ development, tending to be tied fairly closely to the matching version of G++. STLport and the Apache libstdcxx library are two other popular candidates, but both lack C++11 support. Our experience (and the experience of libstdc++ developers) is that adding support for C++11 (in particular rvalue references and move-only types) requires changes to almost every class and function, essentially amounting to a rewrite. Faced with a rewrite, we decided to start from scratch and evaluate every design decision from first principles based on experience. Further, both projects are apparently abandoned: STLport 5.2.1 was released in Oct’08, and STDCXX 4.2.1 in May’08. Platform and Compiler Support ¶ Libc++ aims to support common compilers that implement the C++11 Standard. In order to strike a good balance between stability for users and maintenance cost, testing coverage and development velocity, libc++ drops support for older compilers as newer ones are released. Compiler Versions Restrictions Support policy Clang 16, 17, 18-git latest two stable releases per LLVM’s release page and the development version AppleClang 15 latest stable release per Xcode’s release page Open XL 17.1 (AIX) latest stable release per Open XL’s documentation page GCC 13 In C++11 or later only latest stable release per GCC’s release page Libc++ also supports common platforms and architectures: Target platform Target architecture Notes macOS 10.13+ i386, x86_64, arm64 FreeBSD 12+ i386, x86_64, arm Linux i386, x86_64, arm, arm64 Only glibc-2.24 and later and no other libc is officially supported Android 5.0+ i386, x86_64, arm, arm64 Windows i386, x86_64 Both MSVC and MinGW style environments, ABI in MSVC environments is unstable AIX 7.2TL5+ powerpc, powerpc64 Embedded (picolibc) arm Generally speaking, libc++ should work on any platform that provides a fairly complete C Standard Library. It is also possible to turn off parts of the library for use on systems that provide incomplete support. However, libc++ aims to provide a high-quality implementation of the C++ Standard Library, especially when it comes to correctness. As such, we aim to have test coverage for all the platforms and compilers that we claim to support. If a platform or compiler is not listed here, it is not officially supported. It may happen to work, and in practice the library is known to work on some platforms not listed here, but we don’t make any guarantees. If you would like your compiler and/or platform to be formally supported and listed here, please work with the libc++ team to set up testing for your configuration. C++ Dialect Support ¶ C++11 - Complete C++14 - Complete C++17 - In Progress C++20 - In Progress C++23 - In Progress C++2c - In Progress C++ Feature Test Macro Status Notes and Known Issues ¶ This list contains known issues with libc++ Building libc++ with -fno-rtti is not supported. However linking against it with -fno-rtti is supported. A full list of currently open libc++ bugs can be found here . Design Documents ¶ Libc++ ABI stability <atomic> Design Capturing configuration information in the headers Experimental Features Extended C++03 Support Feature Test Macros File Time Type Header Removal Policy noexcept Policy PSTL integration Threading Support API Enable std::unique_ptr [[clang::trivial_abi]] Unspecified Behavior Randomization Symbol Visibility Macros Time Zone Support Build Bots and Test Coverage ¶ Github Actions CI pipeline Buildkite CI pipeline LLVM Buildbot Builders Adding New CI Jobs Getting Involved ¶ First please review our Developer’s Policy and Getting started with LLVM . Bug Reports If you think you’ve found a bug in libc++, please report it using the LLVM bug tracker . If you’re not sure, you can ask for support on the libcxx forum or on IRC. Patches If you want to contribute a patch to libc++, the best place for that is Phabricator . Please add libcxx-commits as a subscriber. Also make sure you are subscribed to the libcxx-commits mailing list . Discussion and Questions Send discussions and questions to the libcxx forum . Quick Links ¶ LLVM Homepage libc++abi Homepage LLVM Bug Tracker libcxx-commits Mailing List libcxx Forum Browse libc++ Sources Contents   ::   Libc++ 18.0.0 (In-Progress) Release Notes   » © Copyright 2011-2024, LLVM Project. Created using Sphinx 7.1.2. | 2026-01-13T09:30:34 |
https://th-th.facebook.com/login/?next=https%3A%2F%2Fl.facebook.com%2Fl.php%3Fu%3Dhttps%253A%252F%252Fwww.instagram.com%252F%26amp%253Bh%3DAT0_eO-stakg9vLsOUo7Lt26VLQ_aYkr9Pf8ZZaLhPMiLcqEKHlcgGyJNGUNiyBkcQSC6SVtvR-ocoHfFkGBRUIIfK4kqcuSRuVlDS1_g0KFGeSi6wHVGd63HL5D3r9fcZfhU2T8Lb5znjek | Facebook Facebook อีเมลหรือโทรศัพท์ รหัสผ่าน ลืมบัญชีใช่หรือไม่ สร้างบัญชีใหม่ คุณถูกบล็อกชั่วคราว คุณถูกบล็อกชั่วคราว ดูเหมือนว่าคุณจะใช้คุณสมบัตินี้ในทางที่ผิดโดยการใช้เร็วเกินไป คุณถูกบล็อกจากการใช้โดยชั่วคราว Back ภาษาไทย 한국어 English (US) Tiếng Việt Bahasa Indonesia Español 中文(简体) 日本語 Português (Brasil) Français (France) Deutsch สมัคร เข้าสู่ระบบ Messenger Facebook Lite วิดีโอ Meta Pay Meta Store Meta Quest Ray-Ban Meta Meta AI เนื้อหาเพิ่มเติมจาก Meta AI Instagram Threads ศูนย์ข้อมูลการลงคะแนนเสียง นโยบายความเป็นส่วนตัว ศูนย์ความเป็นส่วนตัว เกี่ยวกับ สร้างโฆษณา สร้างเพจ ผู้พัฒนา ร่วมงานกับ Facebook คุกกี้ ตัวเลือกโฆษณา เงื่อนไข ความช่วยเหลือ การอัพโหลดผู้ติดต่อและผู้ที่ไม่ได้ใช้บริการ การตั้งค่า บันทึกกิจกรรม Meta © 2026 | 2026-01-13T09:30:34 |
https://llvmweekly.org/issue/552 | LLVM Weekly - #552, July 29th 2024 LLVM Weekly - #552, July 29th 2024 Welcome to the five hundred and fifty-second issue of LLVM Weekly, a weekly newsletter (published every Monday) covering developments in LLVM, Clang, and related projects. LLVM Weekly is brought to you by Alex Bradbury . Subscribe to future issues at http://llvmweekly.org and pass it on to anyone else you think may be interested. Please send any tips or feedback to asb@asbradbury.org , @llvmweekly or @asbradbury on Twitter, or @llvmweekly@fosstodon.org or @asb@fosstodon.org . News and articles from around the web and events The LLVM 19.x release branch was created and 19.1.0-rc1 was released . The next LLVM Bay Area meetup will take place today, Monday 29th July. As a reminder, open calls for papers/proposals are out for the LLVM in HPC Workshop (closing August 16th) and for the LLVM Developers' Meeting (closing August 11th). Student travel grant applications for the LLVM Developers' Meeting are also now open . According to the LLVM calendar in the coming week there will be the following: Office hours with the following hosts: Johannes Doerfert. Online sync-ups on the following topics: Pointer authentication, SPIR-V, new contributors, OpenMP, Flang, RISC-V backend, LLVM libc, MLIR, HLSL, MLGO. For more details see the LLVM calendar , getting involved documentation on online sync ups and office hours . On the forums Tanya Lattner put out a call for applications to serve on the LLVM Foundation Board of Directors . William Junda Huang proposes adding a new auxiliary field to the BasicBlock class in order to reduce the number of cases where a DenseMap<BasicBlock *, T> must be created. Shourya Goel provided a mid-term update on the GSoC project looking at improving the various thresholds in LLVM . Chaitanya Shahare is seeking feedback on the mockups of the LLVM website redesign . Slides from the recent LLVM meetup in Munich are now available , with talks on “Life with Opaque Pointers from a Frontend Perspective” by Sebastian Neubauer and “A Wishlist for Faster LLVM Back-Ends” by Alexis Engelke. Zoran Zomborat proposed adding support for QuantileQuantizedType in the MLIR Quant dialect . Sergey Semenov started an RFC thread to get feedback on how to handle the initial SYCL dependency on the Unified Runtime project , along with some other questions. David Blaikie queried if the llvm-commits is still useful . Vlad Serebrennikov provided an update on efforts to improve and better label the database of Clang bugs and is asking for help in triaging those labeled clang:to-be-triaged . LLVM commits Frame lowering code was updated to support frames larger than 2GiB. ca076f7 . 128 and 256-bit vector shuffles were implemented for LoongArch. 464ea88 . The PowerPC backend now supports -fpatchable-function-entry . 4321300 . The main branch is now 20.0.0git. 8f701b5 . Clang commits The clang-nvlink-wrapper tool was introduced, which as the name suggests wraps Nvidia’s nvlink linker. It provides an ld.lld style interface. 37d0568 . The pauthtest ABI is now accepted for AArch64 Linux triples. 146fd7c . __atomic_always_lock_free and __atomic_is_lock_free can now be folded at compile time for non-null constant pointers even if the type of the pointer doesn’t guarantee appropriate alignment. 511e93b . __builtin_cpu_init and __builtin_cpu_supports are now implemented for RISC-V. d1e28e2 . The MMX vector intrinsic functions have been reimplemented on the SSE2 instruction set. 0431d6d . Clang static analyzer’s MallocChecker now supports __ownership_returns and __ownership_takes attributes. 893a303 . Other project commits LLD can now use profile guided function ordering, which can reduce page faults during startup. e3b30bc5 . Bolt’s CMake infrastructure was updated to enable a standalone build. abc2eae . Bounded iterators for string and vector can now be enabled for libcxx as part of the hardening options. bcf9fb9 . Subscribe at LLVMWeekly.org . | 2026-01-13T09:30:34 |
https://support.microsoft.com/vi-vn/windows/qu%E1%BA%A3n-l%C3%BD-cookie-trong-microsoft-edge-xem-cho-ph%C3%A9p-ch%E1%BA%B7n-x%C3%B3a-v%C3%A0-s%E1%BB%AD-d%E1%BB%A5ng-168dab11-0753-043d-7c16-ede5947fc64d | Quản lý cookie trong Microsoft Edge: Xem, cho phép, chặn, xóa và sử dụng - Hỗ trợ của Microsoft Chủ đề liên quan × Bảo mật, an toàn và quyền riêng tư của Windows Tổng quan Tổng quan về bảo mật, an toàn và quyền riêng tư Bảo mật của Windows Nhận trợ giúp về bảo mật Windows Luôn được bảo vệ với bảo mật Windows Trước khi bạn tái chế, bán hoặc tặng Xbox hoặc PC chạy Windows của mình Xóa phần mềm độc hại khỏi PC chạy Windows của bạn An toàn Windows Nhận trợ giúp về an toàn Windows Xem và xóa lịch sử trình duyệt trong Microsoft Edge Xóa và quản lý cookie Xóa nội dung có giá trị của bạn một cách an toàn khi cài đặt lại Windows Tìm và khóa thiết bị Windows bị mất Quyền riêng tư của Windows Nhận trợ giúp về quyền riêng tư của Windows Cài đặt quyền riêng tư của Windows mà các ứng dụng sử dụng Xem dữ liệu của bạn trên bảng điều khiển quyền riêng tư Bỏ qua để tới nội dung chính Microsoft Hỗ trợ Hỗ trợ Hỗ trợ Trang chủ Microsoft 365 Office Các sản phẩm Microsoft 365 Outlook Microsoft Teams OneDrive Microsoft Copilot OneNote Windows xem thêm ... Thiết bị Surface Phụ kiện PC Xbox Chơi trò chơi trên PC HoloLens Surface Hub Bảo hành phần cứng Account & billing Tài khoản Microsoft Store và thanh toán Tài nguyên Tính năng mới Diễn đàn cộng đồng Quản trị Microsoft 365 Cổng thông tin dành cho doanh nghiệp nhỏ Nhà phát triển Giáo dục Báo cáo nạn lừa đảo hỗ trợ An toàn sản phẩm Thêm Mua Microsoft 365 Tất cả Microsoft Global Microsoft 365 Teams Copilot Windows Xbox Hỗ trợ Phần mềm Phần mềm Ứng dụng cho Windows AI OneDrive Outlook OneNote Microsoft Teams Máy tính và các thiết bị Máy tính và các thiết bị Mua Xbox Phụ kiện Máy tính Giải trí Giải trí Trò chơi trên PC Kinh doanh Kinh doanh Microsoft Security Azure Dynamics 365 Microsoft 365 dành cho doanh nghiệp Microsoft trong ngành Microsoft Power Platform Windows 365 Nhà phát triển & CNTT Nhà phát triển & CNTT Nhà phát triển Microsoft Microsoft Learn Hỗ trợ cho các ứng dụng trên chợ điện tử AI Cộng đồng Microsoft Tech Microsoft Marketplace Visual Studio Marketplace Rewards Khác Khác Bản tải xuống và bảo mật miễn phí Giáo dục Licensing Xem sơ đồ trang Tìm kiếm Tìm kiếm sự trợ giúp Không có kết quả Hủy Đăng nhập Đăng nhập với Microsoft Đăng nhập hoặc tạo một tài khoản. Xin chào, Chọn một tài khoản khác. Bạn có nhiều tài khoản Chọn tài khoản bạn muốn đăng nhập. Chủ đề liên quan Bảo mật, an toàn và quyền riêng tư của Windows Tổng quan Tổng quan về bảo mật, an toàn và quyền riêng tư Bảo mật của Windows Nhận trợ giúp về bảo mật Windows Luôn được bảo vệ với bảo mật Windows Trước khi bạn tái chế, bán hoặc tặng Xbox hoặc PC chạy Windows của mình Xóa phần mềm độc hại khỏi PC chạy Windows của bạn An toàn Windows Nhận trợ giúp về an toàn Windows Xem và xóa lịch sử trình duyệt trong Microsoft Edge Xóa và quản lý cookie Xóa nội dung có giá trị của bạn một cách an toàn khi cài đặt lại Windows Tìm và khóa thiết bị Windows bị mất Quyền riêng tư của Windows Nhận trợ giúp về quyền riêng tư của Windows Cài đặt quyền riêng tư của Windows mà các ứng dụng sử dụng Xem dữ liệu của bạn trên bảng điều khiển quyền riêng tư Quản lý cookie trong Microsoft Edge: Xem, cho phép, chặn, xóa và sử dụng Áp dụng cho Windows 10 Windows 11 Microsoft Edge Cookie là các mẩu dữ liệu nhỏ được lưu trữ trên thiết bị của bạn bởi các trang web bạn truy cập. Chúng phục vụ các mục đích khác nhau, chẳng hạn như ghi nhớ thông tin đăng nhập, tùy chọn trang web và theo dõi hành vi của người dùng. Tuy nhiên, bạn có thể muốn xóa cookie vì lý do quyền riêng tư hoặc để giải quyết các sự cố duyệt web. Bài viết này cung cấp hướng dẫn về cách: Xem tất cả cookie Cho phép tất cả cookie Cho phép cookie từ một trang web cụ thể Chặn cookie của bên thứ ba Chặn tất cả các cookie Chặn cookie từ một trang web cụ thể Xóa tất cả cookie Xóa cookie khỏi một trang web cụ thể Xóa cookie mỗi khi bạn đóng trình duyệt Sử dụng cookie để tải trước trang để duyệt web nhanh hơn Xem tất cả cookie Mở trình duyệt Edge, chọn Cài đặt và hơn thế nữa ở góc trên bên phải của cửa sổ trình duyệt. Chọn Cài đặt > quyền riêng tư, tìm kiếm và dịch vụ . Chọn Cookie , sau đó bấm Xem tất cả cookie và dữ liệu trang web để xem tất cả cookie được lưu trữ và thông tin trang web liên quan. Cho phép tất cả cookie Bằng cách cho phép cookie, các trang web sẽ có thể lưu và truy xuất dữ liệu trên trình duyệt của bạn, điều này có thể nâng cao trải nghiệm duyệt web của bạn bằng cách ghi nhớ các tùy chọn và thông tin đăng nhập của bạn. Mở trình duyệt Edge, chọn Cài đặt và hơn thế nữa ở góc trên bên phải của cửa sổ trình duyệt. Chọn Cài đặt > riêng tư, tìm kiếm và dịch vụ . Chọn Cookie và bật nút bật tắt Cho phép các trang web lưu và đọc dữ liệu cookie (được khuyến nghị) để cho phép tất cả cookie. Cho phép cookie từ một trang web cụ thể Bằng cách cho phép cookie, các trang web sẽ có thể lưu và truy xuất dữ liệu trên trình duyệt của bạn, điều này có thể nâng cao trải nghiệm duyệt web của bạn bằng cách ghi nhớ các tùy chọn và thông tin đăng nhập của bạn. Mở trình duyệt Edge, chọn Cài đặt và hơn thế nữa ở góc trên bên phải của cửa sổ trình duyệt. Chọn Cài đặt > quyền riêng tư, tìm kiếm và dịch vụ . Chọn Cookie và đi tới Được phép lưu cookie. Chọn Thêm trang web để cho phép cookie trên cơ sở từng trang web bằng cách nhập URL của trang web. Chặn cookie của bên thứ ba Nếu không muốn các trang web bên thứ ba lưu trữ cookie trên PC của mình, bạn có thể chặn cookie. Tuy nhiên, việc này có thể khiến một số trang hiển thị không chính xác hoặc bạn có thể nhận được thông báo từ trang web cho bạn biết rằng bạn cần cho phép cookie để xem trang đó. Mở trình duyệt Edge, chọn Cài đặt và hơn thế nữa ở góc trên bên phải của cửa sổ trình duyệt. Chọn Cài đặt > riêng tư, tìm kiếm và dịch vụ . Chọn Cookie và bật nút bật tắt Chặn cookie của bên thứ ba. Chặn tất cả các cookie Nếu không muốn các trang web bên thứ ba lưu trữ cookie trên PC của mình, bạn có thể chặn cookie. Tuy nhiên, việc này có thể khiến một số trang hiển thị không chính xác hoặc bạn có thể nhận được thông báo từ trang web cho bạn biết rằng bạn cần cho phép cookie để xem trang đó. Mở trình duyệt Edge, chọn Cài đặt và hơn thế nữa ở góc trên bên phải của cửa sổ trình duyệt. Chọn Cài đặt > quyền riêng tư, tìm kiếm và dịch vụ . Chọn Cookie và tắt Cho phép các trang web lưu và đọc dữ liệu cookie (được khuyến nghị) để chặn tất cả cookie. Chặn cookie từ một trang web cụ thể Microsoft Edge cho phép bạn chặn cookie từ một trang web cụ thể, tuy nhiên, việc này có thể ngăn một số trang hiển thị chính xác hoặc bạn có thể nhận được thông báo từ một trang web cho bạn biết rằng bạn cần cho phép cookie để xem trang web đó. Để chặn cookie từ một trang web cụ thể: Mở trình duyệt Edge, chọn Cài đặt và hơn thế nữa ở góc trên bên phải của cửa sổ trình duyệt. Chọn Cài đặt > quyền riêng tư, tìm kiếm và dịch vụ . Chọn Cookie và đi tới Không được phép lưu và đọc cookie . Chọn Thêm trang web để chặn cookie trên cơ sở từng trang web bằng cách nhập URL của trang web. Xóa tất cả cookie Mở trình duyệt Edge, chọn Cài đặt và hơn thế nữa ở góc trên bên phải của cửa sổ trình duyệt. Chọn Cài đặt > riêng tư, tìm kiếm và dịch vụ . Chọn Xóa dữ liệu duyệt web, sau đó chọn Chọn nội dung cần xóa nằm bên cạnh Xóa dữ liệu duyệt web ngay. Bên dưới Khoảng thời gian, chọn một khoảng thời gian từ danh sách. Chọn Cookie và dữ liệu trang web khác , sau đó chọn Xóa ngay . Lưu ý: Ngoài ra, bạn có thể xóa cookie bằng cách nhấn ctrl + SHIFT + DELETE cùng nhau và sau đó tiếp tục với các bước 4 và 5. Tất cả cookie của bạn và dữ liệu trang web khác bây giờ sẽ bị xóa trong khoảng thời gian bạn đã chọn. Điều này làm bạn đăng xuất khỏi hầu hết các trang web. Xóa cookie khỏi một trang web cụ thể Mở trình duyệt Edge, chọn Cài đặt và hơn thế > đặt và > quyền riêng tư, tìm kiếm và dịch vụ . Chọn Cookie , sau đó bấm Xem tất cả cookie và dữ liệu trang web và tìm kiếm trang web có cookie mà bạn muốn xóa. Chọn mũi tên xuống ở bên phải trang web có cookie mà bạn muốn xóa, rồi chọn Xóa . Cookie cho trang web bạn đã chọn hiện đã bị xóa. Lặp lại bước này cho bất kỳ trang web nào có cookie mà bạn muốn xóa. Xóa cookie mỗi khi bạn đóng trình duyệt Mở trình duyệt Edge, chọn Cài đặt và hơn thế > Đặt để > quyền riêng tư, tìm kiếm và dịch vụ . Chọn Xóa dữ liệu duyệt web, sau đó chọn Chọn nội dung cần xóa mỗi lần bạn đóng trình duyệt . Bật nút gạt Cookie và dữ liệu trang web khác. Sau khi bật tính năng này, mỗi lần bạn đóng trình duyệt Edge, tất cả cookie và dữ liệu trang web khác sẽ bị xóa. Điều này làm bạn đăng xuất khỏi hầu hết các trang web. Sử dụng cookie để tải trước trang để duyệt web nhanh hơn Mở trình duyệt Edge, chọn Cài đặt và hơn thế nữa ở góc trên bên phải của cửa sổ trình duyệt. Chọn Cài đặt > riêng tư, tìm kiếm và dịch vụ . Chọn Cookie và bật nút bật/tắt Tải trước các trang để duyệt và tìm kiếm nhanh hơn. ĐĂNG KÝ NGUỒN CẤP DỮ LIỆU RSS Bạn cần thêm trợ giúp? Bạn muốn xem các tùy chọn khác? Khám phá Cộng đồng Liên hệ Chúng tôi Khám phá các lợi ích của gói đăng ký, xem qua các khóa đào tạo, tìm hiểu cách bảo mật thiết bị của bạn và hơn thế nữa. Lợi ích đăng ký Microsoft 365 Nội dung đào tạo về Microsoft 365 Bảo mật Microsoft Trung tâm trợ năng Cộng đồng giúp bạn đặt và trả lời các câu hỏi, cung cấp phản hồi và lắng nghe ý kiến từ các chuyên gia có kiến thức phong phú. Hỏi Cộng đồng Microsoft Cộng đồng Kỹ thuật Microsoft Người dùng Nội bộ Windows Người dùng nội bộ Microsoft 365 Tìm giải pháp cho các sự cố thường gặp hoặc nhận trợ giúp từ nhân viên hỗ trợ. Hỗ trợ trực tuyến Thông tin này có hữu ích không? Có Không Xin cảm ơn! Bạn có thêm ý kiến phản hồi nào cho Microsoft không? Bạn có thể giúp chúng tôi cải thiện không? (Gửi ý kiến phản hồi cho Microsoft để chúng tôi có thể trợ giúp.) Bạn hài lòng đến đâu với chất lượng dịch thuật? Điều gì ảnh hưởng đến trải nghiệm của bạn? Đã giải quyết vấn đề của tôi Hướng dẫn Rõ ràng Dễ theo dõi Không có thuật ngữ Hình ảnh có ích Chất lượng dịch thuật Không khớp với màn hình của tôi Hướng dẫn không chính xác Quá kỹ thuật Không đủ thông tin Không đủ hình ảnh Chất lượng dịch thuật Bất kỳ thông tin phản hồi bổ sung? (Không bắt buộc) Gửi phản hồi Khi nhấn gửi, phản hồi của bạn sẽ được sử dụng để cải thiện các sản phẩm và dịch vụ của Microsoft. Người quản trị CNTT của bạn sẽ có thể thu thập dữ liệu này. Điều khoản về quyền riêng tư. Cảm ơn phản hồi của bạn! × Nội dung mới Copilot cho các tổ chức Copilot cho mục đích sử dụng cá nhân Microsoft 365 Khám phá các sản phẩm Microsoft Microsoft 365 Family Microsoft 365 Personal Ứng dụng cho Windows 11 Microsoft Store Hồ sơ tài khoản Trung tâm Tải xuống Trả lại Theo dõi đơn hàng Giáo dục Microsoft trong ngành giáo dục Thiết bị cho ngành giáo dục Microsoft Teams dành cho Giáo dục Microsoft 365 Education Office trong ngành giáo dục Đào tạo và phát triển giảng viên Ưu đãi dành cho sinh viên và phụ huynh Azure dành cho sinh viên Doanh nghiệp Microsoft Security Azure Dynamics 365 Microsoft 365 Microsoft Advertising Microsoft 365 Copilot Microsoft Teams Developer & IT Nhà phát triển Microsoft Microsoft Learn Hỗ trợ cho các ứng dụng trên chợ điện tử AI Cộng đồng Microsoft Tech Microsoft Marketplace Microsoft Power Platform Marketplace Rewards Visual Studio Công ty Sự nghiệp Giới thiệu về Microsoft Tin tức công ty Quyền riêng tư ở Microsoft Nhà đầu tư Tính bền vững Tiếng Việt (Việt Nam) Biểu tượng Chọn không tham gia lựa chọn quyền riêng tư của bạn Các lựa chọn về quyền riêng tư của bạn Biểu tượng Chọn không tham gia lựa chọn quyền riêng tư của bạn Các lựa chọn về quyền riêng tư của bạn Quyền riêng tư về Sức khỏe người tiêu dùng Liên hệ với Microsoft Quyền riêng tư Quản lý cookie Điều khoản sử dụng Nhãn hiệu Giới thiệu về quảng cáo của chúng tôi © Microsoft 2026 | 2026-01-13T09:30:34 |
https://releases.llvm.org/18.1.8/projects/libcxx/docs/ReleaseNotes.html | Libc++ 18.0.0 (In-Progress) Release Notes — libc++ documentation libc++ documentation Libc++ 18.0.0 (In-Progress) Release Notes «   “libc++” C++ Standard Library   ::   Contents   ::   Using libc++   » Libc++ 18.0.0 (In-Progress) Release Notes ¶ Introduction What’s New in Libc++ 18.0.0? Implemented Papers Improvements and New Features Deprecations and Removals Upcoming Deprecations and Removals ABI Affecting Changes Build System Changes Written by the Libc++ Team Warning These are in-progress notes for the upcoming libc++ 18.0.0 release. Release notes for previous releases can be found on the Download Page . Introduction ¶ This document contains the release notes for the libc++ C++ Standard Library, part of the LLVM Compiler Infrastructure, release 18.0.0. Here we describe the status of libc++ in some detail, including major improvements from the previous release and new feature work. For the general LLVM release notes, see the LLVM documentation . All LLVM releases may be downloaded from the LLVM releases web site . For more information about libc++, please see the Libc++ Web Site or the LLVM Web Site . Note that if you are reading this file from a Git checkout or the main Libc++ web page, this document applies to the next release, not the current one. To see the release notes for a specific release, please see the releases page . What’s New in Libc++ 18.0.0? ¶ The main focus of the libc++ team has been to implement new C++20, C++23, and C++26 features. New hardened modes for the library have been added, replacing the legacy debug mode that was removed in the LLVM 17 release. Unlike the legacy debug mode, some of these hardening modes are also intended to be used in production. See Hardening Modes for more details. Work on the ranges support has progressed. See libc++ Ranges Status for the current status. Work on the experimental C++23 module support has progressed. The std.compat module is available and the feature is retroactively available in C++20. See Modules in libc++ for more information. Work on the experimental C++17 Parallel STL has progressed. See libc++ Parallel STL Status for the current status. Work on the experimental C++17 SIMD support has progressed. See libc++ Parallelism TS Status (N4808) for the current status. Implemented Papers ¶ P2093R14 - Formatted output P2539R4 - Should the output of std::print to a terminal be synchronized with the underlying stream? P2497R0 - Testing for success or failure of <charconv> functions P2697R1 - Interfacing bitset with string_view P2443R1 - views::chunk_by P2538R1 - ADL-proof std::projected P2614R2 - Deprecate numeric_limits::has_denorm P0053R7 - C++ Synchronized Buffered Ostream (in the experimental library) P2467R1 - Support exclusive mode for fstreams P0020R6 - Floating Point Atomic P2905R2 - Runtime format strings P2918R2 - Runtime format strings II P2871R3 - Remove Deprecated Unicode Conversion Facets from C++26 P2870R3 - Remove basic_string::reserve() P2909R4 - Fix formatting of code units as integers (Dude, where’s my char ?) P2821R5 - span.at() P0521R0 - Proposed Resolution for CA 14 ( shared_ptr use_count/unique ) P0543R3 - Saturation arithmetic P1759R6 - Native handles and file streams P2868R3 - Remove Deprecated std::allocator Typedef From C++26 P2517R1 - Add a conditional noexcept specification to std::apply P2447R6 - span over initializer list Improvements and New Features ¶ std::ranges::count and std::ranges::find are now optimized for std::vector<bool>::iterator , which can lead up to 350x performance improvements. std::for_each has been optimized for segmented iterators like std::deque::iterator in C++23 and later, which can lead up to 40x performance improvements. The library now provides several hardening modes under which common cases of library undefined behavior will be turned into a reliable program termination. The fast hardening mode enables a set of security-critical checks with minimal runtime overhead; the extensive hardening mode additionally enables relatively cheap checks that catch common logic errors but aren’t necessarily security-critical; and the debug hardening mode enables all available checks, some of which might be very expensive. Vendors can configure which hardening mode is enabled by default with the LIBCXX_HARDENING_MODE variable at CMake configuration time. Users can control which hardening mode is enabled on a per translation unit basis using the _LIBCPP_HARDENING_MODE macro. See the hardening documentation for more details. The _LIBCPP_ENABLE_CXX26_REMOVED_CODECVT macro has been added to make the declarations in <codecvt> available. The _LIBCPP_ENABLE_CXX26_REMOVED_STRING_RESERVE macro has been added to make the function std::basic_string<...>::reserve() available. The _LIBCPP_ENABLE_CXX26_REMOVED_ALLOCATOR_MEMBERS macro has been added to make the function allocator<T>::is_always_equal available. The _LIBCPP_ENABLE_CXX20_REMOVED_SHARED_PTR_UNIQUE macro has been added to make the function std::shared_ptr<...>::unique() available. The cmake option LIBCXX_ENABLE_STD_MODULES has been removed. The test infrastructure no longer depends on a modern CMake, it works with the minimal required LLVM version (3.20.0). The .cppm files of experimental standard library modules can now be installed. By default, they are not installed. This can be enabled by configuring CMake with -DLIBCXX_INSTALL_MODULES=ON . The installation directory can be configured with the CMake option -DLIBCXX_INSTALL_MODULE_DIR=<path> . The default location is ${PREFIX}/share/libc++/v1 . AddressSanitizer annotations have been added to std::basic_string . These annotations are enabled for all allocators by default. It’s only enabled for long strings, strings using the small buffer optimization are not annotated. The libc++ source code has been formatted with clang-format . This discourse thread contains information how to rebase downstream patches. Deprecations and Removals ¶ Availability macros which will never trigger an error have been removed. This includes anything that has been introduced before macOS 10.13, iOS 12, tvOS 12 and watchOS 4. This shouldn’t affect anybody, since AppleClang 15 doesn’t support any older OSes. If you are a vendor and make use of these macros, please inform the libc++ team so we can re-introduce them and consider upstreaming support for your platform. The non-conforming constructor std::future_error(std::error_code) has been removed. Please use the std::future_error(std::future_errc) constructor provided in C++17 instead. P1957 has been implemented in Clang and libc++ removed a code path that led to narrowing conversions in std::variant behaving in a non-standard way. This may change how some uses of std::variant ’s constructor behave in user code. The _LIBCPP_ENABLE_NARROWING_CONVERSIONS_IN_VARIANT macro is provided to restore the previous behavior, and it will be supported in the LLVM 18 release only. In LLVM 19 and beyond, _LIBCPP_ENABLE_NARROWING_CONVERSIONS_IN_VARIANT will not be honored anymore. Overriding __libcpp_verbose_abort no longer has any effect on library assertions. The only supported way to customize the assertion handler that gets invoked when a hardening assertion fails is now by setting the LIBCXX_ASSERTION_HANDLER_FILE CMake variable and providing a custom header. See the documentation on overriding the default assertion handler for details. The ability to override __libcpp_verbose_abort will be removed in an upcoming release in favor of the new overriding mechanism. In safe mode (which is now equivalent to the extensive hardening mode), a failed assertion will now generate a trap rather than a call to verbose abort. The _LIBCPP_AVAILABILITY_CUSTOM_VERBOSE_ABORT_PROVIDED macro is not honored anymore in LLVM 18. Please see the updated documentation about the hardening modes in libc++ and in particular on overriding the default assertion handler. The headers <experimental/deque> , <experimental/forward_list> , <experimental/list> , <experimental/map> , <experimental/memory_resource> , <experimental/regex> , <experimental/set> , <experimental/string> , <experimental/unordered_map> , <experimental/unordered_set> , and <experimental/vector> have been removed in LLVM 18, as all their contents will have been implemented in namespace std for at least two releases. The macro _LIBCPP_ENABLE_CXX20_REMOVED_ALLOCATOR_MEMBERS has been deprecated and will be removed in LLVM 19. This macro used to re-enable redundant members of std::allocator<T> like pointer , reference , rebind , address , max_size , construct , destroy , and the two-argument overload of allocate . However, this led to the library being non-conforming due to incorrect constexpr-ness. The macros _LIBCPP_ENABLE_CXX17_REMOVED_FEATURES and _LIBCPP_ENABLE_CXX20_REMOVED_FEATURES have been deprecated and will be removed in LLVM 19. These macros used to re-enable all features that were removed in the C++17 and C++20 standards. Instead of using these macros, please use the macros to re-enable individual features. The macro _LIBCPP_INLINE_VISIBILITY has been deprecated in LLVM 18 and will be removed entirely in LLVM 19. The macro _LIBCPP_HIDE_FROM_ABI is the drop-in replacement. The macro _VSTD has been deprecated in LLVM 18 and will be removed entirely in LLVM 19. The code std is the drop-in replacement. Upcoming Deprecations and Removals ¶ The ability to override __libcpp_verbose_abort will be removed in an upcoming release. LLVM 19 ¶ The LIBCXX_EXECUTOR CMake variable has been deprecated. LLVM 19 will completely remove support for the *_EXECUTOR variables. The LIBCXX_ENABLE_ASSERTIONS CMake variable that was used to enable the safe mode will be deprecated and setting it will trigger an error; use the LIBCXX_HARDENING_MODE variable with the value extensive instead. Similarly, the _LIBCPP_ENABLE_ASSERTIONS macro will be deprecated (setting it to 1 still enables the extensive mode in the LLVM 19 release while also issuing a deprecation warning). See the hardening documentation for more details. The base template for std::char_traits has been marked as deprecated and will be removed in LLVM 19. If you are using std::char_traits with types other than char , wchar_t , char8_t , char16_t , char32_t or a custom character type for which you specialized std::char_traits , your code will stop working when we remove the base template. The Standard does not mandate that a base template is provided, and such a base template is bound to be incorrect for some types, which could currently cause unexpected behavior while going undetected. Note that the _LIBCPP_CHAR_TRAITS_REMOVE_BASE_SPECIALIZATION macro can be defined in LLVM 18 to eagerly remove the specialization and prepare code bases for the unconditional removal in LLVM 19. The _LIBCPP_ENABLE_NARROWING_CONVERSIONS_IN_VARIANT macro that changed the behavior for narrowing conversions in std::variant will be removed in LLVM 19. The _LIBCPP_ENABLE_CXX20_REMOVED_ALLOCATOR_MEMBERS macro has been deprecated in LLVM 18 and will be removed entirely in LLVM 19. The _LIBCPP_ENABLE_CXX17_REMOVED_FEATURES and _LIBCPP_ENABLE_CXX20_REMOVED_FEATURES macros have been deprecated in LLVM 18 and will be removed entirely in LLVM 19. The macro _LIBCPP_INLINE_VISIBILITY has been deprecated in LLVM 18 and will be removed entirely in LLVM 19. The macro _VSTD has been deprecated in LLVM 18 and will be removed entirely in LLVM 19. LLVM 20 ¶ The LIBCXX_ENABLE_ASSERTIONS CMake variable and the _LIBCPP_ENABLE_ASSERTIONS macro that were used to enable the safe mode will be removed. ABI Affecting Changes ¶ When the shared/static library is built with -fno-exceptions , the behavior of operator new was changed to make it standards-conforming. In LLVM 17 and before, the throwing versions of operator new would return nullptr upon failure to allocate, when the shared/static library was built with exceptions disabled. This was non-conforming, since the throwing versions of operator new are never expected to return nullptr , and this non-conformance could actually lead to miscompiles in subtle cases. Starting in LLVM 18, the throwing versions of operator new will abort the program when they fail to allocate if the shared/static library has been built with -fno-exceptions . This is consistent with the behavior of all other potentially-throwing functions in the library, which abort the program instead of throwing when -fno-exceptions is used. Furthermore, when the shared/static library is built with -fno-exceptions , users who override the throwing version of operator new will now need to also override the std::nothrow_t version of operator new if they want to use it. Indeed, this is because there is no way to implement a conforming operator new(nothrow) from a conforming potentially-throwing operator new when compiled with -fno-exceptions . In that case, using operator new(nothrow) without overriding it explicitly but after overriding the throwing operator new will result in an error. Note that this change only impacts vendors/users that build the shared/static library themselves and pass -DLIBCXX_ENABLE_EXCEPTIONS=OFF , which is not the default configuration. If you are using the default configuration of the library, the libc++ shared/static library will be built with exceptions enabled, and there is no change between LLVM 17 and LLVM 18, even for users who build their own code using -fno-exceptions . The symbol of a non-visible function part of std::system_error was removed. This is not a breaking change as the private function __init was never referenced internally outside of the dylib. This release of libc++ added missing visibility annotations on some types in the library. Users compiling with -fvisbility=hidden may notice that additional type infos from libc++ are being exported from their ABI. This is the correct behavior in almost all cases since exporting the RTTI is required for these types to work properly with dynamic_cast , exceptions and other mechanisms across binaries. However, if you intend to use libc++ purely as an internal implementation detail (i.e. you use libc++ as a static archive and never export libc++ symbols from your ABI) and you notice changes to your exported symbols list, then this means that you were not properly preventing libc++ symbols from being part of your ABI. The name mangling for instantiations of std::projected has changed in order to implement P2538R1. This technically results in an ABI break, however in practice we expect uses of std::projected in ABI-sensitive places to be extremely rare. Any error resulting from this change should result in a link-time error. The internal alignment requirements for heap allocations inside std::string has decreased from 16 to 8. This saves memory since string requests fewer additional bytes than it did previously. However, this also changes the return value of std::string::max_size and can cause code compiled against older libc++ versions but linked at runtime to a new version to throw a different exception when attempting allocations that are too large ( std::bad_alloc vs std::length_error ). The layout of some range adaptors that use the movable-box exposition-only type as an implementation detail has changed in order to fix a bug which could result in overwriting user data following the movable-box . This bug was caused by incorrect usage of the [[no_unique_address]] attribute inside the implementation of movable-box . This fix affects the layout of the following views: take_while_view , filter_view , single_view , drop_while_view , repeat_view , transform_view , chunk_by_view . In order to avoid silent breakage as a result of this fix, an ABI tag has been added to these views such that their mangled name will be different starting in this version of libc++. As a result, attempting to call a function that expects one of these views will fail to link until the code has been rebuilt against a matching version of libc++. In practice, we believe it is unusual for these views to appear at ABI boundaries so this should not be a major problem for most users. However it is probably worth auditing ranges-heavy code for ABI boundaries that would contain these views, or for types that contain these views as members and which are passed across ABI boundaries. Some properties of libc++ may cause ODR-violations when mixing multiple libc++ instances. To avoid these, often benign, ODR-violations the ODR-affecting properties are now part of the ABI tag. The ODR-affecting properties are: library version (This was part of the ABI tag prior to LLVM 18.) exceptions vs no-exceptions hardening mode This should not be ABI-affecting except that libc++ will be more robust against different configurations of it being used in different translation units. The amount of padding bytes available for use at the end of certain std::expected instantiations has changed in this release. This is an ABI break for any code that held a std::expected member with [[no_unique_address]] in an ABI-facing type. In those cases, the layout of the enclosing type will change, breaking the ABI. However, the std::expected<T, E> member requires a few characteristics in order to be affected by this change: A type equivalent to union {T ; E} needs to have more than one byte of padding available. The std::expected<T, E> member must have been in a situation where its padding bytes were previously reused by another object, which can happen in a few cases (this is probably not exhaustive): It is a member with [[no_unique_address]] applied to it, and it is followed by another data member, or It is a member with [[no_unique_address]] applied to it, and it is the last member of the user-defined type, and that user-defined type is used in ways that its padding bytes can be reused, or It is inherited from We expect that this will not be a very frequent occurrence. However, there is unfortunately no technique we can use in the library to catch such misuse. Indeed, even applying an ABI tag to std::expected would not help since ABI tags are not propagated to containing types. As a result, if you notice very difficult to explain bugs around the usage of a std::expected , you should consider checking whether you are hitting this ABI break. This change was done to fix #70494 and the vendor communication is handled in #70820 . Build System Changes ¶ The LIBCXX_EXECUTOR CMake variable has been deprecated. If you are relying on this, the new replacement is passing -Dexecutor=... to llvm-lit . Alternatively, this flag can be made persistent in the generated test configuration file by passing -DLIBCXX_TEST_PARAMS=executor=... . This also applies to the LIBUWIND_EXECTOR and LIBCXXABI_EXECUTOR CMake variables. LLVM 19 will completely remove support for the *_EXECUTOR variables. LIBCXXABI_USE_LLVM_UNWINDER and COMPILER_RT_USE_LLVM_UNWINDER switched defaults from OFF to ON . This means that by default, libc++abi and compiler-rt will link against the LLVM provided libunwind library instead of the system-provided unwinding library. If you are building the LLVM runtimes with the goal of shipping them so that they can interoperate with other system-provided libraries that might be using a different unwinding library (such as libgcc_s ), you should pass LIBCXXABI_USE_LLVM_UNWINDER=OFF and COMPILER_RT_USE_LLVM_UNWINDER=OFF to make sure the system-provided unwinding library is used by the LLVM runtimes. In Clang-cl configurations, libc++ can now be built against the static and/or debug MSVC C runtimes «   “libc++” C++ Standard Library   ::   Contents   ::   Using libc++   » © Copyright 2011-2024, LLVM Project. Created using Sphinx 7.1.2. | 2026-01-13T09:30:34 |
https://www.php.net/session-name | PHP: session_name - Manual update page now Downloads Documentation Get Involved Help Search docs Getting Started Introduction A simple tutorial Language Reference Basic syntax Types Variables Constants Expressions Operators Control Structures Functions Classes and Objects Namespaces Enumerations Errors Exceptions Fibers Generators Attributes References Explained Predefined Variables Predefined Exceptions Predefined Interfaces and Classes Predefined Attributes Context options and parameters Supported Protocols and Wrappers Security Introduction General considerations Installed as CGI binary Installed as an Apache module Session Security Filesystem Security Database Security Error Reporting User Submitted Data Hiding PHP Keeping Current Features HTTP authentication with PHP Cookies Sessions Handling file uploads Using remote files Connection handling Persistent Database Connections Command line usage Garbage Collection DTrace Dynamic Tracing Function Reference Affecting PHP's Behaviour Audio Formats Manipulation Authentication Services Command Line Specific Extensions Compression and Archive Extensions Cryptography Extensions Database Extensions Date and Time Related Extensions File System Related Extensions Human Language and Character Encoding Support Image Processing and Generation Mail Related Extensions Mathematical Extensions Non-Text MIME Output Process Control Extensions Other Basic Extensions Other Services Search Engine Extensions Server Specific Extensions Session Extensions Text Processing Variable and Type Related Extensions Web Services Windows Only Extensions XML Manipulation GUI Extensions Keyboard Shortcuts ? This help j Next menu item k Previous menu item g p Previous man page g n Next man page G Scroll to bottom g g Scroll to top g h Goto homepage g s Goto search (current page) / Focus search box session_regenerate_id » « session_module_name PHP Manual Function Reference Session Extensions Sessions Session Functions Change language: English German Spanish French Italian Japanese Brazilian Portuguese Russian Turkish Ukrainian Chinese (Simplified) Other session_name (PHP 4, PHP 5, PHP 7, PHP 8) session_name — Get and/or set the current session name Description session_name ( ? string $name = null ): string | false session_name() returns the name of the current session. If name is given, session_name() will update the session name and return the old session name. If a new session name is supplied, session_name() modifies the HTTP cookie (and outputs the content when session.use_trans_sid is enabled). Once the HTTP cookie has been sent, calling session_name() raises an E_WARNING . session_name() must be called before session_start() for the session to work properly. The session name is reset to the default value stored in session.name at request startup time. Thus, you need to call session_name() for every request (and before session_start() is called). Parameters name The session name references the name of the session, which is used in cookies and URLs (e.g. PHPSESSID ). It should contain only alphanumeric characters; it should be short and descriptive (i.e. for users with enabled cookie warnings). If name is specified and not null , the name of the current session is changed to its value. Warning The session name can't consist of digits only, at least one letter must be present. Otherwise a new session id is generated every time. Return Values Returns the name of the current session. If name is given and function updates the session name, name of the old session is returned, or false on failure. Changelog Version Description 8.0.0 name is nullable now. 7.2.0 session_name() checks session status, previously it only checked cookie status. Therefore, older session_name() allows to call session_name() after session_start() which may crash PHP and may result in misbehaviors. Examples Example #1 session_name() example <?php /* set the session name to WebsiteID */ $previous_name = session_name ( "WebsiteID" ); echo "The previous session name was $previous_name <br />" ; ?> See Also The session.name configuration directive Found A Problem? Learn How To Improve This Page • Submit a Pull Request • Report a Bug ＋ add a note User Contributed Notes 9 notes up down 146 Hongliang Qiang ¶ 21 years ago This may sound no-brainer: the session_name() function will have no essential effect if you set session.auto_start to "true" in php.ini . And the obvious explanation is the session already started thus cannot be altered before the session_name() function--wherever it is in the script--is executed, same reason session_name needs to be called before session_start() as documented. I know it is really not a big deal. But I had a quite hard time before figuring this out, and hope it might be helpful to someone like me. up down 65 php at wiz dot cx ¶ 17 years ago if you try to name a php session "example.com" it gets converted to "example_com" and everything breaks. don't use a period in your session name. up down 40 relsqui at chiliahedron dot com ¶ 16 years ago Remember, kids--you MUST use session_name() first if you want to use session_set_cookie_params() to, say, change the session timeout. Otherwise it won't work, won't give any error, and nothing in the documentation (that I've seen, anyway) will explain why. Thanks to brandan of bildungsroman.com who left a note under session_set_cookie_params() explaining this or I'd probably still be throwing my hands up about it. up down 21 Joseph Dalrymple ¶ 14 years ago For those wondering, this function is expensive! On a script that was executing in a consistent 0.0025 seconds, just the use of session_name("foo") shot my execution time up to ~0.09s. By simply sacrificing session_name("foo"), I sped my script up by roughly 0.09 seconds. up down 10 Victor H ¶ 10 years ago As Joseph Dalrymple said, adding session_name do slow down a little bit the execution time. But, what i've observed is that it decreased the fluctuation between requests. Requests on my script fluctuated between 0,045 and 0,022 seconds. With session_name("myapp"), it goes to 0,050 and 0,045. Not a big deal, but that's a point to note. For those with problems setting the name, when session.auto_start is set to 1, you need to set the session.name on php.ini! up down 3 mmulej at gmail dot com ¶ 4 years ago Hope this is not out of php.net noting scope. session_name('name') must be set before session_start() because the former changes ini settings and the latter reads them. For the same reason session_set_cookie_params($options) must be set before session_start() as well. I find it best to do the following. function is_session_started() { if (php_sapi_name() === 'cli') return false; if (version_compare(phpversion(), '5.4.0', '>=')) return session_status() === PHP_SESSION_ACTIVE; return session_id() !== ''; } if (!is_session_started()) { session_name($session_name); session_set_cookie_params($cookie_options); session_start(); } up down 0 tony at marston-home dot demon dot co dot uk ¶ 7 years ago The description that session_name() gets and/or sets the name of the current session is technically wrong. It does nothing but deal with the value originally supplied by the session.name value within the php.ini file. Thus:- $name = session_name(); is functionally equivalent to $name = ini_get('session.name'); and session_name('newname); is functionally equivalent to ini_set('session.name','newname'); This also means that: $old_name = session_name('newname'); is functionally equivalent to $old_name = ini_set('session.name','newname'); The current value of session.name is not attached to a session until session_start() is called. Once session_start() has used session.name to lookup the session_id() in the cookie data the name becomes irrelevant as all further operations on the session data are keyed by the session_id(). Note that changing session.name while a session is currently active will not update the name in any session cookie. The new name does not take effect until the next call to session_start(), and this requires that the current session, which was created with the previous value for session.name, be closed. up down -4 tony at marston-home dot demon dot co dot uk ¶ 7 years ago The description has recently been modified to contain the statement "When new session name is supplied, session_name() modifies HTTP cookie". This is not correct as session_name() has never modified any cookie data. A change in session.name does not become effective until session_start() is called, and it is session_start() that creates the cookie if it does not already exist. See the following bug report for details: https://bugs.php.net/bug.php?id=76413 up down -3 descartavel1+php at gmail dot com ¶ 2 years ago Always try to set the prefix for your session name attribute to either `__Host-` or `__Secure-` to benefit from Browsers improved security. See https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie#attributes Also, if you have auto_session enabled, you must set this name in session.name in your config (php.ini, htaccess, etc) ＋ add a note Session Functions session_​abort session_​cache_​expire session_​cache_​limiter session_​commit session_​create_​id session_​decode session_​destroy session_​encode session_​gc session_​get_​cookie_​params session_​id session_​module_​name session_​name session_​regenerate_​id session_​register_​shutdown session_​reset session_​save_​path session_​set_​cookie_​params session_​set_​save_​handler session_​start session_​status session_​unset session_​write_​close Copyright © 2001-2026 The PHP Documentation Group My PHP.net Contact Other PHP.net sites Privacy policy ↑ and ↓ to navigate • Enter to select • Esc to close • / to open Press Enter without selection to search using Google | 2026-01-13T09:30:34 |
https://releases.llvm.org/18.1.8/tools/polly/docs/index.html | Welcome to Polly's documentation! — Polly 18.1.8 documentation Polly 18.1.8 documentation Welcome to Polly's documentation! Contents   ::   Release Notes 18.1.8 Release Notes   » Upcoming Release ¶ Release Notes 18.1.8 Release Notes Using Polly ¶ The Architecture Polly in the LLVM pass pipeline Using Polly with Clang Make Polly available from Clang Optimizing with Polly Automatic OpenMP code generation Automatic Vector code generation Isolate the Polly passes Further options How to manually use the Individual pieces of Polly Execute the individual Polly passes manually Tips and Tricks on using and contributing to Polly Committing to polly trunk Using bugpoint to track down errors in large files Understanding which pass makes a particular change Debugging regressions introduced at some unknown earlier point Performance High-Performance Generalized Matrix Multiplication Compile Time Impact of Polly A list of Polly passes Indices and tables ¶ Index Search Page Contents   ::   Release Notes 18.1.8 Release Notes   » © Copyright 2010-2024, The Polly Team. Created using Sphinx 7.1.2. | 2026-01-13T09:30:34 |
https://th-th.facebook.com/login/?next=https%3A%2F%2Fl.facebook.com%2Fl.php%3Fu%3Dhttps%253A%252F%252Fwww.instagram.com%252F%26amp%253Bh%3DAT0oK5bRFTTybnDOhYhIZLq01lQic0NLTeIbHIWCatEHpQ1l_XvBDhFFg93NTxyaIWLyhjuKO75pi9dqx6GinsMsCUF3-jXwiN5uEdfkpm7k0xf-caL8YQT8KCcQ_cBSLI1zBjdYsjE75jVT | Facebook Facebook อีเมลหรือโทรศัพท์ รหัสผ่าน ลืมบัญชีใช่หรือไม่ สร้างบัญชีใหม่ คุณถูกบล็อกชั่วคราว คุณถูกบล็อกชั่วคราว ดูเหมือนว่าคุณจะใช้คุณสมบัตินี้ในทางที่ผิดโดยการใช้เร็วเกินไป คุณถูกบล็อกจากการใช้โดยชั่วคราว Back ภาษาไทย 한국어 English (US) Tiếng Việt Bahasa Indonesia Español 中文(简体) 日本語 Português (Brasil) Français (France) Deutsch สมัคร เข้าสู่ระบบ Messenger Facebook Lite วิดีโอ Meta Pay Meta Store Meta Quest Ray-Ban Meta Meta AI เนื้อหาเพิ่มเติมจาก Meta AI Instagram Threads ศูนย์ข้อมูลการลงคะแนนเสียง นโยบายความเป็นส่วนตัว ศูนย์ความเป็นส่วนตัว เกี่ยวกับ สร้างโฆษณา สร้างเพจ ผู้พัฒนา ร่วมงานกับ Facebook คุกกี้ ตัวเลือกโฆษณา เงื่อนไข ความช่วยเหลือ การอัพโหลดผู้ติดต่อและผู้ที่ไม่ได้ใช้บริการ การตั้งค่า บันทึกกิจกรรม Meta © 2026 | 2026-01-13T09:30:34 |
http://bugs.php.net/stats.php | PHP :: Bugs Stats php.net | support | documentation | report a bug | advanced search | search howto | statistics | random bug | login go to bug id or search bugs for Bug Type: All Bug Feature/Change Request Documentation Problem Security Name Closed Open Crit Verified Analyzed Assigned Fdbk No Fdbk Susp Not a bug Dupe Wont Fix All 81426 39987 1739 360 37 152 7371 829 25175 1688 3410 SOAP related 679 270 124 6 130 120 17 7 *General Issues 4472 1345 96 15 1 6 352 66 1888 148 296 Scripting Engine problem 5092 2412 77 30 3 5 338 71 1786 120 236 FPM related 495 237 55 3 1 24 65 2 56 28 16 SPL related 708 393 52 20 4 34 6 134 20 37 opcache 479 270 41 8 3 92 2 28 28 7 Streams related 588 279 36 10 2 2 73 2 136 24 18 Filesystem function related 1280 515 35 8 1 162 12 465 32 46 Unknown/Other Function 1902 540 34 4 2 148 12 1076 27 56 Documentation problem 6582 4915 30 16 1 113 6 1295 40 146 MySQLi related 676 265 29 5 1 99 4 226 18 28 Website problem 2313 1309 29 9 1 4 124 601 67 127 Filter related 238 91 27 6 8 82 14 5 Strings related 919 351 26 3 1 70 19 391 17 39 Arrays related 1087 327 25 10 1 57 21 564 28 54 oauth 132 77 25 1 13 1 10 3 1 PDO MySQL 208 89 25 7 1 21 25 32 5 PDO related 804 340 25 4 1 1 162 8 221 12 27 OpenSSL related 419 237 23 4 2 5 41 1 81 11 12 PHP options/info functions 619 200 23 5 2 67 7 277 7 28 mbstring related 434 241 21 11 1 53 2 77 12 12 Class/Object related 1183 350 20 5 3 68 35 586 41 74 cURL related 594 305 20 4 1 3 71 1 162 14 10 IMAP related 598 250 20 2 3 91 5 206 7 14 PDO_INFORMIX 66 25 20 2 11 5 1 1 I18N and L10N related 89 32 19 2 7 1 20 3 4 Reflection related 328 186 19 4 18 4 62 11 23 PCNTL related 68 25 18 1 8 12 1 2 *Configuration Issues 539 181 17 4 40 6 255 12 21 CGI/CLI related 554 175 17 7 113 2 215 8 16 Doc Build problem 250 145 17 5 2 2 13 6 25 6 5 Sockets related 439 208 17 4 2 69 1 126 5 6 ssh2 208 104 17 3 1 40 22 18 3 Performance problem 490 189 16 1 50 1 202 7 16 solr 137 93 16 1 5 3 15 2 2 HTTP related 393 173 15 1 35 3 153 2 7 Built-in web server 184 93 14 1 23 1 23 10 12 Compile Failure 3847 2402 14 2 1 356 5 967 28 67 Feature/Change Request 2278 1130 14 45 13 712 47 317 Closed Open Crit Verified Analyzed Assigned Fdbk No Fdbk Susp Not a bug Dupe Wont Fix SimpleXML related 323 94 14 6 1 30 2 138 18 16 *Compile Issues 387 138 13 2 48 157 9 19 DOM XML related 729 279 13 5 56 3 317 8 48 Session related 1768 726 13 2 2 11 229 2 722 9 48 PCRE related 671 202 12 6 2 55 8 349 21 15 PHAR related 256 157 12 5 1 25 41 10 Program Execution 253 112 12 2 1 3 26 2 81 3 9 FTP related 266 111 11 1 1 52 1 82 1 3 OCI8 related 828 361 11 4 143 2 278 13 16 PDO DBlib 57 23 11 5 12 5 1 PDO OCI 92 32 11 1 22 16 9 PostgreSQL related 464 258 11 2 2 45 107 5 34 Semaphore related 66 22 11 15 1 13 2 Apache2 related 1141 334 10 2 3 1 218 1 542 10 16 FFI 13 10 1 1 Systems problem 244 156 10 3 15 23 10 12 Testing related 195 140 10 1 17 16 5 2 COM related 403 174 9 4 75 3 113 9 16 gmagick 99 71 9 1 1 1 7 5 1 3 ibm_db2 134 97 9 2 6 16 2 2 JSON related 211 83 9 13 4 82 7 12 Network related 169 75 9 1 2 24 44 4 9 ODBC related 649 375 9 4 114 130 6 10 phpdbg 62 41 9 2 2 5 1 Reproducible crash 90 9 1 1 72 URL related 181 60 9 2 1 19 3 72 8 6 *Encryption and hash functions 119 55 8 2 1 6 1 39 3 4 PECL 87 45 8 1 5 2 15 8 3 Zip Related 171 93 8 2 2 22 38 3 3 *Network Functions 79 31 7 7 25 5 2 MySQL related 1398 585 7 1 1 109 637 11 44 PDO Core 53 29 7 2 2 8 2 3 PDO PgSQL 58 26 7 2 4 11 6 1 PDO_IBM 31 7 7 1 10 1 4 Variables related 584 130 7 4 29 12 360 17 24 yaf 35 23 7 3 2 DBus 7 6 1 hash related 72 34 6 7 1 18 2 4 JIT 56 38 6 10 1 1 LDAP related 349 191 6 5 36 90 5 15 Closed Open Crit Verified Analyzed Assigned Fdbk No Fdbk Susp Not a bug Dupe Wont Fix mongo 48 27 6 1 2 8 3 Output Control 722 199 6 3 2 98 3 369 10 21 POSIX related 43 15 6 1 5 13 2 SNMP related 147 67 6 1 35 36 2 stomp 35 18 6 1 6 3 1 Translation problem 856 783 6 2 11 4 35 7 2 *Directory/Filesystem functions 310 110 5 7 1 32 1 127 16 8 *XML functions 118 39 5 2 7 1 56 3 2 Apache related 817 350 5 1 88 358 3 12 GD related 1135 538 5 3 123 13 401 31 19 mailparse 74 41 5 2 1 10 7 5 1 PDO ODBC 56 12 5 1 1 28 5 4 PDO SQLite 47 19 5 4 8 4 6 Readline related 33 19 5 1 1 1 4 1 1 XML related 211 90 5 1 26 1 77 1 10 *Programming Data Structures 105 17 4 4 4 62 3 9 EXIF related 133 92 4 17 13 4 3 geoip 46 27 4 1 2 6 5 ICONV related 121 57 4 3 13 37 3 4 Mail related 386 159 4 49 3 155 5 8 PECL website 336 245 4 1 5 54 12 13 PHP Language Specification 72 36 4 1 4 16 3 1 Safe Mode/open_basedir 238 77 4 1 42 2 78 15 16 svn 107 64 4 5 16 13 5 XSLT related 224 66 4 35 110 9 Zlib related 132 66 4 2 1 1 21 1 32 2 2 *Extensibility Functions 48 22 3 1 5 1 12 3 1 *URL Functions 89 35 3 2 7 34 4 2 *Web Server problem 150 38 3 1 9 3 83 2 2 Bitset 10 4 3 2 1 Bzip2 Related 47 29 3 9 5 1 DBM/DBA related 154 88 3 1 17 32 2 11 expect 32 16 3 5 7 1 IIS related 681 181 3 2 106 1 372 4 12 SQLite related 179 99 3 2 1 15 1 44 3 10 APC 844 434 2 1 1 132 8 80 32 153 dbase 36 27 2 5 1 1 Online Doc Editor problem 106 83 2 1 5 1 9 2 PDO_OCI 19 9 2 4 1 3 uuid 13 6 2 5 Closed Open Crit Verified Analyzed Assigned Fdbk No Fdbk Susp Not a bug Dupe Wont Fix xdiff 23 11 2 6 3 1 XML Writer 39 17 2 1 4 14 1 XMLRPC-EPI related 92 53 2 4 20 4 8 *Database Functions 57 13 1 4 1 36 1 1 *Math Functions 136 26 1 2 9 1 94 2 1 *Regular Expressions 118 25 1 2 6 79 2 2 ares 2 1 1 bcompiler 75 32 1 5 13 14 7 3 Compile Warning 233 129 1 18 58 4 22 Dynamic loading 379 165 1 26 164 11 enchant 4 2 1 1 gearman 87 36 1 12 26 4 1 7 GetImageSize related 105 52 1 15 29 2 6 gnupg 57 33 1 1 9 6 3 4 lua 17 14 1 1 1 Math related 421 98 1 25 2 276 2 17 memcache 246 152 1 29 44 8 12 mogilefs 5 4 1 mongodb 15 7 1 1 6 mqseries 10 7 1 1 1 Other web server 119 71 1 14 1 28 3 PDO Firebird 41 29 1 4 2 5 PDO_ODBC 14 11 1 1 1 PDO_PGSQL 11 6 1 2 2 phar 24 14 1 3 5 1 PHP-GTK related 128 54 1 16 9 31 5 Pspell related 43 17 1 1 7 17 radius 16 9 1 4 1 1 taint 13 9 1 2 1 Tidy 93 46 1 7 35 4 varnish 4 2 1 1 Win32API related 9 5 1 2 XML Reader 43 15 1 5 2 15 2 3 *Calendar problems 7 1 1 3 2 *Compression related 15 3 2 3 7 *Data Exchange functions 8 4 3 1 *Directory Services problems 4 1 3 *E-commerce functions 4 1 3 *Function Specific 51 47 4 *Graphics related 55 13 2 1 37 2 Closed Open Crit Verified Analyzed Assigned Fdbk No Fdbk Susp Not a bug Dupe Wont Fix *Languages/Translation 73 28 6 35 4 *Mail Related 75 20 3 49 2 *PDF functions 17 5 3 9 *Spelling functions 3 1 1 *Unicode Issues 55 13 1 3 30 5 3 Adabas-D related 12 10 1 1 amfext 6 2 1 3 amqp 107 81 5 9 5 7 apd 48 8 5 26 7 2 APM 16 13 1 1 1 archive 2 1 1 automap 2 2 axis2 1 1 bbcode 31 11 1 1 4 1 13 BC math related 54 33 1 2 16 1 1 big_int 3 1 1 1 BLENC 20 4 14 2 bloomy 2 2 bz2 2 1 1 cairo 12 7 1 3 cairo_wrapper 8 4 1 3 Calendar related 67 22 2 3 4 33 2 1 chdb 2 1 1 ClibPDF related 7 3 1 3 clucene 1 1 coin_acceptor 1 1 colorer 7 5 2 crack 17 9 2 3 1 2 cvsclient 1 1 cybercash 1 1 cyrus 1 1 Date/time related 1838 694 1 107 4 841 94 96 date_time 13 7 5 1 dBase related 101 64 11 21 5 DBDO 3 1 2 dbplus 1 1 dbx 5 2 2 1 DBX related 8 4 3 1 dio 14 6 4 2 1 1 Directory function related 231 81 33 1 106 4 6 Closed Open Crit Verified Analyzed Assigned Fdbk No Fdbk Susp Not a bug Dupe Wont Fix docblock 6 3 1 2 domxml 1 1 drizzle 10 3 1 6 DTrace 5 2 1 2 ecasound 1 1 eio 6 3 1 1 1 Enchant related 13 11 1 1 esmtp 1 1 event 29 17 1 2 1 8 fann 9 7 2 FDF related 25 17 6 2 ffi 18 10 1 1 1 5 Fileinfo 41 23 3 15 filter 59 34 4 19 2 fpdf 2 1 1 FreeImage 4 2 1 fribidi 4 2 2 FrontBase related 4 3 1 FrontPage related 7 7 funcall 6 5 1 fuse 4 2 2 GDChart 10 1 9 Gettext related 62 31 1 11 17 1 1 GNU MP related 49 28 1 4 9 1 6 gupnp 4 1 3 haru 15 8 2 3 2 hash 7 4 1 1 hidef 13 7 3 2 1 html_parse 3 1 1 1 htscanner 34 26 2 5 1 id3 11 1 7 1 1 1 idn 16 4 2 7 3 igbinary 10 7 1 2 imagick 331 159 4 7 62 5 71 9 13 imlib2 2 1 1 inclued 13 9 1 1 2 informix 2 2 Informix related 114 62 21 26 5 ingres 60 38 2 16 3 1 Ingres II related 13 4 1 1 5 1 Closed Open Crit Verified Analyzed Assigned Fdbk No Fdbk Susp Not a bug Dupe Wont Fix inotify 7 5 1 1 Installation problem 749 650 2 79 18 InterBase related 250 134 24 18 70 2 2 intercept 1 1 intl 242 146 15 64 8 9 iPlanet related 104 45 27 29 3 isis 1 1 Java related 99 29 38 24 8 json 33 11 5 13 1 3 kadm5 6 1 5 KTaglib 2 2 lchash 3 1 1 1 leveldb 3 3 libevent 25 10 1 6 8 Livedocs problem 38 22 6 10 lzf 10 6 2 2 markdown 1 1 maxdb 4 1 3 mcrypt related 178 120 6 41 3 7 mcve 3 3 mdbtools 4 1 3 memcached 136 112 2 8 8 4 memtrack 6 1 1 2 2 mhash related 19 7 3 9 ming 1 1 Ming related 18 5 9 3 1 Misbehaving function 839 755 38 46 mnogosearch 8 3 2 1 2 mnoGoSearch related 11 3 1 7 mono 5 1 2 2 msgpack 2 1 1 mSQL related 30 28 1 1 MSSQL related 548 199 101 210 38 mysql 15 5 2 6 2 mysqlnd_memcache 3 3 mysqlnd_ms 41 14 7 17 2 1 mysqlnd_qc 11 6 2 3 mysqlnd_uh 4 4 ncurses 12 5 1 1 5 ncurses related 6 1 5 Closed Open Crit Verified Analyzed Assigned Fdbk No Fdbk Susp Not a bug Dupe Wont Fix newt 11 9 1 1 oci8 52 29 2 17 2 2 oggvorbis 9 2 7 openal 1 1 operator 20 8 2 9 optimizer 7 2 1 2 1 1 Oracle related 142 82 5 43 12 Other 646 552 52 42 PAM 13 4 1 2 2 4 panda 1 1 Paradox 15 3 4 8 params 1 1 parsekit 15 5 2 1 7 Parser error 152 137 7 8 Parse_Tree 5 2 3 PDF related 74 37 6 30 1 pdflib 26 14 4 5 3 PDO 69 35 10 19 5 PDO_4D 9 3 2 4 PDO_DBLIB 1 1 PDO_FIREBIRD 2 2 PDO_MYSQL 53 24 2 22 3 2 pdo_oci 3 PDO_SQLITE 16 8 4 3 1 pdo_sqlsrv 5 2 1 2 pdo_user 4 1 3 PEAR related 397 280 33 79 5 PECL bug system 142 82 1 30 3 3 PECL_Gen 6 4 1 pecl_http 174 99 19 29 5 16 perforce 1 1 perl 24 3 7 11 2 1 PHK 1 1 PHPScript 21 3 1 8 9 POP3 7 2 2 3 printer 7 1 1 4 proctitle 4 1 3 ps 14 5 1 6 1 1 pthreads 44 20 2 12 1 9 PWS related 45 15 2 28 Closed Open Crit Verified Analyzed Assigned Fdbk No Fdbk Susp Not a bug Dupe Wont Fix python 8 4 1 1 2 rar 48 23 1 4 10 5 5 Recode related 17 6 2 2 7 Regexps related 114 37 8 65 1 3 Reproducible Crash 2892 1726 427 651 88 rpmreader 3 3 rrd 35 31 3 1 runkit 71 55 3 10 1 2 Sablotron XSL 63 46 16 1 sam 7 1 1 5 sasl 4 1 1 2 SCA_SDO 108 52 12 32 8 3 1 scream 3 3 Servlet related 27 5 11 9 2 shape 1 1 Solid related 13 9 1 1 2 sphinx 52 34 3 5 10 spidermonkey 20 9 9 1 1 SPL 2 1 1 SPL_Types 15 5 10 spread 14 10 2 1 1 SQLite 30 12 2 5 7 4 sqlite3 4 4 sqlsrv 12 7 2 1 1 1 ssdeep 3 1 1 1 statgrab 6 6 stats 22 17 3 2 stem 9 3 2 2 1 1 swish 4 2 2 Sybase (dblib) related 136 88 19 26 3 Sybase-ct (ctlib) related 211 126 32 1 37 15 syck 7 3 4 tcpwrap 1 1 tdb 1 1 threads 1 1 timezonedb 40 26 3 1 9 1 tk 2 1 tokyo_tyrant 3 3 Trader 13 8 2 2 1 translit 5 2 2 1 Closed Open Crit Verified Analyzed Assigned Fdbk No Fdbk Susp Not a bug Dupe Wont Fix Unicode Engine related 35 15 4 9 6 unicodestring 1 uploadprogress 61 24 4 10 13 2 7 v8js 18 16 1 1 Valkyrie 2 Verisign Payflow Pro related 17 10 1 5 1 vld 14 10 2 2 vpopmail 6 2 3 1 WBXML 3 2 1 WDDX related 81 55 10 13 3 Weakref 9 4 5 win32ps 2 1 1 win32service 10 7 3 win32std 5 1 1 3 WinBinder 2 2 WinCache 64 39 1 1 1 16 Windows Installer 205 93 35 55 4 15 xattr 5 3 2 Xdebug 40 15 4 13 2 6 xhprof 41 15 22 2 1 xmlReader 9 2 1 6 xmlwriter 9 5 2 2 xmms 1 1 xrange 3 2 1 xslcache 4 2 2 yami 1 1 yaml 46 39 1 5 1 yar 3 2 1 yaz 11 7 1 3 yp 3 2 1 zip 75 36 13 1 19 4 2 PHP Versions for recent bug reports: Copyright © 2001-2026 The PHP Group All rights reserved. Last updated: Tue Jan 13 09:00:01 2026 UTC | 2026-01-13T09:30:34 |
https://th-th.facebook.com/login/?next=https%3A%2F%2Fl.facebook.com%2Fl.php%3Fu%3Dhttps%253A%252F%252Fwww.instagram.com%252F%26amp%253Bh%3DAT2keGOX2gxggubPvbD2U4v7iuDC9S3X2Lk7QEf_zG6UCPFlqRgkB8gDW-EZJfw1fiHskSqvBHeZQITabHORPi6bmhZQB9HgmigfedLFjaYt-gvk5RTqrih_kcyIODnVVuMY0a6Vs1-agSJ_ | Facebook Facebook อีเมลหรือโทรศัพท์ รหัสผ่าน ลืมบัญชีใช่หรือไม่ สร้างบัญชีใหม่ คุณถูกบล็อกชั่วคราว คุณถูกบล็อกชั่วคราว ดูเหมือนว่าคุณจะใช้คุณสมบัตินี้ในทางที่ผิดโดยการใช้เร็วเกินไป คุณถูกบล็อกจากการใช้โดยชั่วคราว Back ภาษาไทย 한국어 English (US) Tiếng Việt Bahasa Indonesia Español 中文(简体) 日本語 Português (Brasil) Français (France) Deutsch สมัคร เข้าสู่ระบบ Messenger Facebook Lite วิดีโอ Meta Pay Meta Store Meta Quest Ray-Ban Meta Meta AI เนื้อหาเพิ่มเติมจาก Meta AI Instagram Threads ศูนย์ข้อมูลการลงคะแนนเสียง นโยบายความเป็นส่วนตัว ศูนย์ความเป็นส่วนตัว เกี่ยวกับ สร้างโฆษณา สร้างเพจ ผู้พัฒนา ร่วมงานกับ Facebook คุกกี้ ตัวเลือกโฆษณา เงื่อนไข ความช่วยเหลือ การอัพโหลดผู้ติดต่อและผู้ที่ไม่ได้ใช้บริการ การตั้งค่า บันทึกกิจกรรม Meta © 2026 | 2026-01-13T09:30:34 |
http://docs.buildbot.net/current/manual/installation/misc.html#launching-worker-as-windows-service | 2.2.6. Next Steps — Buildbot 4.3.0 documentation Buildbot 1. Buildbot Tutorial 2. Buildbot Manual 2.1. Introduction 2.2. Installation 2.2.1. Buildbot Components 2.2.2. Requirements 2.2.3. Installing the code 2.2.4. Buildmaster Setup 2.2.5. Worker Setup 2.2.6. Next Steps 2.2.6.1. Launching the daemons 2.2.6.2. Launching worker as Windows service 2.2.6.3. Logfiles 2.2.6.4. Shutdown 2.3. Concepts 2.4. Secret Management 2.5. Configuration 2.6. Customization 2.7. Command-line Tool 2.8. Resources 2.9. Optimization 2.10. Plugin Infrastructure in Buildbot 2.11. Deployment 2.12. Upgrading 3. Buildbot Development 4. Release Notes 5. Older Release Notes 6. API Indices Buildbot 2. Buildbot Manual 2.2. Installation 2.2.6. Next Steps View page source 2.2.6. Next Steps 2.2.6.1. Launching the daemons Both the buildmaster and the worker run as daemon programs. To launch them, pass the working directory to the buildbot and buildbot-worker commands, as appropriate: # start a master buildbot start [ BASEDIR ] # start a worker buildbot-worker start [ WORKER_BASEDIR ] The BASEDIR is optional and can be omitted if the current directory contains the buildbot configuration (the buildbot.tac file). buildbot start This command will start the daemon and then return, so normally it will not produce any output. To verify that the programs are indeed running, look for a pair of files named twistd.log and twistd.pid that should be created in the working directory. twistd.pid contains the process ID of the newly-spawned daemon. When the worker connects to the buildmaster, new directories will start appearing in its base directory. The buildmaster tells the worker to create a directory for each Builder which will be using that worker. All build operations are performed within these directories: CVS checkouts, compiles, and tests. Once you get everything running, you will want to arrange for the buildbot daemons to be started at boot time. One way is to use cron , by putting them in a @reboot crontab entry [ 1 ] @reboot buildbot start [ BASEDIR ] When you run crontab to set this up, remember to do it as the buildmaster or worker account! If you add this to your crontab when running as your regular account (or worse yet, root), then the daemon will run as the wrong user, quite possibly as one with more authority than you intended to provide. It is important to remember that the environment provided to cron jobs and init scripts can be quite different than your normal runtime. There may be fewer environment variables specified, and the PATH may be shorter than usual. It is a good idea to test out this method of launching the worker by using a cron job with a time in the near future, with the same command, and then check twistd.log to make sure the worker actually started correctly. Common problems here are for /usr/local or ~/bin to not be on your PATH , or for PYTHONPATH to not be set correctly. Sometimes HOME is messed up too. If using systemd to launch buildbot-worker , it may be a good idea to specify a fixed PATH using the Environment directive (see systemd unit file example ). Some distributions may include conveniences to make starting buildbot at boot time easy. For instance, with the default buildbot package in Debian-based distributions, you may only need to modify /etc/default/buildbot (see also /etc/init.d/buildbot , which reads the configuration in /etc/default/buildbot ). Buildbot also comes with its own init scripts that provide support for controlling multi-worker and multi-master setups (mostly because they are based on the init script from the Debian package). With a little modification, these scripts can be used on both Debian and RHEL-based distributions. Thus, they may prove helpful to package maintainers who are working on buildbot (or to those who haven’t yet split buildbot into master and worker packages). # install as /etc/default/buildbot-worker # or /etc/sysconfig/buildbot-worker worker/contrib/init-scripts/buildbot-worker.default # install as /etc/default/buildmaster # or /etc/sysconfig/buildmaster master/contrib/init-scripts/buildmaster.default # install as /etc/init.d/buildbot-worker worker/contrib/init-scripts/buildbot-worker.init.sh # install as /etc/init.d/buildmaster master/contrib/init-scripts/buildmaster.init.sh # ... and tell sysvinit about them chkconfig buildmaster reset # ... or update-rc.d buildmaster defaults 2.2.6.2. Launching worker as Windows service Security consideration Setting up the buildbot worker as a Windows service requires Windows administrator rights. It is important to distinguish installation stage from service execution. It is strongly recommended run Buildbot worker with lowest required access rights. It is recommended run a service under machine local non-privileged account. If you decide run Buildbot worker under domain account it is recommended to create dedicated strongly limited user account that will run Buildbot worker service. Windows service setup In this description, we assume that the buildbot worker account is the local domain account worker . In case worker should run under domain user account please replace .\worker with <domain>\worker . Please replace <worker.passwd> with given user password. Please replace <worker.basedir> with the full/absolute directory specification to the created worker (what is called BASEDIR in Creating a worker ). buildbot_worker_windows_service --user .\worker --password < worker.passwd > --startup auto install powershell -command "& {&'New-Item' -path Registry::HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\BuildBot\Parameters}" powershell -command "& {&'set-ItemProperty' -path Registry::HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\BuildBot\Parameters -Name directories -Value '<worker.basedir>'}" The first command automatically adds user rights to run Buildbot as service. Modify environment variables This step is optional and may depend on your needs. At least we have found useful to have dedicated temp folder worker steps. It is much easier discover what temporary files your builds leaks/misbehaves. As Administrator run regedit Open the key Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Buildbot . Create a new value of type REG_MULTI_SZ called Environment . Add entries like TMP = c : \ bbw \ tmp TEMP = c : \ bbw \ tmp Check if Buildbot can start correctly configured as Windows service As admin user run the command net start buildbot . In case everything goes well, you should see following output The BuildBot service is starting . The BuildBot service was started successfully . Troubleshooting If anything goes wrong check Twisted log on C:\bbw\worker\twistd.log Windows system event log ( eventvwr.msc in command line, Show-EventLog in PowerShell). 2.2.6.3. Logfiles While a buildbot daemon runs, it emits text to a logfile, named twistd.log . A command like tail -f twistd.log is useful to watch the command output as it runs. The buildmaster will announce any errors with its configuration file in the logfile, so it is a good idea to look at the log at startup time to check for any problems. Most buildmaster activities will cause lines to be added to the log. 2.2.6.4. Shutdown To stop a buildmaster or worker manually, use: buildbot stop [ BASEDIR ] # or buildbot-worker stop [ WORKER_BASEDIR ] This simply looks for the twistd.pid file and kills whatever process is identified within. At system shutdown, all processes are sent a SIGKILL . The buildmaster and worker will respond to this by shutting down normally. The buildmaster will respond to a SIGHUP by re-reading its config file. Of course, this only works on Unix-like systems with signal support and not on Windows. The following shortcut is available: buildbot reconfig [ BASEDIR ] When you update the Buildbot code to a new release, you will need to restart the buildmaster and/or worker before they can take advantage of the new code. You can do a buildbot stop BASEDIR and buildbot start BASEDIR in succession, or you can use the restart shortcut, which does both steps for you: buildbot restart [ BASEDIR ] Workers can similarly be restarted with: buildbot-worker restart [ BASEDIR ] There are certain configuration changes that are not handled cleanly by buildbot reconfig . If this occurs, buildbot restart is a more robust way to fully switch over to the new configuration. buildbot restart may also be used to start a stopped Buildbot instance. This behavior is useful when writing scripts that stop, start, and restart Buildbot. A worker may also be gracefully shutdown from the web UI. This is useful to shutdown a worker without interrupting any current builds. The buildmaster will wait until the worker has finished all its current builds, and will then tell the worker to shutdown. [ 1 ] This @reboot syntax is understood by Vixie cron, which is the flavor usually provided with Linux systems. Other unices may have a cron that doesn’t understand @reboot Previous Next © Copyright Buildbot Team Members. Built with Sphinx using a theme provided by Read the Docs . | 2026-01-13T09:30:34 |
https://fr-fr.facebook.com/login/?next=https%3A%2F%2Fl.facebook.com%2Fl.php%3Fu%3Dhttps%253A%252F%252Fwww.instagram.com%252F%26amp%253Bh%3DAT2keGOX2gxggubPvbD2U4v7iuDC9S3X2Lk7QEf_zG6UCPFlqRgkB8gDW-EZJfw1fiHskSqvBHeZQITabHORPi6bmhZQB9HgmigfedLFjaYt-gvk5RTqrih_kcyIODnVVuMY0a6Vs1-agSJ_ | Facebook Facebook Adresse e-mail ou téléphone Mot de passe Informations de compte oubliées ? Créer un compte Cette fonction est temporairement bloquée Cette fonction est temporairement bloquée Il semble que vous ayez abusé de cette fonctionnalité en l’utilisant trop vite. Vous n’êtes plus autorisé à l’utiliser. Back Français (France) 한국어 English (US) Tiếng Việt Bahasa Indonesia ภาษาไทย Español 中文(简体) 日本語 Português (Brasil) Deutsch S’inscrire Se connecter Messenger Facebook Lite Vidéo Meta Pay Boutique Meta Meta Quest Ray-Ban Meta Meta AI Plus de contenu Meta AI Instagram Threads Centre d’information sur les élections Politique de confidentialité Centre de confidentialité À propos Créer une publicité Créer une Page Développeurs Emplois Cookies Choisir sa publicité Conditions générales Aide Importation des contacts et non-utilisateurs Paramètres Historique d’activité Meta © 2026 | 2026-01-13T09:30:34 |
http://docs.buildbot.net/current/manual/installation/misc.html#modify-environment-variables | 2.2.6. Next Steps — Buildbot 4.3.0 documentation Buildbot 1. Buildbot Tutorial 2. Buildbot Manual 2.1. Introduction 2.2. Installation 2.2.1. Buildbot Components 2.2.2. Requirements 2.2.3. Installing the code 2.2.4. Buildmaster Setup 2.2.5. Worker Setup 2.2.6. Next Steps 2.2.6.1. Launching the daemons 2.2.6.2. Launching worker as Windows service 2.2.6.3. Logfiles 2.2.6.4. Shutdown 2.3. Concepts 2.4. Secret Management 2.5. Configuration 2.6. Customization 2.7. Command-line Tool 2.8. Resources 2.9. Optimization 2.10. Plugin Infrastructure in Buildbot 2.11. Deployment 2.12. Upgrading 3. Buildbot Development 4. Release Notes 5. Older Release Notes 6. API Indices Buildbot 2. Buildbot Manual 2.2. Installation 2.2.6. Next Steps View page source 2.2.6. Next Steps 2.2.6.1. Launching the daemons Both the buildmaster and the worker run as daemon programs. To launch them, pass the working directory to the buildbot and buildbot-worker commands, as appropriate: # start a master buildbot start [ BASEDIR ] # start a worker buildbot-worker start [ WORKER_BASEDIR ] The BASEDIR is optional and can be omitted if the current directory contains the buildbot configuration (the buildbot.tac file). buildbot start This command will start the daemon and then return, so normally it will not produce any output. To verify that the programs are indeed running, look for a pair of files named twistd.log and twistd.pid that should be created in the working directory. twistd.pid contains the process ID of the newly-spawned daemon. When the worker connects to the buildmaster, new directories will start appearing in its base directory. The buildmaster tells the worker to create a directory for each Builder which will be using that worker. All build operations are performed within these directories: CVS checkouts, compiles, and tests. Once you get everything running, you will want to arrange for the buildbot daemons to be started at boot time. One way is to use cron , by putting them in a @reboot crontab entry [ 1 ] @reboot buildbot start [ BASEDIR ] When you run crontab to set this up, remember to do it as the buildmaster or worker account! If you add this to your crontab when running as your regular account (or worse yet, root), then the daemon will run as the wrong user, quite possibly as one with more authority than you intended to provide. It is important to remember that the environment provided to cron jobs and init scripts can be quite different than your normal runtime. There may be fewer environment variables specified, and the PATH may be shorter than usual. It is a good idea to test out this method of launching the worker by using a cron job with a time in the near future, with the same command, and then check twistd.log to make sure the worker actually started correctly. Common problems here are for /usr/local or ~/bin to not be on your PATH , or for PYTHONPATH to not be set correctly. Sometimes HOME is messed up too. If using systemd to launch buildbot-worker , it may be a good idea to specify a fixed PATH using the Environment directive (see systemd unit file example ). Some distributions may include conveniences to make starting buildbot at boot time easy. For instance, with the default buildbot package in Debian-based distributions, you may only need to modify /etc/default/buildbot (see also /etc/init.d/buildbot , which reads the configuration in /etc/default/buildbot ). Buildbot also comes with its own init scripts that provide support for controlling multi-worker and multi-master setups (mostly because they are based on the init script from the Debian package). With a little modification, these scripts can be used on both Debian and RHEL-based distributions. Thus, they may prove helpful to package maintainers who are working on buildbot (or to those who haven’t yet split buildbot into master and worker packages). # install as /etc/default/buildbot-worker # or /etc/sysconfig/buildbot-worker worker/contrib/init-scripts/buildbot-worker.default # install as /etc/default/buildmaster # or /etc/sysconfig/buildmaster master/contrib/init-scripts/buildmaster.default # install as /etc/init.d/buildbot-worker worker/contrib/init-scripts/buildbot-worker.init.sh # install as /etc/init.d/buildmaster master/contrib/init-scripts/buildmaster.init.sh # ... and tell sysvinit about them chkconfig buildmaster reset # ... or update-rc.d buildmaster defaults 2.2.6.2. Launching worker as Windows service Security consideration Setting up the buildbot worker as a Windows service requires Windows administrator rights. It is important to distinguish installation stage from service execution. It is strongly recommended run Buildbot worker with lowest required access rights. It is recommended run a service under machine local non-privileged account. If you decide run Buildbot worker under domain account it is recommended to create dedicated strongly limited user account that will run Buildbot worker service. Windows service setup In this description, we assume that the buildbot worker account is the local domain account worker . In case worker should run under domain user account please replace .\worker with <domain>\worker . Please replace <worker.passwd> with given user password. Please replace <worker.basedir> with the full/absolute directory specification to the created worker (what is called BASEDIR in Creating a worker ). buildbot_worker_windows_service --user .\worker --password < worker.passwd > --startup auto install powershell -command "& {&'New-Item' -path Registry::HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\BuildBot\Parameters}" powershell -command "& {&'set-ItemProperty' -path Registry::HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\BuildBot\Parameters -Name directories -Value '<worker.basedir>'}" The first command automatically adds user rights to run Buildbot as service. Modify environment variables This step is optional and may depend on your needs. At least we have found useful to have dedicated temp folder worker steps. It is much easier discover what temporary files your builds leaks/misbehaves. As Administrator run regedit Open the key Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Buildbot . Create a new value of type REG_MULTI_SZ called Environment . Add entries like TMP = c : \ bbw \ tmp TEMP = c : \ bbw \ tmp Check if Buildbot can start correctly configured as Windows service As admin user run the command net start buildbot . In case everything goes well, you should see following output The BuildBot service is starting . The BuildBot service was started successfully . Troubleshooting If anything goes wrong check Twisted log on C:\bbw\worker\twistd.log Windows system event log ( eventvwr.msc in command line, Show-EventLog in PowerShell). 2.2.6.3. Logfiles While a buildbot daemon runs, it emits text to a logfile, named twistd.log . A command like tail -f twistd.log is useful to watch the command output as it runs. The buildmaster will announce any errors with its configuration file in the logfile, so it is a good idea to look at the log at startup time to check for any problems. Most buildmaster activities will cause lines to be added to the log. 2.2.6.4. Shutdown To stop a buildmaster or worker manually, use: buildbot stop [ BASEDIR ] # or buildbot-worker stop [ WORKER_BASEDIR ] This simply looks for the twistd.pid file and kills whatever process is identified within. At system shutdown, all processes are sent a SIGKILL . The buildmaster and worker will respond to this by shutting down normally. The buildmaster will respond to a SIGHUP by re-reading its config file. Of course, this only works on Unix-like systems with signal support and not on Windows. The following shortcut is available: buildbot reconfig [ BASEDIR ] When you update the Buildbot code to a new release, you will need to restart the buildmaster and/or worker before they can take advantage of the new code. You can do a buildbot stop BASEDIR and buildbot start BASEDIR in succession, or you can use the restart shortcut, which does both steps for you: buildbot restart [ BASEDIR ] Workers can similarly be restarted with: buildbot-worker restart [ BASEDIR ] There are certain configuration changes that are not handled cleanly by buildbot reconfig . If this occurs, buildbot restart is a more robust way to fully switch over to the new configuration. buildbot restart may also be used to start a stopped Buildbot instance. This behavior is useful when writing scripts that stop, start, and restart Buildbot. A worker may also be gracefully shutdown from the web UI. This is useful to shutdown a worker without interrupting any current builds. The buildmaster will wait until the worker has finished all its current builds, and will then tell the worker to shutdown. [ 1 ] This @reboot syntax is understood by Vixie cron, which is the flavor usually provided with Linux systems. Other unices may have a cron that doesn’t understand @reboot Previous Next © Copyright Buildbot Team Members. Built with Sphinx using a theme provided by Read the Docs . | 2026-01-13T09:30:34 |
https://th-th.facebook.com/login/?next=https%3A%2F%2Fl.facebook.com%2Fl.php%3Fu%3Dhttps%253A%252F%252Fwww.instagram.com%252F%26amp%253Bh%3DAT3lN7wpIGgWaTyXErk4SF1WCKEs9PDHJPdbiN3Yl_7Rba5JxYLIit5nb079Cw1WWMDlqJeHCsuW7di_wtBhIrbQwVsBpN2U3fkPKWMYiOrU-c_JuLCa8u7nUnpt80Nm-EprkKK9rPoa2_sw | Facebook Facebook อีเมลหรือโทรศัพท์ รหัสผ่าน ลืมบัญชีใช่หรือไม่ สร้างบัญชีใหม่ คุณถูกบล็อกชั่วคราว คุณถูกบล็อกชั่วคราว ดูเหมือนว่าคุณจะใช้คุณสมบัตินี้ในทางที่ผิดโดยการใช้เร็วเกินไป คุณถูกบล็อกจากการใช้โดยชั่วคราว Back ภาษาไทย 한국어 English (US) Tiếng Việt Bahasa Indonesia Español 中文(简体) 日本語 Português (Brasil) Français (France) Deutsch สมัคร เข้าสู่ระบบ Messenger Facebook Lite วิดีโอ Meta Pay Meta Store Meta Quest Ray-Ban Meta Meta AI เนื้อหาเพิ่มเติมจาก Meta AI Instagram Threads ศูนย์ข้อมูลการลงคะแนนเสียง นโยบายความเป็นส่วนตัว ศูนย์ความเป็นส่วนตัว เกี่ยวกับ สร้างโฆษณา สร้างเพจ ผู้พัฒนา ร่วมงานกับ Facebook คุกกี้ ตัวเลือกโฆษณา เงื่อนไข ความช่วยเหลือ การอัพโหลดผู้ติดต่อและผู้ที่ไม่ได้ใช้บริการ การตั้งค่า บันทึกกิจกรรม Meta © 2026 | 2026-01-13T09:30:34 |
https://www.visma.com/voiceofvisma/episode-5-anne-grethe-thomle-karlsen | Ep 05: Our Team Visma | Lease a Bike sponsorship with Anne-Grethe Thomle Karlsen Who we are About us Connected by software – driven by people Become a Visma company Join our family of thriving SaaS companies Technology and AI at Visma Innovation with customer value at its heart Our sponsorship Team Visma | Lease a Bike Sustainability A better impact through software Contact us Find the right contact information What we offer Cloud software We create brilliant ways to work For medium businesses Lead your business with clarity For small businesses Start, run and grow with ease For public sector Empower efficient societies For accounting offices Build your dream accounting office For partners Help us keep customers ahead For investors For investors Latest results, news and strategy Financials Key figures, quarterly and annual results Events Financial calendar Governance Policies, management, board and owners Careers Careers at Visma Join the business software revolution Locations Find your nearest office Open positions Turn your passion into a career Resources News For small businesses Cloud accounting software built for small businesses Who we are About us Technology and AI at Visma Sustainability Become a Visma company Our sponsorship What we offer Cloud software For small businesses For accounting offices For enterprises Public sector For partners For investors Overview Financials Governance News and press Events Careers Careers at Visma Open positions Hubs Resources Blog Visma Developer Trust Centre News Press releases Team Visma | Lease a Bike Podcast Ep 05: Our Team Visma | Lease a Bike sponsorship with Anne-Grethe Thomle Karlsen Voice of Visma June 12, 2024 Spotify Created with Sketch. YouTube Apple Podcasts Amazon Music <iframe style="border-radius:12px" src="https://open.spotify.com/embed/episode/1oBByXJv9BqVrHbUekAjad?utm_source=generator" width="100%" height="352" frameBorder="0" allowfullscreen="" allow="autoplay; clipboard-write; encrypted-media; fullscreen; picture-in-picture" loading="lazy"></iframe> About the episode It’s one thing to sponsor the world’s best cycling team; it’s a whole other thing to provide software and expertise that helps them do what they do best. Today, Anne-Grethe and Johan explore how we help Team Visma | Lease a Bike, both on and off the bikes. And why we’re so proud to now be the first title sponsor! Share More from Voice of Visma We're sitting down with leaders and colleagues from around Visma to share their stories, industry knowledge, and valuable career lessons. With the Voice of Visma podcast, we’re bringing our people and culture closer to you. Get to know the podcast Ep 22: Building, learning, and accelerating growth in the SaaS world with Maxin Schneider Entrepreneurial leadership often grows through experience, and Maxin Schneider has seen that up close. Read more Ep 21: How DEI fuels business success with Iveta Bukane Why DEI isn't just a moral imperative—it’s a business necessity. Read more Ep 20: Driving tangible sustainability outcomes with Freja Landewall Discover how ESG goes far beyond the environment, encompassing people, governance, and the long-term resilience of business. Read more Ep 19: Future-proofing public services in Sweden with Marie Ceder Between demographic changes, the rise in AI, and digitalisation, the public sector is at a pivotal moment. Read more Ep 18: Making inclusion part of our everyday work with Ida Algotsson What does inclusion truly mean at Visma – not just as values, but as everyday actions? Read more Ep 17: Sustainability at the heart of business with Robin Åkerberg Honouring our responsibility goes well beyond the numbers – it starts with a shared purpose and values. Read more Ep 16: Innovation for the public good with Kasper Lyhr Serving the public sector goes way beyond software – it’s about shaping the future of society as a whole. Read more Ep 15: Leading with transparency and vulnerability with Ellen Sano What does it mean to be a “firestarter” in business? Read more Ep 14: Women, innovation, and the future of Visma with Merete Hverven Our CEO, Merete, knows that great leadership takes more than just hard work – it takes vision. Read more Ep 13: Building partnerships beyond software with Daniel Ognøy Kaspersen What does it look like when an accounting software company delivers more than just great software? Read more Ep 12: AI in the accounting sphere with Joris Joppe Artificial intelligence is changing industries across the board, and accounting is no exception. But in such a highly specialised field, what does change actually look like? Read more Ep 11: From Founder to Segment Director with Ari-Pekka Salovaara Ari-Pekka is a serial entrepreneur who joined Visma when his company was acquired in 2010. He now leads the small business segment. Read more Ep 10: When brave choices can save a company with Charlotte von Sydow What’s it like stepping in as the Managing Director for a company in decline? Read more Ep 09: Revolutionising tax tech in Italy with Enrico Mattiazzi and Vito Lomele Take one look at their product, their customer reviews, or their workplace awards, and it’s clear why Fiscozen leads Italy’s tax tech scene. Read more Ep 08: Navigating the waters of entrepreneurship with Steffen Torp When it comes to being an entrepreneur, the journey is as personal as it is unpredictable. Read more Ep 07: The untold stories of Visma with Øystein Moan What did Visma look like in its early days? Are there any decisions our former CEO would have made differently? Read more Ep 06: Measure what matters: Employee engagement with Vibeke Müller Research shows that having engaged, happy employees is so important for building a great company culture and performing better financially. Read more Ep 05: Our Team Visma | Lease a Bike sponsorship with Anne-Grethe Thomle Karlsen It’s one thing to sponsor the world’s best cycling team; it’s a whole other thing to provide software and expertise that helps them do what they do best. Read more Ep 04: “How do you make people care about security?” with Joakim Tauren With over 700 applications across the Visma Group (and counting!), cybersecurity is make-or-break for us. Read more Ep 03: The human side of enterprise with Yvette Hoogewerf As a software company, our products are central to our business… but that’s only one part of the equation. Read more Ep 02: From Management Trainee to CFO with Stian Grindheim How does someone work their way up from Management Trainee to CFO by the age of 30? And balance fatherhood alongside it all? Read more Ep 01: An optimistic look at the future of AI with Jacob Nyman We’re all-too familiar with the fears surrounding artificial intelligence. So today, Jacob and Johan are flipping the script. Read more (Trailer) Introducing: Voice of Visma These are the stories that shape us... and the reason Visma is unlike anywhere else. Read more Visma Software International AS Organisation number: 980858073 MVA (Foretaksregisteret/The Register of Business Enterprises) Main office Karenslyst allé 56 0277 Oslo Norway Postal address PO box 733, Skøyen 0214 Oslo Norway visma@visma.com Visma on LinkedIn Who we are About us Technology at Visma Sustainability Become a Visma company Our sponsorship Contact us What we offer For small businesses For accounting offices For medium businesses For public sector For partners e-invoicing Digital signature For investors Overview Financials Governance Events Careers Careers at Visma Open positions Hubs Resources Blog Trust Centre Community News Press ©️ 2026 Visma Privacy policy Cookie policy Whistleblowing Cookies settings Transparency Act Change country | 2026-01-13T09:30:34 |
https://support.microsoft.com/zh-cn/windows/%E5%9C%A8-microsoft-edge-%E4%B8%AD%E7%AE%A1%E7%90%86-cookie-%E6%9F%A5%E7%9C%8B-%E5%85%81%E8%AE%B8-%E9%98%BB%E6%AD%A2-%E5%88%A0%E9%99%A4%E5%92%8C%E4%BD%BF%E7%94%A8-168dab11-0753-043d-7c16-ede5947fc64d | 在 Microsoft Edge 中管理 Cookie：查看、允许、阻止、删除和使用 - Microsoft 支持 相关主题 × Windows 安全、安全和隐私 概述 安全性、安全和隐私概述 Windows 安全中心 获取有关 Windows 安全的帮助 通过 Windows 安全获得长久保护 在回收、销售或赠送 Xbox 或 Windows 电脑之前 从 Windows 电脑中移除恶意软件 Windows 安全 获取有关 Windows 安全的帮助 在 Microsoft Edge 中查看和删除浏览器历史记录 删除和管理 Cookie 重新安装 Windows 时安全移除有价值的内容 查找并锁定丢失的 Windows 设备 Windows 隐私 获取有关 Windows 隐私的帮助 应用使用的 Windows 隐私设置 在隐私仪表板上查看你的数据 跳转至主内容 Microsoft 支持 支持 支持 主页 Microsoft 365 Office 产品 Microsoft 365 Outlook Microsoft Teams OneDrive Microsoft Copilot OneNote Windows 更多信息 ... 设备 Surface 电脑配件 Xbox PC 游戏 HoloLens Surface Hub 硬件保修 帐户和计费 帐户 Microsoft Store 和计费 资源 新增功能 社区论坛 Microsoft 365 管理员 小型企业门户 开发人员 教育 上报支持欺诈 产品安全 更多 购买 Microsoft 365 所有 Microsoft Global Microsoft 365 Teams Windows Surface Xbox 折扣专区 企业购 支持 软件 软件 Windows 应用 AI OneDrive Outlook 从 Skype 转到 Teams OneNote Microsoft Teams PC 和设备 PC 和设备 购买 Xbox PC 和平板电脑 配件 娱乐 娱乐 Xbox 与游戏 PC 游戏 企业 企业 Microsoft 安全 Azure Dynamics 365 Microsoft 365 商业版 Microsoft 行业 Microsoft Power Platform 开发人员与 IT 开发人员与 IT Microsoft 开发人员 Microsoft Learn 支持 AI 商城应用 Microsoft 技术社区 Microsoft Marketplace Visual Studio Marketplace Rewards 其他 其他 免费下载与安全性 教育 查看站点地图 搜索 搜索帮助 无结果 取消 登录 使用 Microsoft 登录 登录或创建帐户。 你好， 使用其他帐户。 你有多个帐户 选择要登录的帐户。 相关主题 Windows 安全、安全和隐私 概述 安全性、安全和隐私概述 Windows 安全中心 获取有关 Windows 安全的帮助 通过 Windows 安全获得长久保护 在回收、销售或赠送 Xbox 或 Windows 电脑之前 从 Windows 电脑中移除恶意软件 Windows 安全 获取有关 Windows 安全的帮助 在 Microsoft Edge 中查看和删除浏览器历史记录 删除和管理 Cookie 重新安装 Windows 时安全移除有价值的内容 查找并锁定丢失的 Windows 设备 Windows 隐私 获取有关 Windows 隐私的帮助 应用使用的 Windows 隐私设置 在隐私仪表板上查看你的数据 在 Microsoft Edge 中管理 Cookie：查看、允许、阻止、删除和使用 应用对象 Windows 10 Windows 11 Microsoft Edge Cookie 是你访问的网站存储在设备上的小块数据。 它们有多种用途，例如记住登录凭据、站点首选项和跟踪用户行为。 但是，出于隐私原因或解决浏览问题，你可能想要删除 Cookie。 本文提供有关如何： 查看所有 Cookie 允许所有 Cookie 允许来自特定网站的 Cookie 阻止第三方 Cookie “阻止所有 Cookie” 阻止来自特定站点的 Cookie 删除所有 Cookie 删除特定网站中的 Cookie 每次关闭浏览器时都删除 Cookie 使用 Cookie 预加载页面以加快浏览速度 查看所有 Cookie 打开 Edge 浏览器，选择浏览器窗口右上角的 “设置”等 。 选择 “设置” > “隐私”、“搜索和服务 ”。 选择 “Cookie” ，然后单击“ 查看所有 Cookie 和站点数据 ”，查看所有存储的 Cookie 和相关站点信息。 允许所有 Cookie 通过允许 Cookie，网站将能够在你的浏览器中保存和检索数据，这可以通过记住你的首选项和登录信息来增强你的浏览体验。 打开 Edge 浏览器，选择浏览器窗口右上角的 “设置”等 。 选择 “设置” > “隐私”、“搜索和服务 ”。 选择 “Cookie” 并启用“ 允许站点保存和读取 Cookie 数据 (建议) 以允许所有 Cookie 的切换。 允许来自特定站点的 Cookie 通过允许 Cookie，网站将能够在你的浏览器中保存和检索数据，这可以通过记住你的首选项和登录信息来增强你的浏览体验。 打开 Edge 浏览器，选择浏览器窗口右上角的 “设置”等 。 选择 “设置” > “隐私”、“搜索和服务 ”。 选择 “Cookie” 并转到 “允许”以保存 Cookie。 选择“ 添加站点 ”，通过输入站点的 URL，允许每个站点的 Cookie。 阻止第三方 Cookie 如果你不希望第三方站点在你的电脑上存储 Cookie，则可以阻止 Cookie。 但是执行此操作可能会导致某些页面无法正确显示，或者可能会从站点收到一条消息，通知你需要允许 Cookie 才能查看该站点。 打开 Edge 浏览器，选择浏览器窗口右上角的 “设置”等 。 选择 “设置” > “隐私”、“搜索和服务 ”。 选择“ Cookie” 并启用“ 阻止第三方 Cookie”切换。 “阻止所有 Cookie” 如果你不希望第三方站点在你的电脑上存储 Cookie，则可以阻止 Cookie。 但是执行此操作可能会导致某些页面无法正确显示，或者可能会从站点收到一条消息，通知你需要允许 Cookie 才能查看该站点。 打开 Edge 浏览器，选择浏览器窗口右上角的 “设置”等 。 选择 “设置” > “隐私”、“搜索和服务 ”。 选择 “Cookie” 并禁用 “允许站点保存和读取 cookie 数据 (建议) 阻止所有 Cookie。 阻止来自特定站点的 Cookie Microsoft Edge 允许阻止来自特定网站的 Cookie，但这样做可能会阻止某些页面正确显示，或者你可能会从网站收到一条消息，告知你需要允许 Cookie 查看该网站。 阻止来自特定站点的 Cookie： 打开 Edge 浏览器，选择浏览器窗口右上角的 “设置”等 。 选择 “设置” > “隐私”、“搜索和服务 ”。 选择 “Cookie” 并转到 “不允许保存和读取 Cookie ”。 选择 “添加 站点 ”，通过输入站点的 URL 来阻止每个站点的 Cookie。 删除所有 Cookie 打开 Edge 浏览器，选择浏览器窗口右上角的 “设置”等 。 选择 设置>“ > 隐私、搜索和服务 。 选择“ 清除浏览数据 ”，然后选择“ 立即清除浏览数据 ”旁边的“ 选择要清除的内容 ”。 在 时间范围 下，选择时间范围。 选择 “Cookie 和其他网站数据” ，然后选择 “立即清除” 。 注意: 或者，可以同时按 Ctrl + SHIFT + DELETE ，然后继续执行步骤 4 和 5，删除 Cookie。 现在将删除所选时间范围内的所有 Cookie 和其他站点数据。 这会使你从大多数站点退出登录。 删除特定网站中的 Cookie 打开 Edge 浏览器，选择 “设置”和“更多 > 设置 > 隐私、搜索和服务 ”。 选择 “Cookie” ，然后单击“ 查看所有 Cookie 和站点数据 ”，并搜索要删除其 Cookie 的站点。 选择要删除其 Cookie 的网站右侧的向下箭头 ，然后选择 删除 。 所选站点的 Cookie 现在已删除。 对要删除其 Cookie 的任何网站重复此步骤。 每次关闭浏览器时都删除 Cookie 打开 Edge 浏览器，选择 “设置和更多 > 设置 > 隐私、搜索和服务 ”。 选择“ 清除浏览数据 ”，然后选择“ 选择每次关闭浏览器时要清除的内容 ”。 打开 Cookie 和其他网站数据 切换开关。 启用此功能后，每次关闭 Edge 浏览器时，都会删除所有 Cookie 和其他站点数据。 这会使你从大多数站点退出登录。 使用 Cookie 预加载页面以加快浏览速度 打开 Edge 浏览器，选择浏览器窗口右上角的 “设置”等 。 选择 设置>“ > 隐私、搜索和服务 。 选择 “Cookie” 并启用切换“ 预加载页面”以加快浏览和搜索速度。 订阅 RSS 源 需要更多帮助? 需要更多选项? 发现 社区 联系我们 了解订阅权益、浏览培训课程、了解如何保护设备等。 Microsoft 365 订阅权益 Microsoft 365 培训 Microsoft 安全性 辅助功能中心 社区可帮助你提出和回答问题、提供反馈，并听取经验丰富专家的意见。 咨询 Microsoft 社区 Microsoft 技术社区 Windows 预览体验成员 Microsoft 365 预览体验 查找常见问题的解决方案或从支持代理获取帮助。 联机支持 此信息是否有帮助? 是 否 谢谢!还有关于 Microsoft 的反馈吗? 你能帮助我们改进吗? (向 Microsoft 发送反馈，以便我们提供帮助。) 你对语言质量的满意程度如何? 哪些因素影响了你的体验? 解决了我的问题 指示清晰 易于理解 无行话 图片有帮助 翻译质量 与屏幕上显示的不一致 错误说明 技术性太强 信息还少 图片太少 翻译质量 是否还有其他反馈? (可选) 提交反馈 按“提交”即表示你的反馈将用于改进 Microsoft 产品和服务。 你的 IT 管理员将能够收集此数据。 隐私声明。 谢谢您的反馈！ × 新增内容 Surface Pro Surface Laptop 适用于组织的 Copilot Microsoft 365 探索 Microsoft 产品 Windows 11 应用程序 Microsoft Store 帐户个人资料 下载中心 订单跟踪 教育 Microsoft 教育版 教育设备 Microsoft Teams 教育版 Microsoft 365 教育版 Office 教育版 教育工作者培训和开发 面向学生和家长的优惠 面向学生的 Azure 企业 Microsoft 安全 Azure Dynamics 365 Microsoft 365 Microsoft Advertising Microsoft 365 Copilot Microsoft Teams 开发人员与 IT Microsoft 开发人员 Microsoft Learn 支持 AI 商城应用 Microsoft 技术社区 Microsoft Marketplace Microsoft Power Platform Marketplace Rewards Visual Studio 公司 招贤纳士 关于 Microsoft 公司新闻 Microsoft 隐私 投资人 可持续发展 中文(中国) 你的隐私选择选择退出图标 你的隐私选择 你的隐私选择选择退出图标 你的隐私选择 消费者健康隐私 与 Microsoft 联系 隐私 管理 Cookie 使用条款 商标 关于我们的广告 京ICP备09042378号-6 © Microsoft 2026 | 2026-01-13T09:30:34 |
https://support.microsoft.com/ko-kr/windows/microsoft-edge%EC%97%90%EC%84%9C-%EC%BF%A0%ED%82%A4-%EA%B4%80%EB%A6%AC-%EB%B3%B4%EA%B8%B0-%ED%97%88%EC%9A%A9-%EC%B0%A8%EB%8B%A8-%EC%82%AD%EC%A0%9C-%EB%B0%8F-%EC%82%AC%EC%9A%A9-168dab11-0753-043d-7c16-ede5947fc64d | Microsoft Edge에서 쿠키 관리: 보기, 허용, 차단, 삭제 및 사용 - Microsoft 지원 관련 주제 × Windows 보안, 안전 및 개인 정보 개요 보안, 안전 및 개인 정보 개요 Windows 보안 Windows 보안에 대한 도움말 보기 Windows 보안으로 보호 유지 Xbox 또는 Windows PC 재활용, 판매 또는 선물하기 전에 Windows PC에서 맬웨어 제거 Windows 안전 Windows 안전에 대한 도움말 보기 Microsoft Edge에서 브라우저 기록 보기 및 삭제 쿠키 삭제 및 관리 Windows를 다시 설치할 때 중요한 콘텐츠를 안전하게 제거 분실한 Windows 장치 찾기 및 잠금 Windows 개인 정보 보호 Windows 개인 정보 보호에 대한 도움말 보기 앱에서 사용하는 Windows 개인 정보 설정 개인 정보 대시보드에서 사용자 데이터 보기 주 콘텐츠로 건너뛰기 Microsoft 고객 지원 고객 지원 고객 지원 홈 Microsoft 365 Office 제품 Microsoft 365 Outlook Microsoft Teams OneDrive Microsoft Copilot OneNote Windows 기타... 장치 Surface PC 액세서리 Xbox PC 게임 HoloLens Surface Hub 하드웨어 보증 계정 및 청구 계정 Microsoft Store & 청구 리소스 새로운 기능 커뮤니티 포럼 Microsoft 365 관리자 소규모 비즈니스 포털 개발자 교육 지원 사기 보고 제품 안전 자세히 Microsoft 365 구입 Microsoft 전체 Global Microsoft 365 Teams Copilot Windows Surface Xbox 세일 지원 소프트웨어 소프트웨어 Windows 앱 AI OneDrive Outlook Skype에서 Teams로 이동 중 OneNote Microsoft Teams PC 및 장치 PC 및 장치 Xbox 쇼핑 주변 기기 엔터테인먼트 엔터테인먼트 Xbox Game Pass Ultimate Xbox 및 게임 PC 게임 기업 고객용 기업 고객용 Microsoft Security Azure Dynamics 365 비즈니스용 Microsoft 365 Microsoft Industry Microsoft Power Platform Windows 365 개발자 및 IT 개발자 및 IT Microsoft 개발자 Microsoft Learn AI 마켓플레이스 앱 지원 Microsoft Tech 커뮤니티 Microsoft Marketplace Visual Studio Marketplace Rewards 기타 기타 무료 다운로드 및 보안 교육 볼륨 라이선싱 사이트맵 보기 검색 도움말 검색 결과 없음 취소 로그인 Microsoft로 로그인 로그인하거나 계정을 만듭니다. 안녕하세요. 다른 계정을 선택합니다. 계정이 여러 개 있음 로그인할 계정을 선택합니다. 관련 주제 Windows 보안, 안전 및 개인 정보 개요 보안, 안전 및 개인 정보 개요 Windows 보안 Windows 보안에 대한 도움말 보기 Windows 보안으로 보호 유지 Xbox 또는 Windows PC 재활용, 판매 또는 선물하기 전에 Windows PC에서 맬웨어 제거 Windows 안전 Windows 안전에 대한 도움말 보기 Microsoft Edge에서 브라우저 기록 보기 및 삭제 쿠키 삭제 및 관리 Windows를 다시 설치할 때 중요한 콘텐츠를 안전하게 제거 분실한 Windows 장치 찾기 및 잠금 Windows 개인 정보 보호 Windows 개인 정보 보호에 대한 도움말 보기 앱에서 사용하는 Windows 개인 정보 설정 개인 정보 대시보드에서 사용자 데이터 보기 Microsoft Edge에서 쿠키 관리: 보기, 허용, 차단, 삭제 및 사용 적용 대상 Windows 10 Windows 11 Microsoft Edge 쿠키는 방문하는 웹 사이트에서 디바이스에 저장된 작은 데이터 조각입니다. 로그인 자격 증명 기억, 사이트 기본 설정, 사용자 동작 추적 등 다양한 용도로 사용됩니다. 그러나 개인 정보 보호를 위해 쿠키를 삭제하거나 검색 문제를 resolve 수 있습니다. 이 문서에서는 다음 방법에 대한 지침을 제공합니다. 모든 쿠키 보기 모든 쿠키 허용 특정 웹 사이트에서 쿠키 허용 타사 쿠키 차단 모든 쿠키 차단은 특정 사이트에서 쿠키 차단 모든 쿠키 삭제 특정 사이트에서 쿠키 삭제 브라우저를 닫을 때마다 쿠키 삭제 쿠키를 사용하여 더 빠른 검색을 위해 페이지를 미리 로드합니다. 모든 쿠키 보기 Edge 브라우저를 열고 브라우저 창의 오른쪽 위 모서리에서 설정 등을 선택합니다. 설정 > 개인 정보, 검색 및 서비스를 선택합니다. 쿠키를 선택한 다음 모든 쿠키 및 사이트 데이터 보기를 클릭하여 저장된 모든 쿠키 및 관련 사이트 정보를 확인합니다. 모든 쿠키 허용 쿠키를 허용하면 웹 사이트에서 브라우저에서 데이터를 저장하고 검색할 수 있으므로 기본 설정 및 로그인 정보를 기억하여 검색 환경을 향상시킬 수 있습니다. Edge 브라우저를 열고 브라우저 창의 오른쪽 위 모서리에서 설정 등을 선택합니다. 설정 > 개인 정보, 검색 및 서비스를 선택합니다. 쿠키를 선택하고 모든 쿠키를 허용 하도록 사이트에서 쿠키 데이터를 저장하고 읽을 수 있도록 허용(권장) 토글을 사용하도록 설정합니다. 특정 사이트에서 쿠키 허용 쿠키를 허용하면 웹 사이트에서 브라우저에서 데이터를 저장하고 검색할 수 있으므로 기본 설정 및 로그인 정보를 기억하여 검색 환경을 향상시킬 수 있습니다. Edge 브라우저를 열고 브라우저 창의 오른쪽 위 모서리에서 설정 등을 선택합니다. 설정 > 개인 정보, 검색 및 서비스를 선택합니다. 쿠키를 선택하고 허용됨으로 이동하여 쿠키를 저장합니다. 사이트 추가 를 선택하여 사이트의 URL을 입력하여 사이트별로 쿠키를 허용합니다. 타사 쿠키 차단 타사 사이트에서 PC에 쿠키를 저장하지 않으려면 쿠키를 차단할 수 있습니다. 그러나 쿠키를 차단하면 일부 페이지가 올바르게 표시되지 않거나 사이트를 보려면 쿠키를 허용해야 한다는 메시지가 표시될 수 있습니다. Edge 브라우저를 열고 브라우저 창의 오른쪽 위 모서리에서 설정 등을 선택합니다. 설정 > 개인 정보, 검색 및 서비스를 선택합니다. 쿠키를 선택하고 타사 쿠키 차단 토글을 사용하도록 설정합니다. 모든 쿠키 차단은 타사 사이트에서 PC에 쿠키를 저장하지 않으려면 쿠키를 차단할 수 있습니다. 그러나 쿠키를 차단하면 일부 페이지가 올바르게 표시되지 않거나 사이트를 보려면 쿠키를 허용해야 한다는 메시지가 표시될 수 있습니다. Edge 브라우저를 열고 브라우저 창의 오른쪽 위 모서리에서 설정 등을 선택합니다. 설정 > 개인 정보, 검색 및 서비스를 선택합니다. 쿠키를 선택하고 사이트에서 쿠키 데이터를 저장하고 읽을 수 있도록 허용(권장) 을 사용하지 않도록 설정하여 모든 쿠키를 차단합니다. 특정 사이트에서 쿠키 차단 Microsoft Edge를 사용하면 특정 사이트의 쿠키를 차단할 수 있지만 이렇게 하면 일부 페이지가 올바르게 표시되지 않거나 쿠키가 해당 사이트를 볼 수 있도록 허용해야 한다는 메시지가 사이트에서 수신될 수 있습니다. 특정 사이트에서 쿠키를 차단하려면 다음을 수행합니다. Edge 브라우저를 열고 브라우저 창의 오른쪽 위 모서리에서 설정 등을 선택합니다. 설정 > 개인 정보, 검색 및 서비스를 선택합니다. 쿠키를 선택하고 쿠키를 저장하고 읽을 수 없음으로 이동합니다. 사이트 추가 를 선택하여 사이트의 URL을 입력하여 사이트별로 쿠키를 차단합니다. 모든 쿠키 삭제 Edge 브라우저를 열고 브라우저 창의 오른쪽 위 모서리에서 설정 등을 선택합니다. 설정 > 개인 정보, 검색 및 서비스 를 선택합니다. 검색 데이터 지우기를 선택한 다음, 지금 검색 데이터 지우 기 옆에 있는 선택을 선택합니다 . 시간 범위 의 목록에서 시간 범위를 선택합니다. 쿠키 및 기타 사이트 데이터 를 선택한 다음 지금 지우기 를 선택합니다. 참고: 또는 Ctrl + Shift + DELETE 를 함께 누 른 다음 4단계와 5단계를 진행하여 쿠키를 삭제할 수 있습니다. 이제 선택한 시간 범위에 대한 모든 쿠키 및 기타 사이트 데이터가 삭제됩니다. 대부분의 사이트에서 로그아웃됩니다. 특정 사이트에서 쿠키 삭제 Edge 브라우저를 열고 설정 및 기타 > 설정 > 개인 정보, 검색 및 서비스를 선택합니다. 쿠키를 선택한 다음 모든 쿠키 및 사이트 데이터 보기를 클릭하고 쿠키를 삭제하려는 사이트를 검색합니다. 삭제하려는 쿠키가 있는 사이트 오른쪽에 있는 아래쪽 화살표 를 선택하고 삭제 를 선택합니다. 선택한 사이트의 쿠키는 이제 삭제됩니다. 쿠키를 삭제하려는 모든 사이트에 대해 이 단계를 반복합니다. 브라우저를 닫을 때마다 쿠키 삭제 Edge 브라우저를 열고 설정 및 기타 > 설정 > 개인 정보, 검색 및 서비스를 선택합니다. 검색 데이터 지우기를 선택한 다음 브라우저를 닫을 때마다 지울 항목 선택을 선택합니다. 쿠키 및 기타 사이트 데이터 토글을 켭니다. 이 기능이 켜지면 Edge 브라우저를 닫을 때마다 모든 쿠키 및 기타 사이트 데이터가 삭제됩니다. 대부분의 사이트에서 로그아웃됩니다. 쿠키를 사용하여 더 빠른 검색을 위해 페이지를 미리 로드합니다. Edge 브라우저를 열고 브라우저 창의 오른쪽 위 모서리에서 설정 등을 선택합니다. 설정 > 개인 정보, 검색 및 서비스 를 선택합니다. 쿠키를 선택하고 빠른 검색 및 검색을 위해 페이지 미리 로드 토글을 사용하도록 설정합니다. RSS 피드 구독 도움이 더 필요하세요? 더 많은 옵션을 원하세요? 검색 커뮤니티 문의 구독 혜택을 살펴보고, 교육 과정을 찾아보고, 디바이스를 보호하는 방법 등을 알아봅니다. Microsoft 365 구독 혜택 Microsoft 365 교육 Microsoft 보안 접근성 센터 커뮤니티를 통해 질문하고 답변하고, 피드백을 제공하고, 풍부한 지식을 갖춘 전문가의 의견을 들을 수 있습니다. Microsoft 커뮤니티에 질문하기 Microsoft Tech Community Windows 참가자 Microsoft 365 참가자 일반적인 문제에 대한 해결 방법을 찾거나 지원 에이전트로부터 도움을 받으세요. 온라인 지원 이 정보가 유용한가요? 예 아니요 감사합니다. Microsoft에 대한 피드백이 더 있으신가요? 사용자 환경 개선에 도움을 주시겠어요? (Microsoft에 피드백을 보내 주시면 도움을 드리겠습니다.) 언어 품질에 얼마나 만족하시나요? 사용 경험에 어떠한 영향을 주었나요? 문제가 해결됨 지침이 명확함 이해하기 쉬움 전문 용어가 없음 그림이 도움이 됨 번역 품질 내 화면과 일치하지 않음 지침이 잘못됨 너무 기술적임 정보가 부족함 그림이 부족함 번역 품질 추가 피드백이 있으신가요? (선택 사항) 피드백 제출 제출을 누르면 피드백이 Microsoft 제품과 서비스를 개선하는 데 사용됩니다. IT 관리자는 이 데이터를 수집할 수 있습니다. 개인정보처리방침 의견 주셔서 감사합니다! × 새로운 기능 Surface Pro Surface Laptop 조직용 Copilot 개인 사용자용 Copilot Microsoft 365 Microsoft 제품 살펴보기 Windows 11 앱 Microsoft Store 계정 프로필 다운로드 센터 Microsoft Store 지원 반품/환불 주문 조회 교육 Microsoft Education 교육용 장치 교육용 Microsoft Teams Microsoft 365 Education Office Education 교육자 트레이닝 및 개발 학생 및 학부모용 특가 혜택 Azure for students 기업 고객 Microsoft Security Azure Dynamics 365 Microsoft 365 Microsoft Advertising Microsoft 365 Copilot Microsoft Teams 개발자 및 IT Microsoft 개발자 Microsoft Learn AI 마켓플레이스 앱 지원 Microsoft Tech 커뮤니티 Microsoft Marketplace Microsoft Power Platform Marketplace Rewards Visual Studio 회사 채용 정보 Microsoft 정보 회사 뉴스 Microsoft 개인 정보 보호 투자자 지속 가능성 한국어(대한민국) 개인정보처리방침 선택 옵트아웃 아이콘 개인 정보 선택 사항 개인정보처리방침 선택 옵트아웃 아이콘 개인 정보 선택 사항 소비자 상태 개인정보처리방침 Microsoft에 문의 개인정보처리방침 및 위치정보이용약관 쿠키 관리 사용약관 상표 광고 정보 © Microsoft 2026 한국마이크로소프트(유) 대표이사: 조원우 주소: (우)110-150 서울 종로구 종로1길 50 더 케이트윈타워 A동 12층 전화번호: 02-531-4500, 메일: ms-korea@microsoft.com 사업자등록번호: 120-81-05948 사업자정보확인 호스팅서비스 제공자: Microsoft Corporation 통신판매신고: 제2013-서울종로-1009호 사이버몰의 이용약관: Microsoft Store 판매 약관 | 2026-01-13T09:30:34 |
https://llvmweekly.org/issue/554 | LLVM Weekly - #554, August 12th 2024 LLVM Weekly - #554, August 12th 2024 Welcome to the five hundred and fifty-fourth issue of LLVM Weekly, a weekly newsletter (published every Monday) covering developments in LLVM, Clang, and related projects. LLVM Weekly is brought to you by Alex Bradbury . Subscribe to future issues at http://llvmweekly.org and pass it on to anyone else you think may be interested. Please send any tips or feedback to asb@asbradbury.org , @llvmweekly or @asbradbury on Twitter, or @llvmweekly@fosstodon.org or @asb@fosstodon.org . News and articles from around the web and events Registration is now open for the 2024 LLVM Developers' Meeting , and the full/half day workshops ahve been announced. More details have been posted about the LLVM :hearts: ML Workshop , and the talk submission deadline for the mean Dev Meeting has been extended by a single day (today). Min-Yih Hsu blogged about scheduling models in LLVM . Ramkumar Ramachandra blogged about auto-vectorization in LLVM and introducing LLVM backends . The next Toronto LLVM meetup will take place on August 15th and feature talks on “Catalyst: An AOT/JIT compiler for accelerated quantum computing in Python” and “DPC++ SYCL Compiler”. The monthly LLVM Bay Area meetup is taking place today (12th August) . According to the LLVM calendar in the coming week there will be the following: Office hours with the following hosts: Aaron Ballman, Alexey Bader, Kristof Beyls, Johannes Doerfert. Online sync-ups on the following topics: pointer authentication, new contributors, OpenMP, Flang, BOLT, RISC-V, MLIR, embedded toolchains. For more details see the LLVM calendar , getting involved documentation on online sync ups and office hours . On the forums “higher-performance” proposed adding a new attribute to Clang that ensures a warning is produced if fields aren’t explicitly initialised . “rahulana-quic” initiated an RFC on adding a new structure layout optimization pass which has generated a fair bit of discussion. “n-omer” started an RFC discussion on implementing a way to inform the compiler that a function is a fiber suspend point . Maksim Kita proposed adding a force_vectorize pragma to Clang . Chaitanya Shahare is still seeking feedback on the proposed llvm.org website redesign . Schrodinger Zhu kicked off a discussion on flat-combining in LLVM’s libc](https://discourse.llvm.org/t/libc-rfc-introduce-mcs-based-flat-combining-lambda-lock/80543). The question of renaming flang-new to flang was raised again . Yaxun (Sam) Liu suggested adding a new atomic progma to Clang to allow greater control over atomics lowering . LLVM commits Basic block numbers are now used to store dominator tree nodes in a vector. c2f92fa , d871b2e . If --skip-line-zero is passed, LLVM symbolizer can now report the nearest non-zero line number if it can’t get the correct line number. 0886440 . The ExpandVP pass was merged into PreISelIntrinsicLowering. fa92d51 . The NVPTX backend gained support for Volta’s sequentially consistent load and store operations. f55abd5 . A LoongArchMergeBaseOffset pass was added. b2e69f5 . riscv-experimental-rv64-legal-i32 was backed out for now as it’s not receiving active development attention. ca7ad38 . A merge-release-pr.py script was added to help release managers merge backports PRs. f3e950a . IRBuilder now generates nuw GEPs for struct member accesses. 94473f4 . Clang commits Builtins were added for the AVX10.2-SATCVT instructions. 80721e0 . Single-element accesses to GCC vector/ext_vector_type objects can now be used in constant expressions. 7753429 . attribute((rvv_vector_bits(N))) can now be used when N < 8 . 635d20e . Other project commits LLVM’s libopenmp can now compile and run under the emscripten WebAssembly toolchain. f7b2c2e . Spin lock family functions were added to LLVM’s libc. 03841e7 . “Edit this page” links were added to LLDB’s generated documentation. 2771ce8 . MLIR’s documentation for scalable vectors was updated. 673604a . mlir-opt now has a --list-passes option. 5e6d5c0 . Subscribe at LLVMWeekly.org . | 2026-01-13T09:30:34 |
https://llvmweekly.org/issue/538 | LLVM Weekly - #538, April 22nd 2024 LLVM Weekly - #538, April 22nd 2024 Welcome to the five hundred and thirty-eighth issue of LLVM Weekly, a weekly newsletter (published every Monday) covering developments in LLVM, Clang, and related projects. LLVM Weekly is brought to you by Alex Bradbury . Subscribe to future issues at http://llvmweekly.org and pass it on to anyone else you think may be interested. Please send any tips or feedback to asb@asbradbury.org , @llvmweekly or @asbradbury on Twitter, or @llvmweekly@fosstodon.org or @asb@fosstodon.org . News and articles from around the web and events LLVM 18.1.4 was released . The next Bay Area LLVM dev meeting is today . John Regehr blogged about dataflow analyses and compiler optimisations that use them . According to the LLVM calendar in the coming week there will be the following: Office hours with the following hosts: Kristof Beyls, Johannes Doerfert, Amara Emerson. Online sync-ups on the following topics: SPIR-V, new contributors, OpenMP, Flang, RISC-V, MLIR open meeting, LLVM embedded toolchains. For more details see the LLVM calendar , getting involved documentation on online sync ups and office hours . On the forums Slides from the MLIR workshop at EuroLLVM are now available . Venkata Ramanaiah Nalamothu posted an RFC on providing a ROM patching mechanism for embedded applications . Florian Hahn provided an update on the set of patches to revive TypeSanitizer . Mark de Wever suggested adding native lit support for C++ version compatibility in e.g. libcxx tests, meaning <=c++23 could be used rather than listing all C++ standards prior to C++23. Tom Stellard is seeking LLVM developers who will admit to having “secure development knowledge” . Fangrui Song proposed a update_test_body.py utility script to simplify creating test cases from C inputs , motivated by the various manually updated debuginfo tests that frequently have comments describing the C input used to create them. Renato Golin posted notes from the MLIR upstream round table at EuroLLVM . Hans Wennborg and Reid Kleckner shared notes from the project governance roundtable at EuroLLVM . Mircea Trofin posted an RFC on contextual profile instrumentation . Pierre van Houtryve started an RFC discussion on measuring GlobalISel compile-time performance . Kristof Beyls shared a summary of the EuroLLVM roundtable on using BOLT as a binary analysis tool . Kristof Beyls shared an update on behalf of the LLVM Foundation board, that the requirement to contribute under the old LLVM license as well as the new one will be dropped . Maciej Gabka proposes promoting various vector intrinsics from the experimental namespace . J Ryan Stinnett distributed notes from the debug info round table at EuroLLVM . Jeremy Kun proposed upstreaming a tutorial on MLIR for beginners . LLVM commits Latencies were updated for the Cortex-A510 scheduling model. cc82f12 . llvm-objcopy now has a --compress-sections option. 0794298 . Backends can now implement verification of target SelectionDAG nodes. 7089c35 . Scheduling information was added for SiFive VCIX instructions. 6da1966 . Debugify gained support for debug variable records. 1c6b0f7 . InstCombine now canonicalises sitofp to uitofp nneg . b6bd41d . Clang commits -fexperimental-modules-reduced-bmi was introduced and documented (see the second commit for a full write-up). f811d7b , e6ecff8 . The __builtin_is_align{ed,_up,_down} builtins were implemented for the Clang interpreter. 75244a1 . __builtin_allow_runtime_check was implemented. 1f35e72 . Other project commits The beginnings of a polynomial dialect were committed to MLIR. 55b6f17 . MLIR’s mem2reg partial load support was improved. ac39fa7 . The sanitizers in compiler-rt moved to using __atomic builtins wherever possible. abd5e45 . The pthread_condattr_t functions were implemented in LLVM’s libc. 06947b9 . --debug-names was introduced to LLD’s ELF linker to create merged .debug_names . 16711b43 . Subscribe at LLVMWeekly.org . | 2026-01-13T09:30:34 |
http://docs.buildbot.net/current/manual/configuration/steps/index.html | 2.5.13. Build Steps — Buildbot 4.3.0 documentation Buildbot 1. Buildbot Tutorial 2. Buildbot Manual 2.1. Introduction 2.2. Installation 2.3. Concepts 2.4. Secret Management 2.5. Configuration 2.5.1. Configuring Buildbot 2.5.2. Global Configuration 2.5.3. Change Sources and Changes 2.5.4. Changes 2.5.5. Schedulers 2.5.6. Workers 2.5.7. Builder Configuration 2.5.8. Projects 2.5.9. Codebases 2.5.10. Build Factories 2.5.11. Build Sets 2.5.12. Properties 2.5.13. Build Steps 2.5.13.1. Parameters Common to all Steps 2.5.13.2. Common Parameters of source checkout operations 2.5.13.3. Bzr 2.5.13.4. CVS 2.5.13.5. Darcs 2.5.13.6. Gerrit 2.5.13.7. GitHub 2.5.13.8. GitLab 2.5.13.9. Git 2.5.13.10. Mercurial 2.5.13.11. Monotone 2.5.13.12. P4 2.5.13.13. Repo 2.5.13.14. SVN 2.5.13.15. GitCommit 2.5.13.16. GitTag 2.5.13.17. GitPush 2.5.13.18. GitDiffInfo 2.5.13.19. ShellCommand 2.5.13.20. Shell Sequence 2.5.13.21. Compile 2.5.13.22. Configure 2.5.13.23. CMake 2.5.13.24. Visual C++ 2.5.13.25. Cppcheck 2.5.13.26. Robocopy 2.5.13.27. Test 2.5.13.28. TreeSize 2.5.13.29. PerlModuleTest 2.5.13.30. SubunitShellCommand 2.5.13.31. HLint 2.5.13.32. MaxQ 2.5.13.33. Trigger 2.5.13.34. BuildEPYDoc 2.5.13.35. PyFlakes 2.5.13.36. Sphinx 2.5.13.37. PyLint 2.5.13.38. Trial 2.5.13.39. RemovePYCs 2.5.13.40. HTTP Requests 2.5.13.41. Worker Filesystem Steps 2.5.13.42. Transferring Files 2.5.13.43. Transferring Strings 2.5.13.44. MasterShellCommand 2.5.13.45. LogRenderable 2.5.13.46. Assert 2.5.13.47. SetProperty 2.5.13.48. SetProperties 2.5.13.49. SetPropertyFromCommand buildbot.steps.worker.SetPropertiesFromEnv 2.5.13.50. SetPropertiesFromEnv 2.5.13.51. RpmBuild 2.5.13.52. RpmLint 2.5.13.53. MockBuildSRPM Step 2.5.13.54. MockRebuild 2.5.13.55. DebPbuilder 2.5.13.56. DebCowbuilder 2.5.13.57. DebLintian 2.5.13.58. Build steps 2.5.14. Interlocks 2.5.15. Report Generators 2.5.16. Reporters 2.5.17. Web Server 2.5.18. Change Hooks 2.5.19. Custom Services 2.5.20. DbConfig 2.5.21. Configurators 2.5.22. Manhole 2.5.23. Multimaster 2.5.24. Multiple-Codebase Builds 2.5.25. Miscellaneous Configuration 2.5.26. Testing Utilities 2.6. Customization 2.7. Command-line Tool 2.8. Resources 2.9. Optimization 2.10. Plugin Infrastructure in Buildbot 2.11. Deployment 2.12. Upgrading 3. Buildbot Development 4. Release Notes 5. Older Release Notes 6. API Indices Buildbot 2. Buildbot Manual 2.5. Configuration 2.5.13. Build Steps View page source 2.5.13. Build Steps BuildStep s are usually specified in the buildmaster’s configuration file, in a list that given to a BuildFactory . The BuildStep instances in this list are used as templates to construct new independent copies for each build (so that state can be kept on the BuildStep in one build without affecting a later build). Each BuildFactory can be created with a list of steps, or the factory can be created empty and then steps added to it using the addStep method: from buildbot.plugins import util , steps f = util . BuildFactory () f . addSteps ([ steps . SVN ( repourl = "http://svn.example.org/Trunk/" ), steps . ShellCommand ( command = [ "make" , "all" ]), steps . ShellCommand ( command = [ "make" , "test" ]) ]) The basic behavior for a BuildStep is to: run for a while, then stop possibly invoke some RemoteCommands on the attached worker possibly produce a set of log files finish with a status described by one of four values defined in buildbot.process.results : SUCCESS , WARNINGS , FAILURE , SKIPPED provide a list of short strings to describe the step The rest of this section describes all the standard BuildStep objects available for use in a Build , and the parameters that can be used to control each. A full list of build steps is available in the Build Step Index . Build steps 2.5.13.58. Build steps The following build steps are available: Parameters Common to all Steps Source checkout steps - used to checkout the source code Common Parameters of source checkout operations Bzr CVS Darcs Git Gerrit GitHub GitLab Mercurial Monotone P4 Repo SVN Other source-related steps - used to perform non-checkout source operations GitCommit GitTag GitPush GitDiffInfo ShellCommand steps - used to perform various shell-based operations ShellCommand Shell Sequence Compile Configure CMake Visual C++ ( VC<...> , VS<...> , VCExpress9 , MsBuild<... ) Cppcheck Robocopy Test TreeSize PerlModuleTest SubunitShellCommand HLint MaxQ Trigger - triggering other builds Python build steps - used to perform Python-related build operations BuildEPYDoc PyFlakes Sphinx PyLint Trial Debian build steps - used to build deb packages DebPbuilder , DebCowBuilder DebLintian RPM build steps - used to build rpm packages RpmBuild RpmLint MockBuildSRPM Step MockRebuild Transferring Files - used to perform file transfer operations FileUpload FileDownload DirectoryUpload MultipleFileUpload StringDownload JSONStringDownload JSONPropertiesDownload HTTP Requests - used to perform HTTP requests HTTPStep POST GET PUT DELETE HEAD OPTIONS Worker Filesystem Steps - used to perform filesystem operations on the worker FileExists CopyDirectory RemoveDirectory MakeDirectory Master steps - used to perform operations on the build master MasterShellCommand SetProperty SetProperties SetPropertyFromCommand SetPropertiesFromEnv LogRenderable - used to log a renderable property for debugging Assert - used to terminate build depending on condition Previous Next © Copyright Buildbot Team Members. Built with Sphinx using a theme provided by Read the Docs . | 2026-01-13T09:30:34 |
https://es-la.facebook.com/login/?next=https%3A%2F%2Fl.facebook.com%2Fl.php%3Fu%3Dhttps%253A%252F%252Fwww.instagram.com%252F%26amp%253Bh%3DAT1KY84hKm_-by-YRr4vpnWKQpQpwSlqcHtHuJaVKw1bW8wItTohGpLUCnyGOFaKEl24B0RlP8zqhkc8lgjUOBrHeD_3-x2x1wAeaDTMaMg12_UywdHBUwoulr3RtwamghKKTr5Z0_NPtXeL | Facebook Facebook Correo o teléfono Contraseña ¿Olvidaste tu cuenta? Crear cuenta nueva Se te bloqueó temporalmente Se te bloqueó temporalmente Parece que hiciste un uso indebido de esta función al ir muy rápido. Se te bloqueó su uso temporalmente. Back Español 한국어 English (US) Tiếng Việt Bahasa Indonesia ภาษาไทย 中文(简体) 日本語 Português (Brasil) Français (France) Deutsch Registrarte Iniciar sesión Messenger Facebook Lite Video Meta Pay Tienda de Meta Meta Quest Ray-Ban Meta Meta AI Más contenido de Meta AI Instagram Threads Centro de información de votación Política de privacidad Centro de privacidad Información Crear anuncio Crear página Desarrolladores Empleo Cookies Opciones de anuncios Condiciones Ayuda Importación de contactos y no usuarios Configuración Registro de actividad Meta © 2026 | 2026-01-13T09:30:34 |
https://es-la.facebook.com/login/?next=https%3A%2F%2Fl.facebook.com%2Fl.php%3Fu%3Dhttps%253A%252F%252Fwww.instagram.com%252F%26amp%253Bh%3DAT3lN7wpIGgWaTyXErk4SF1WCKEs9PDHJPdbiN3Yl_7Rba5JxYLIit5nb079Cw1WWMDlqJeHCsuW7di_wtBhIrbQwVsBpN2U3fkPKWMYiOrU-c_JuLCa8u7nUnpt80Nm-EprkKK9rPoa2_sw | Facebook Facebook Correo o teléfono Contraseña ¿Olvidaste tu cuenta? Crear cuenta nueva Se te bloqueó temporalmente Se te bloqueó temporalmente Parece que hiciste un uso indebido de esta función al ir muy rápido. Se te bloqueó su uso temporalmente. Back Español 한국어 English (US) Tiếng Việt Bahasa Indonesia ภาษาไทย 中文(简体) 日本語 Português (Brasil) Français (France) Deutsch Registrarte Iniciar sesión Messenger Facebook Lite Video Meta Pay Tienda de Meta Meta Quest Ray-Ban Meta Meta AI Más contenido de Meta AI Instagram Threads Centro de información de votación Política de privacidad Centro de privacidad Información Crear anuncio Crear página Desarrolladores Empleo Cookies Opciones de anuncios Condiciones Ayuda Importación de contactos y no usuarios Configuración Registro de actividad Meta © 2026 | 2026-01-13T09:30:34 |
https://www.mongodb.com/community/forums/t/mongodb-weeklyupdate-64-april-8-2022-time-series-data-network-compression-and-exploring-nfts-and-crypto/156888 | MongoDB $weeklyUpdate #64 (April 8, 2022): Time Series Data, Network Compression, and Exploring NFTs and Crypto - $weeklyUpdate - MongoDB Community Hub NEW: MongoDB Community Hub is Now in Public Preview! × MongoDB Community Hub MongoDB $weeklyUpdate #64 (April 8, 2022): Time Series Data, Network Compression, and Exploring NFTs and Crypto About the Community $weeklyUpdate weekly-update , mongoose-odm , time-series Megan_Grant (Megan Grant) April 8, 2022, 2:53pm 1 Hi everyone! Welcome to MongoDB $weeklyUpdate! Here, you’ll find the latest developer tutorials, upcoming official MongoDB events, and get a heads up on our latest Twitch streams and podcast, curated by Megan Grant . Enjoy! Freshest Tutorials on DevHub Want to find the latest MongoDB tutorials and articles created for developers, by developers? Look no further than our DevHub ! MongoDB’s New Time Series Collections Michael Gargiulo Mark Smith Learn all about MongoDB’s new time series collection type! Preparing Time Series Data for Analysis Tools with $densify and $fill John Page Learn through examples and graphs how the aggregation stages $densify and $fill allow you to fill gaps in time series data and convert irregular to regular time spacing. MongoDB & Mongoose: Compatibility and Comparison @ado @Stanimira_Vlaeva In this article, we’ll explore the Mongoose library for MongoDB. Mongoose is an Object Data Modeling (ODM) library for MongoDB distributed as an npm package. MongoDB Network Compression: A Win-Win Brian Leonard This article provides two tuneable Python scripts, read-from-mongo.py and write-to-mongo.py, that you can use to see the impact of network compression yourself. Official MongoDB Events & Community Events Attend an official MongoDB event near you! Chat with MongoDB experts, learn something new, meet other developers, and win some swag! Apr 13 (Stockholm) - Stockholm MUG: Kickoff & Explore Energy Prices with MongoDB Apr 20 (Virtual) - Google Startup Summit Apr 20-21 (San Francisco) - MongoDB at AWS Summit San Francisco Apr 25-26 (London) - MongoDB @ Kafka Summit London Apr 27-28 (London) - MongoDB at AWS Summit London MongoDB World 2022: MongoDB Diversity Scholarships for Underrepresented Groups in Tech MongoDB on Twitch & YouTube We stream tech tutorials, live coding, and talk to members of our community via Twitch and YouTube . Sometimes, we even stream twice a week! Be sure to follow us on Twitch and subscribe to our YouTube channel to be notified of every stream! Latest Stream More Video Goodness Follow us on Twitch and subscribe to our YouTube channel so you never miss a stream! Last Word on the MongoDB Podcast Latest Episode Spotify Ep. 105 The MongoDB World 2022 Hackathon Listen to this episode from The MongoDB Podcast on Spotify. MongoDB World Hackathon '22 Build your way to MongoDB World this year by competing in our hackathon. This year’s theme is “Data as news - A hackathon for information overload”. On this... Catch up on past episodes : Ep. 104 - Scaling Iron Mountain with MongoDB Ep. 103 - Exploring NFTs and Crypto with Professor Cardano Ep. 102 - Changing the Game with MongoDB (Not listening on Spotify? We got you! We’re most likely on your favorite podcast network, including Apple Podcasts , PlayerFM , Podtail , and Listen Notes ) Did you know that you get these $weeklyUpdates before anyone else? It’s a small way of saying thank you for being a part of this community. If you know others who want to get first dibs on the latest MongoDB content and MongoDB announcements as well as interact with the MongoDB community and help others solve MongoDB related issues, be sure to share a tweet and get others to sign up today! 1 Like Home Categories Guidelines Terms of Service Privacy Policy Powered by Discourse , best viewed with JavaScript enabled | 2026-01-13T09:30:34 |
http://docs.buildbot.net/current/manual/installation/misc.html#troubleshooting | 2.2.6. Next Steps — Buildbot 4.3.0 documentation Buildbot 1. Buildbot Tutorial 2. Buildbot Manual 2.1. Introduction 2.2. Installation 2.2.1. Buildbot Components 2.2.2. Requirements 2.2.3. Installing the code 2.2.4. Buildmaster Setup 2.2.5. Worker Setup 2.2.6. Next Steps 2.2.6.1. Launching the daemons 2.2.6.2. Launching worker as Windows service 2.2.6.3. Logfiles 2.2.6.4. Shutdown 2.3. Concepts 2.4. Secret Management 2.5. Configuration 2.6. Customization 2.7. Command-line Tool 2.8. Resources 2.9. Optimization 2.10. Plugin Infrastructure in Buildbot 2.11. Deployment 2.12. Upgrading 3. Buildbot Development 4. Release Notes 5. Older Release Notes 6. API Indices Buildbot 2. Buildbot Manual 2.2. Installation 2.2.6. Next Steps View page source 2.2.6. Next Steps 2.2.6.1. Launching the daemons Both the buildmaster and the worker run as daemon programs. To launch them, pass the working directory to the buildbot and buildbot-worker commands, as appropriate: # start a master buildbot start [ BASEDIR ] # start a worker buildbot-worker start [ WORKER_BASEDIR ] The BASEDIR is optional and can be omitted if the current directory contains the buildbot configuration (the buildbot.tac file). buildbot start This command will start the daemon and then return, so normally it will not produce any output. To verify that the programs are indeed running, look for a pair of files named twistd.log and twistd.pid that should be created in the working directory. twistd.pid contains the process ID of the newly-spawned daemon. When the worker connects to the buildmaster, new directories will start appearing in its base directory. The buildmaster tells the worker to create a directory for each Builder which will be using that worker. All build operations are performed within these directories: CVS checkouts, compiles, and tests. Once you get everything running, you will want to arrange for the buildbot daemons to be started at boot time. One way is to use cron , by putting them in a @reboot crontab entry [ 1 ] @reboot buildbot start [ BASEDIR ] When you run crontab to set this up, remember to do it as the buildmaster or worker account! If you add this to your crontab when running as your regular account (or worse yet, root), then the daemon will run as the wrong user, quite possibly as one with more authority than you intended to provide. It is important to remember that the environment provided to cron jobs and init scripts can be quite different than your normal runtime. There may be fewer environment variables specified, and the PATH may be shorter than usual. It is a good idea to test out this method of launching the worker by using a cron job with a time in the near future, with the same command, and then check twistd.log to make sure the worker actually started correctly. Common problems here are for /usr/local or ~/bin to not be on your PATH , or for PYTHONPATH to not be set correctly. Sometimes HOME is messed up too. If using systemd to launch buildbot-worker , it may be a good idea to specify a fixed PATH using the Environment directive (see systemd unit file example ). Some distributions may include conveniences to make starting buildbot at boot time easy. For instance, with the default buildbot package in Debian-based distributions, you may only need to modify /etc/default/buildbot (see also /etc/init.d/buildbot , which reads the configuration in /etc/default/buildbot ). Buildbot also comes with its own init scripts that provide support for controlling multi-worker and multi-master setups (mostly because they are based on the init script from the Debian package). With a little modification, these scripts can be used on both Debian and RHEL-based distributions. Thus, they may prove helpful to package maintainers who are working on buildbot (or to those who haven’t yet split buildbot into master and worker packages). # install as /etc/default/buildbot-worker # or /etc/sysconfig/buildbot-worker worker/contrib/init-scripts/buildbot-worker.default # install as /etc/default/buildmaster # or /etc/sysconfig/buildmaster master/contrib/init-scripts/buildmaster.default # install as /etc/init.d/buildbot-worker worker/contrib/init-scripts/buildbot-worker.init.sh # install as /etc/init.d/buildmaster master/contrib/init-scripts/buildmaster.init.sh # ... and tell sysvinit about them chkconfig buildmaster reset # ... or update-rc.d buildmaster defaults 2.2.6.2. Launching worker as Windows service Security consideration Setting up the buildbot worker as a Windows service requires Windows administrator rights. It is important to distinguish installation stage from service execution. It is strongly recommended run Buildbot worker with lowest required access rights. It is recommended run a service under machine local non-privileged account. If you decide run Buildbot worker under domain account it is recommended to create dedicated strongly limited user account that will run Buildbot worker service. Windows service setup In this description, we assume that the buildbot worker account is the local domain account worker . In case worker should run under domain user account please replace .\worker with <domain>\worker . Please replace <worker.passwd> with given user password. Please replace <worker.basedir> with the full/absolute directory specification to the created worker (what is called BASEDIR in Creating a worker ). buildbot_worker_windows_service --user .\worker --password < worker.passwd > --startup auto install powershell -command "& {&'New-Item' -path Registry::HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\BuildBot\Parameters}" powershell -command "& {&'set-ItemProperty' -path Registry::HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\BuildBot\Parameters -Name directories -Value '<worker.basedir>'}" The first command automatically adds user rights to run Buildbot as service. Modify environment variables This step is optional and may depend on your needs. At least we have found useful to have dedicated temp folder worker steps. It is much easier discover what temporary files your builds leaks/misbehaves. As Administrator run regedit Open the key Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Buildbot . Create a new value of type REG_MULTI_SZ called Environment . Add entries like TMP = c : \ bbw \ tmp TEMP = c : \ bbw \ tmp Check if Buildbot can start correctly configured as Windows service As admin user run the command net start buildbot . In case everything goes well, you should see following output The BuildBot service is starting . The BuildBot service was started successfully . Troubleshooting If anything goes wrong check Twisted log on C:\bbw\worker\twistd.log Windows system event log ( eventvwr.msc in command line, Show-EventLog in PowerShell). 2.2.6.3. Logfiles While a buildbot daemon runs, it emits text to a logfile, named twistd.log . A command like tail -f twistd.log is useful to watch the command output as it runs. The buildmaster will announce any errors with its configuration file in the logfile, so it is a good idea to look at the log at startup time to check for any problems. Most buildmaster activities will cause lines to be added to the log. 2.2.6.4. Shutdown To stop a buildmaster or worker manually, use: buildbot stop [ BASEDIR ] # or buildbot-worker stop [ WORKER_BASEDIR ] This simply looks for the twistd.pid file and kills whatever process is identified within. At system shutdown, all processes are sent a SIGKILL . The buildmaster and worker will respond to this by shutting down normally. The buildmaster will respond to a SIGHUP by re-reading its config file. Of course, this only works on Unix-like systems with signal support and not on Windows. The following shortcut is available: buildbot reconfig [ BASEDIR ] When you update the Buildbot code to a new release, you will need to restart the buildmaster and/or worker before they can take advantage of the new code. You can do a buildbot stop BASEDIR and buildbot start BASEDIR in succession, or you can use the restart shortcut, which does both steps for you: buildbot restart [ BASEDIR ] Workers can similarly be restarted with: buildbot-worker restart [ BASEDIR ] There are certain configuration changes that are not handled cleanly by buildbot reconfig . If this occurs, buildbot restart is a more robust way to fully switch over to the new configuration. buildbot restart may also be used to start a stopped Buildbot instance. This behavior is useful when writing scripts that stop, start, and restart Buildbot. A worker may also be gracefully shutdown from the web UI. This is useful to shutdown a worker without interrupting any current builds. The buildmaster will wait until the worker has finished all its current builds, and will then tell the worker to shutdown. [ 1 ] This @reboot syntax is understood by Vixie cron, which is the flavor usually provided with Linux systems. Other unices may have a cron that doesn’t understand @reboot Previous Next © Copyright Buildbot Team Members. Built with Sphinx using a theme provided by Read the Docs . | 2026-01-13T09:30:34 |
https://repo.maven.apache.org/maven2/ | Central Repository: ../ HTTPClient/ - - abbot/ - - academy/ - - acegisecurity/ - - activation/ - - activecluster/ - - activeio/ - - activemq/ - - activemq-jaxb/ - - activesoap/ - - activespace/ - - adarwin/ - - ae/ - - aelfred/ - - aero/ - - africa/ - - ag/ - - agency/ - - ai/ - - aislib/ - - al/ - - altrmi/ - - am/ - - andromda/ - - annogen/ - - ant/ - - ant-contrib/ - - ant-doxygen/ - - ant4eclipse/ - - antlr/ - - anttex/ - - aopalliance/ - - apache-jaxme/ - - app/ - - aptconvert/ - - ar/ - - args4j/ - - art/ - - as/ - - ashkay/ - - ashkelon/ - - asia/ - - asm/ - - aspectj/ - - aspectwerkz/ - - at/ - - au/ - - avalon/ - - avalon-activation/ - - avalon-apps/ - - avalon-composition/ - - avalon-cornerstone/ - - avalon-extension/ - - avalon-framework/ - - avalon-http/ - - avalon-logging/ - - avalon-logkit/ - - avalon-meta/ - - avalon-phoenix/ - - avalon-repository/ - - avalon-util/ - - aws/ - - ax/ - - axion/ - - axis/ - - axis2/ - - azote/ - - ba/ - - backport-util-concurrent/ - - backport175/ - - band/ - - barsuift/ - - batik/ - - bayern/ - - bcel/ - - bd/ - - be/ - - beehive/ - - beer/ - - berkano/ - - berkeleydb/ - - berlin/ - - best/ - - bet/ - - bg/ - - bi/ - - bike/ - - binky/ - - bio/ - - biz/ - - black/ - - blissed/ - - blog/ - - blue/ - - boo/ - - bot/ - - bouncycastle/ - - box/ - - boxstuff/ - - br/ - - bsf/ - - bsh/ - - build/ - - builders/ - - burlap/ - - buzz/ - - by/ - - bz/ - - c10n/ - - c3p0/ - - ca/ - - cactus/ - - cafe/ - - cam/ - - camp/ - - capital/ - - care/ - - cargo/ - - cas/ - - casa/ - - cash/ - - castor/ - - cat/ - - cc/ - - cd/ - - center/ - - cewolf/ - - cf/ - - cglib/ - - ch/ - - charlotte/ - - chat/ - - checkstyle/ - - church/ - - ci/ - - city/ - - cl/ - - classworlds/ - - click/ - - clickstream/ - - clinic/ - - clirr/ - - cloud/ - - clover/ - - club/ - - cm/ - - cmsdeploy/ - - cn/ - - co/ - - cobertura/ - - coconut/ - - cocoon/ - - code/ - - code316/ - - codehaus/ - - codes/ - - coffee/ - - colt/ - - com/ - - commons-attributes/ - - commons-beanutils/ - - commons-betwixt/ - - commons-chain/ - - commons-cli/ - - commons-codec/ - - commons-collections/ - - commons-compress/ - - commons-configuration/ - - commons-daemon/ - - commons-dbcp/ - - commons-dbutils/ - - commons-digester/ - - commons-discovery/ - - commons-el/ - - commons-email/ - - commons-fileupload/ - - commons-grafolia/ - - commons-grant/ - - commons-graph/ - - commons-http/ - - commons-httpclient/ - - commons-i18n/ - - commons-io/ - - commons-jdbc2pool/ - - commons-jelly/ - - commons-jexl/ - - commons-jux/ - - commons-jxpath/ - - commons-lang/ - - commons-latka/ - - commons-launcher/ - - commons-logging/ - - commons-math/ - - commons-messenger/ - - commons-modeler/ - - commons-naming/ - - commons-net/ - - commons-pool/ - - commons-primitives/ - - commons-resources/ - - commons-scxml/ - - commons-services/ - - commons-sql/ - - commons-test/ - - commons-threadpool/ - - commons-transaction/ - - commons-util/ - - commons-validator/ - - commons-vfs/ - - commons-xo/ - - community/ - - company/ - - computer/ - - concurrent/ - - consulting/ - - continuum/ - - controlhaus/ - - cool/ - - coop/ - - cornerstone-connection/ - - cornerstone-datasources/ - - cornerstone-scheduler/ - - cornerstone-sockets/ - - cornerstone-store/ - - cornerstone-threads/ - - cos/ - - crimson/ - - cryptix/ - - cssparser/ - - cv/ - - cx/ - - cz/ - - d-haven-event/ - - d-haven-eventbus/ - - d-haven-mpool/ - - dalma/ - - dalms/ - - damagecontrol/ - - dataforge/ - - datasift/ - - date/ - - day/ - - dbunit/ - - de/ - - decorutils/ - - default/ - - dentaku/ - - dependency-maven-plugin/ - - design/ - - dev/ - - digital/ - - directory/ - - directory-asn1/ - - directory-authx/ - - directory-clients/ - - directory-naming/ - - directory-network/ - - directory-protocols/ - - directory-shared/ - - displaytag/ - - ditchnet/ - - dk/ - - dna/ - - dnsjava/ - - docbook/ - - doccheck/ - - dom4j/ - - domify/ - - doxia/ - - drone/ - - drools/ - - drools-examples/ - - dsh-vocabulary/ - - dtdparser/ - - dumbster/ - - dwr/ - - dynaop/ - - earth/ - - easyconf/ - - easymock/ - - ec/ - - echo/ - - echo3/ - - echo3extras/ - - eclipse/ - - eco/ - - ecs/ - - edenlib/ - - edtftp/ - - edu/ - - education/ - - ee/ - - ehcache/ - - ejb/ - - el-impl/ - - emberio/ - - emma/ - - energy/ - - engineer/ - - engineering/ - - enterprises/ - - ervacon/ - - es/ - - esper/ - - eu/ - - eus/ - - events/ - - excalibur/ - - excalibur-altrmi/ - - excalibur-cli/ - - excalibur-collections/ - - excalibur-component/ - - excalibur-component-examples/ - - excalibur-component-tests/ - - excalibur-concurrent/ - - excalibur-configuration/ - - excalibur-containerkit/ - - excalibur-datasource/ - - excalibur-event/ - - excalibur-extension/ - - excalibur-fortress/ - - excalibur-i18n/ - - excalibur-instrument/ - - excalibur-instrument-manager/ - - excalibur-instrument-manager-interfaces/ - - excalibur-io/ - - excalibur-lifecycle/ - - excalibur-logger/ - - excalibur-monitor/ - - excalibur-mpool/ - - excalibur-naming/ - - excalibur-pool/ - - excalibur-sourceresolve/ - - excalibur-store/ - - excalibur-thread/ - - excalibur-util/ - - excalibur-xmlutil/ - - exchange/ - - exist/ - - exml/ - - exo/ - - exolabcore/ - - expert/ - - express/ - - exteca/ - - external/ - - family/ - - fan/ - - fans/ - - farm/ - - fastutil/ - - fesi/ - - fi/ - - film/ - - finance/ - - financial/ - - findbugs/ - - fish/ - - fit/ - - flox/ - - flux/ - - fm/ - - fo/ - - foo/ - - fop/ - - forehead/ - - formproc/ - - foundation/ - - foxtrot/ - - fr/ - - freebxml/ - - freemarker/ - - frl/ - - fulcrum/ - - fun/ - - fyi/ - - ga/ - - gabriel/ - - games/ - - garden/ - - gay/ - - gbean/ - - gdn/ - - generama/ - - genjar/ - - genjava/ - - gent/ - - geronimo/ - - geronimo-spec/ - - gg/ - - github/ - - glass/ - - glassfish/ - - global/ - - gmbh/ - - gnu/ - - gnu-regexp/ - - gov/ - - gq/ - - gr/ - - graphics/ - - graphlayout/ - - green/ - - grizzly/ - - grizzly-cachetest/ - - groovy/ - - groovy-xmlrpc/ - - group/ - - gs/ - - gsbase/ - - guru/ - - health/ - - help/ - - hessian/ - - hibernate/ - - hivemind/ - - hk/ - - hm/ - - host/ - - house/ - - howl/ - - hr/ - - hsqldb/ - - htmlunit/ - - httpcomponents-httpcore/ - - httpunit/ - - hu/ - - hudson/ - - ical4j/ - - icu/ - - icu4j/ - - id/ - - idb/ - - ie/ - - iirekm/ - - il/ - - im/ - - immo/ - - in/ - - inc/ - - industries/ - - info/ - - informa/ - - ink/ - - innig/ - - int/ - - io/ - - iq/ - - ir/ - - is/ - - isorelax/ - - it/ - - itext/ - - ivory/ - - izpack/ - - jaas/ - - jackcess/ - - jackson/ - - jacl/ - - jaf/ - - jaimbot/ - - jakarta/ - - jakarta-regexp/ - - jalopy/ - - james/ - - janino/ - - jardiff/ - - jarjar/ - - jarsync/ - - jasper-jsr199/ - - jasperreports/ - - java2html/ - - java3d/ - - java_cup/ - - javacc/ - - javaconfig/ - - javadb/ - - javadoc/ - - javaee/ - - javagroups/ - - javainetlocator/ - - javamail/ - - javancss/ - - javanettasks/ - - javassist/ - - javatar/ - - javax/ - - javazoom/ - - javolution/ - - jawin/ - - jaxb/ - - jaxen/ - - jaxme/ - - jaxr-ra/ - - jblanket/ - - jboss/ - - jca/ - - jcache/ - - jcharts/ - - jcifs/ - - jcom/ - - jcommon/ - - jcoverage/ - - jcs/ - - jcs-javagroups/ - - jcvsii/ - - jdbc/ - - jdbm/ - - jdepend/ - - jdiff/ - - jdo/ - - jdom/ - - jdring/ - - jdsl/ - - je/ - - jen/ - - jencks/ - - jep/ - - jepi/ - - jersey/ - - jetty/ - - jexcelapi/ - - jface/ - - jfree/ - - jfreechart/ - - jgen/ - - jgoodies/ - - jgraph/ - - jgrapht/ - - jgroups/ - - jhunlang/ - - jini/ - - jintention/ - - jisp/ - - jivesoftware/ - - jlibdiff/ - - jline/ - - jmagick/ - - jmaki/ - - jmdns/ - - jmimemagic/ - - jmml/ - - jmock/ - - jms/ - - jmscts/ - - jmsn/ - - joda-time/ - - john-test/ - - jotm/ - - jp/ - - jparsec/ - - jpl/ - - jpox/ - - jpox-dbcp/ - - jpox-enhancer/ - - jpox-java5/ - - jrexx/ - - jrms/ - - jrobin/ - - jruby/ - - jsch/ - - jsf-extensions/ - - jspapi/ - - jsptags/ - - jstl/ - - jstyle/ - - jta/ - - jtds/ - - jtidy/ - - juddi/ - - jug/ - - jung/ - - junit/ - - junit-addons/ - - junit-doclet/ - - junitperf/ - - juno/ - - jwebunit/ - - jxta/ - - jython/ - - kawa/ - - ke/ - - kg/ - - kh/ - - kim/ - - kiwi/ - - koeln/ - - kohsuke/ - - kr/ - - kxml/ - - kxml2/ - - ky/ - - kz/ - - la/ - - land/ - - lat/ - - lc/ - - ldapd-common/ - - ldapsdk/ - - lgbt/ - - li/ - - libgdx-oboe/ - - life/ - - lingo/ - - link/ - - live/ - - lk/ - - llc/ - - locc/ - - log4j/ - - log4unit/ - - logkit/ - - lol/ - - loom/ - - love/ - - lpg/ - - lt/ - - ltd/ - - lu/ - - lucene/ - - lv/ - - ly/ - - ma/ - - magicGball/ - - maps/ - - market/ - - marmalade/ - - math/ - - maven/ - - maven-integration-test-helper/ - - maven-javanet-plugin/ - - maven-new/ - - maven-plugins/ - - maven-proxy/ - - maven-taglib/ - - maven-torque-plugin/ - - maven-validator/ - - maven-xdoclet2-plugin/ - - maxq/ - - mckoi/ - - md/ - - me/ - - media/ - - merlin/ - - merlin-developer/ - - merlin-tutorial/ - - messenger/ - - metaclass/ - - mevenide/ - - microcontainer/ - - middlegen/ - - mil/ - - milyn/ - - mk/ - - ml/ - - mm/ - - mm-mysql/ - - mn/ - - mobi/ - - mockcreator/ - - mockit/ - - mockmaker/ - - mockobjects/ - - mockrunner/ - - modello/ - - moe/ - - monetdb/ - - money/ - - monster/ - - mp/ - - mrj/ - - ms/ - - mstor/ - - msv/ - - mt/ - - mu/ - - mule/ - - muse/ - - mx/ - - mx4j/ - - my/ - - myfaces/ - - mysql/ - - mz/ - - name/ - - nanning/ - - nanocontainer/ - - nekohtml/ - - neo/ - - net/ - - netbeans/ - - network/ - - new/ - - nf/ - - ng/ - - ninja/ - - nl/ - - no/ - - norbert/ - - np/ - - nsuml/ - - nu/ - - nz/ - - oauth/ - - odmg/ - - ognl/ - - ojb/ - - ojdbc/ - - old/ - - one/ - - oness/ - - onl/ - - online/ - - open/ - - open-esb/ - - opencypher/ - - openejb/ - - openim/ - - openjms/ - - opennms/ - - opensymphony/ - - oracle/ - - org/ - - org.elasticsearch/ - - org.elasticsearch.client/ - - org.elasticsearch.distribution.integ-test-zip/ - - org.elasticsearch.distribution.zip/ - - org.elasticsearch.gradle/ - - org.elasticsearch.plugin/ - - org.elasticsearch.test/ - - oro/ - - oscube/ - - ovh/ - - p2psockets/ - - p6spy/ - - page/ - - party/ - - pathwaycommons/ - - patterntesting/ - - payload/ - - pcj/ - - pdfbox/ - - pe/ - - penguin/ - - pet/ - - petridish/ - - ph/ - - piccolo/ - - picocontainer/ - - picounit/ - - pink/ - - pircbot/ - - pitt/ - - pk/ - - pl/ - - plexus/ - - plj/ - - plugin/ - - plus/ - - pluto-container/ - - pm/ - - pmd/ - - pnuts/ - - poi/ - - poolman/ - - portlet-api/ - - postgresql/ - - prevayler/ - - pro/ - - proctor/ - - profiler/ - - proxool/ - - proxytoys/ - - pt/ - - pub/ - - pubscribe/ - - pull-parser/ - - pw/ - - qa/ - - qdox/ - - qfork/ - - quartz/ - - quest/ - - quilt/ - - radeox/ - - re/ - - readline/ - - red/ - - redhill/ - - redis/ - - redmine/ - - regexp/ - - relaxngDatatype/ - - ren/ - - report/ - - reportrunner/ - - rest/ - - rhino/ - - rip/ - - ro/ - - robo-guice/ - - roboguice/ - - rocks/ - - rodeo/ - - roller/ - - rome/ - - rs/ - - rss4j/ - - rsslibj/ - - ru/ - - rubygems/ - - run/ - - sa/ - - sablecc/ - - sale/ - - sax/ - - saxon/ - - saxpath/ - - sc/ - - school/ - - science/ - - scot/ - - scout/ - - scraping-engine/ - - se/ - - security/ - - securityfilter/ - - servicemix/ - - servicemix-ws/ - - services/ - - servletapi/ - - servlets/ - - setpoint/ - - sfx4j/ - - sg/ - - sh/ - - shellix/ - - shocks/ - - shop/ - - show/ - - si/ - - sillyexceptions/ - - simple-jms/ - - simple-jndi/ - - site/ - - sk/ - - skaringa/ - - ski/ - - skinlf/ - - slide/ - - smartrics/ - - sn/ - - so/ - - soap/ - - social/ - - software/ - - soimp/ - - solar/ - - solarisrealm/ - - solutions/ - - space/ - - speexx/ - - spice/ - - spring/ - - springframework/ - - springmodules/ - - sqlline/ - - srl/ - - sshtools/ - - sslext/ - - st/ - - stapler/ - - statcvs/ - - stax/ - - stax-utils/ - - store/ - - stratum/ - - stream/ - - struts/ - - struts-menu/ - - strutstestcase/ - - studio/ - - stxx/ - - su/ - - subpersistence/ - - subshell/ - - suiterunner/ - - surefire/ - - swarmcache/ - - swiss/ - - swt/ - - systems/ - - sysunit/ - - tablelayout/ - - tagalog/ - - tagishauth/ - - taglibrarydoc/ - - taglibs/ - - tagsoup/ - - tambora/ - - tanukisoft/ - - tapestry/ - - tclib/ - - team/ - - tec/ - - tech/ - - technology/ - - tel/ - - textarea/ - - tf/ - - th/ - - thaiopensource/ - - tiffrenderer/ - - tjdo/ - - tk/ - - tl/ - - tmporb/ - - to/ - - today/ - - tokyo/ - - tomcat/ - - tomcat-util/ - - tonic/ - - tools/ - - top/ - - toplink/ - - torque/ - - torque-gen/ - - touchstone/ - - toys/ - - tr/ - - trade/ - - traer/ - - trail-taglib/ - - tranql/ - - travel/ - - trove/ - - trust/ - - turbine/ - - tv/ - - tw/ - - tyrex/ - - tz/ - - ua/ - - uaihebert/ - - ubique/ - - ug/ - - uispec4j/ - - uk/ - - uno/ - - urbanophile/ - - urlrewrite/ - - us/ - - uy/ - - uz/ - - vc/ - - vdoclet/ - - velocity/ - - velocity-anakia/ - - velocity-dvsl/ - - velocity-tools/ - - ventures/ - - video/ - - village/ - - vin/ - - vip/ - - vision/ - - vn/ - - vu/ - - wadi/ - - wang/ - - webmacro/ - - website/ - - webtest/ - - weixinkeji/ - - werken-xpath/ - - werkflow/ - - werkz/ - - westhawk/ - - wf/ - - which/ - - wicket/ - - wiki/ - - win/ - - woodstox/ - - work/ - - works/ - - world/ - - wrapper/ - - ws/ - - ws-commons/ - - ws-commons-java5/ - - ws-commons-util/ - - ws-scout/ - - wsdl4j/ - - wsrf/ - - wss4j/ - - wstx/ - - wtf/ - - wurfl/ - - wutka/ - - xajile/ - - xalan/ - - xbean/ - - xdoclet/ - - xdoclet-plugins/ - - xerces/ - - xercesjarv/ - - xfire/ - - xfire-root/ - - xin/ - - xjavadoc/ - - xml-apis/ - - xml-resolver/ - - xml-security/ - - xmlbeans/ - - xmldb/ - - xmlenc/ - - xmlmind/ - - xmlpull/ - - xmlrpc/ - - xmlrpc-helma/ - - xmlunit/ - - xmlwise/ - - xmlwriter/ - - xom/ - - xpp3/ - - xsddoc/ - - xsdlib/ - - xstream/ - - xtc/ - - xtiff-jai/ - - xxl/ - - xyz/ - - yan/ - - ymsg/ - - yom/ - - za/ - - zm/ - - zone/ - - zw/ - - archetype-catalog.xml 2026-01-11 03:21 17494861 archetype-catalog.xml.md5 2026-01-11 03:21 32 archetype-catalog.xml.sha1 2026-01-11 03:21 40 last_updated.txt 2026-01-13 09:27 29 robots.txt 2023-10-03 17:44 26 | 2026-01-13T09:30:34 |
https://id-id.facebook.com/login/?next=https%3A%2F%2Fl.facebook.com%2Fl.php%3Fu%3Dhttps%253A%252F%252Fwww.instagram.com%252F%26amp%253Bh%3DAT0oK5bRFTTybnDOhYhIZLq01lQic0NLTeIbHIWCatEHpQ1l_XvBDhFFg93NTxyaIWLyhjuKO75pi9dqx6GinsMsCUF3-jXwiN5uEdfkpm7k0xf-caL8YQT8KCcQ_cBSLI1zBjdYsjE75jVT | Facebook Facebook Email atau telepon Kata Sandi Lupa akun? Buat Akun Baru Anda Diblokir Sementara Anda Diblokir Sementara Sepertinya Anda menyalahgunakan fitur ini dengan menggunakannya terlalu cepat. Anda dilarang menggunakan fitur ini untuk sementara. Back Bahasa Indonesia 한국어 English (US) Tiếng Việt ภาษาไทย Español 中文(简体) 日本語 Português (Brasil) Français (France) Deutsch Daftar Masuk Messenger Facebook Lite Video Meta Pay Meta Store Meta Quest Ray-Ban Meta Meta AI Konten Meta AI lainnya Instagram Threads Pusat Informasi Pemilu Kebijakan Privasi Pusat Privasi Tentang Buat Iklan Buat Halaman Developer Karier Cookie Pilihan Iklan Ketentuan Bantuan Pengunggahan Kontak & Non-Pengguna Pengaturan Log aktivitas Meta © 2026 | 2026-01-13T09:30:34 |
https://llvmweekly.org/issue/555 | LLVM Weekly - #555, August 19th 2024 LLVM Weekly - #555, August 19th 2024 Welcome to the five hundred and fifty-fifth issue of LLVM Weekly, a weekly newsletter (published every Monday) covering developments in LLVM, Clang, and related projects. LLVM Weekly is brought to you by Alex Bradbury . Subscribe to future issues at http://llvmweekly.org and pass it on to anyone else you think may be interested. Please send any tips or feedback to asb@asbradbury.org , @llvmweekly or @asbradbury on Twitter, or @llvmweekly@fosstodon.org or @asb@fosstodon.org . News and articles from around the web and events According to the LLVM calendar in the coming week there will be the following: Office hours with the following hosts: Phoebe Wang, Johannes Doerfert. Online sync-ups on the following topics: Flang, pointer authentication, SPIR-V, vectoriser improvements, security group, new contributors, LLVM/Offload, Clang C/C++ language working group, loop optimisation, floating point, OpenMP for Flang, MLIR. For more details see the LLVM calendar , getting involved documentation on online sync ups and office hours . On the forums Aaron Ballman started an RFC discussion on changes to the community code ownership policy , suggesting changes to the notion of “code ownership” with the aim of realigning it better with community needs and expectations. Saleem Abdulrasool started a discussion about dropping support for running LLVM on Windows Vista, 7, and 8 . Issue #69 of the MLIR Newsletter is out . Justin Stitt proposes adding an operator to invert matches in LLVM’s GlobalPattern implementation . Louis Dionne explained why a large number of GitHub issues have been created for libc++ recently . Vlad Serebrennikov noted that pre-commit CI is very slow for a subset of PRs (typically old ones) . Min-Yih Hsu updated the RFC thread on llvm.experimental.get.vector.length . Michael Clark shared an idea for adding the ability to return alloca memory from a function . “ahatanak” proposed adding a __ptrauth qualifier . LLVM commits A git “linkify” script was added. If you do git config core.pager 'llvm/utils/git/linkify | pager' then the script will make text that appears to be a pull request, issue reference, or commit hash into a clickable link. 564efe2 . llvm.minimumnum and llvm.maximumnum intrinsics were added, with semantics matching the equivalent minimumNumber and maximumNumber IEEE 754-2019 operations. fb9e685 . SPIR-V virtual register processing was reworked. f9c9806 . The SLP vectorizer learned to keep original scalars in more cases. b10ecfa . A DXILMetadataAnalysis pass was added to collect DXIL module metadata information in a structure. 03e6675 . Scheduling models were added for the Syntacore SCR4 and SCR5 RISC-V cores. 5ab99bf . A DXILResourceAnalysis pass was started. 28d577e , 372ddcd . Additional guidance was added for using Graphite for stacked pull requests. 6dcfc84 . A SelectionDAG::getSignedConstant helper was introduced. 7afb51e . The -lsr-term-fold transformation was split into its own pass. 27a62ec . Clang commits A new -foffload-via-llvm flag was introduced allowing CUDA kernels to be lowered to the new LLVM/Offload API. 80525df . __builtin_is_implicit_lifetime was implemented. d213981 . Other project commits The NumericalStabilitySanitizer now uses its own allocator. 652707a . A script was added for synchronising the CSV files used to track standards conformance with GitHub issues. f117f0a . LLDB now uses realpath to increase its changes of resolving file/line breakpoints. 47721d4 . Subscribe at LLVMWeekly.org . | 2026-01-13T09:30:34 |
http://docs.buildbot.net/current/manual/cmdline.html#developer-tools | 2.7. Command-line Tool — Buildbot 4.3.0 documentation Buildbot 1. Buildbot Tutorial 2. Buildbot Manual 2.1. Introduction 2.2. Installation 2.3. Concepts 2.4. Secret Management 2.5. Configuration 2.6. Customization 2.7. Command-line Tool 2.7.1. buildbot 2.7.1.1. Administrator Tools 2.7.1.2. Developer Tools 2.7.1.3. Other Tools 2.7.1.4. .buildbot config directory 2.7.2. buildbot-worker 2.7.2.1. create-worker 2.7.2.2. start 2.7.2.3. restart 2.7.2.4. stop 2.8. Resources 2.9. Optimization 2.10. Plugin Infrastructure in Buildbot 2.11. Deployment 2.12. Upgrading 3. Buildbot Development 4. Release Notes 5. Older Release Notes 6. API Indices Buildbot 2. Buildbot Manual 2.7. Command-line Tool View page source 2.7. Command-line Tool This section describes command-line tools available after buildbot installation. The two main command-line tools are buildbot and buildbot-worker . The former handles a Buildbot master and the former handles a Buildbot worker. Every command-line tool has a list of global options and a set of commands which have their own options. One can run these tools in the following way: buildbot [global options] command [command options] buildbot-worker [global options] command [command options] The buildbot command is used on the master, while buildbot-worker is used on the worker. Global options are the same for both tools which perform the following actions: --help Print general help about available commands and global options and exit. All subsequent arguments are ignored. --verbose Set verbose output. --version Print current buildbot version and exit. All subsequent arguments are ignored. You can get help on any command by specifying --help as a command option: buildbot command --help You can also use manual pages for buildbot and buildbot-worker for quick reference on command-line options. The remainder of this section describes each buildbot command. See Command Line Index for a full list. 2.7.1. buildbot The buildbot command-line tool can be used to start or stop a buildmaster or buildbot, and to interact with a running buildmaster. Some of its subcommands are intended for buildmaster admins, while some are for developers who are editing the code that the buildbot is monitoring. 2.7.1.1. Administrator Tools The following buildbot sub-commands are intended for buildmaster administrators: create-master buildbot create-master -r {BASEDIR} This creates a new directory and populates it with files that allow it to be used as a buildmaster’s base directory. You will usually want to use the option -r option to create a relocatable buildbot.tac . This allows you to move the master directory without editing this file. upgrade-master buildbot upgrade-master {BASEDIR} This upgrades a previously created buildmaster’s base directory for a new version of buildbot master source code. This will copy the web server static files, and potentially upgrade the db. start buildbot start [--nodaemon] {BASEDIR} This starts a buildmaster which was already created in the given base directory. The daemon is launched in the background, with events logged to a file named twistd.log . The option –nodaemon option instructs Buildbot to skip daemonizing. The process will start in the foreground. It will only return to the command-line when it is stopped. Additionally, the user can set the environment variable START_TIMEOUT to specify the amount of time the script waits for the master to start until it declares the operation as failure. restart buildbot restart [--nodaemon] {BASEDIR} Restart the buildmaster. This is equivalent to stop followed by start The option –nodaemon option has the same meaning as for start . stop buildbot stop {BASEDIR} This terminates the daemon (either buildmaster or worker) running in the given directory. The --clean option shuts down the buildmaster cleanly. With --no-wait option buildbot stop command will send buildmaster shutdown signal and will immediately exit, not waiting for complete buildmaster shutdown. sighup buildbot sighup {BASEDIR} This sends a SIGHUP to the buildmaster running in the given directory, which causes it to re-read its master.cfg file. checkconfig buildbot checkconfig {BASEDIR|CONFIG_FILE} This checks if the buildmaster configuration is well-formed and contains no deprecated or invalid elements. If no arguments are used or the base directory is passed as the argument the config file specified in buildbot.tac is checked. If the argument is the path to a config file then it will be checked without using the buildbot.tac file. cleanupdb buildbot cleanupdb {BASEDIR|CONFIG_FILE} [-q] This command is frontend for various database maintenance jobs: optimiselogs: This optimization groups logs into bigger chunks to apply higher level of compression. This script runs for as long as it takes to finish the job including the time needed to check master.cfg file. copy-db buildbot copy-db {DESTINATION_URL} {BASEDIR} [-q] This command copies all buildbot data from source database configured in the buildbot configuration file to the destination database. The URL of the destination database is specified on the command line. The destination database may have different type from the source database. The destination database must be empty. The script will initialize it in the same way as if a new Buildbot installation was created. Source database must be already upgraded to the current Buildbot version by the buildbot upgrade-master command. 2.7.1.2. Developer Tools These tools are provided for use by the developers who are working on the code that the buildbot is monitoring. try This lets a developer to ask the question What would happen if I committed this patch right now? . It runs the unit test suite (across multiple build platforms) on the developer’s current code, allowing them to make sure they will not break the tree when they finally commit their changes. The buildbot try command is meant to be run from within a developer’s local tree, and starts by figuring out the base revision of that tree (what revision was current the last time the tree was updated), and a patch that can be applied to that revision of the tree to make it match the developer’s copy. This (revision, patch) pair is then sent to the buildmaster, which runs a build with that SourceStamp . If you want, the tool will emit status messages as the builds run, and will not terminate until the first failure has been detected (or the last success). There is an alternate form which accepts a pre-made patch file (typically the output of a command like svn diff ). This --diff form does not require a local tree to run from. See try –diff concerning the --diff command option. For this command to work, several pieces must be in place: the Try_Jobdir or : Try_Userpass , as well as some client-side configuration. Locating the master The try command needs to be told how to connect to the try scheduler, and must know which of the authentication approaches described above is in use by the buildmaster. You specify the approach by using --connect=ssh or --connect=pb (or try_connect = 'ssh' or try_connect = 'pb' in .buildbot/options ). For the PB approach, the command must be given a option –master argument (in the form HOST : PORT ) that points to TCP port that you picked in the Try_Userpass scheduler. It also takes a option –username and option –passwd pair of arguments that match one of the entries in the buildmaster’s userpass list. These arguments can also be provided as try_master , try_username , and try_password entries in the .buildbot/options file. For the SSH approach, the command must be given option –host and option –username , to get to the buildmaster host. It must also be given option –jobdir , which points to the inlet directory configured above. The jobdir can be relative to the user’s home directory, but most of the time you will use an explicit path like ~buildbot/project/trydir . These arguments can be provided in .buildbot/options as try_host , try_username , try_password , and try_jobdir . If you need to use something different from the default ssh command for connecting to the remote system, you can use –ssh command line option or try_ssh in the configuration file. The SSH approach also provides a option –buildbotbin argument to allow specification of the buildbot binary to run on the buildmaster. This is useful in the case where buildbot is installed in a virtualenv on the buildmaster host, or in other circumstances where the buildbot command is not on the path of the user given by option –username . The option –buildbotbin argument can be provided in .buildbot/options as try_buildbotbin The following command line arguments are deprecated, but retained for backward compatibility: --tryhost is replaced by option –host --trydir is replaced by option –jobdir --master is replaced by option –masterstatus Likewise, the following .buildbot/options file entries are deprecated, but retained for backward compatibility: try_dir is replaced by try_jobdir masterstatus is replaced by try_masterstatus Waiting for results If you provide the option –wait option (or try_wait = True in .buildbot/options ), the buildbot try command will wait until your changes have either been proven good or bad before exiting. Unless you use the option –quiet option (or try_quiet=True ), it will emit a progress message every 60 seconds until the builds have completed. The SSH connection method does not support waiting for results. Choosing the Builders A trial build is performed on multiple Builders at the same time, and the developer gets to choose which Builders are used (limited to a set selected by the buildmaster admin with the TryScheduler ’s builderNames= argument). The set you choose will depend upon what your goals are: if you are concerned about cross-platform compatibility, you should use multiple Builders, one from each platform of interest. You might use just one builder if that platform has libraries or other facilities that allow better test coverage than what you can accomplish on your own machine, or faster test runs. The set of Builders to use can be specified with multiple option –builder arguments on the command line. It can also be specified with a single try_builders option in .buildbot/options that uses a list of strings to specify all the Builder names: try_builders = [ "full-OSX" , "full-win32" , "full-linux" ] If you are using the PB approach, you can get the names of the builders that are configured for the try scheduler using the get-builder-names argument: buildbot try --get-builder-names --connect = pb --master = ... --username = ... --passwd = ... Specifying the VC system The try command also needs to know how to take the developer’s current tree and extract the (revision, patch) source-stamp pair. Each VC system uses a different process, so you start by telling the try command which VC system you are using, with an argument like option –vc=cvs or option –vc=git . This can also be provided as try_vc in .buildbot/options . The following names are recognized: bzr cvs darcs hg git mtn p4 svn Finding the top of the tree Some VC systems (notably CVS and SVN) track each directory more-or-less independently, which means the try command needs to move up to the top of the project tree before it will be able to construct a proper full-tree patch. To accomplish this, the try command will crawl up through the parent directories until it finds a marker file. The default name for this marker file is .buildbot-top , so when you are using CVS or SVN you should touch .buildbot-top from the top of your tree before running buildbot try . Alternatively, you can use a filename like ChangeLog or README , since many projects put one of these files in their top-most directory (and nowhere else). To set this filename, use --topfile=ChangeLog , or set it in the options file with try_topfile = 'ChangeLog' . You can also manually set the top of the tree with --topdir=~/trees/mytree , or try_topdir = '~/trees/mytree' . If you use try_topdir , in a .buildbot/options file, you will need a separate options file for each tree you use, so it may be more convenient to use the try_topfile approach instead. Other VC systems which work on full projects instead of individual directories (Darcs, Mercurial, Git, Monotone) do not require try to know the top directory, so the option –try-topfile and option –try-topdir arguments will be ignored. If the try command cannot find the top directory, it will abort with an error message. The following command line arguments are deprecated, but retained for backward compatibility: --try-topdir is replaced by option –topdir --try-topfile is replaced by option –topfile Determining the branch name Some VC systems record the branch information in a way that try can locate it. For the others, if you are using something other than the default branch, you will have to tell the buildbot which branch your tree is using. You can do this with either the option –branch argument, or a try_branch entry in the .buildbot/options file. Determining the revision and patch Each VC system has a separate approach for determining the tree’s base revision and computing a patch. CVS try pretends that the tree is up to date. It converts the current time into a option -D time specification, uses it as the base revision, and computes the diff between the upstream tree as of that point in time versus the current contents. This works, more or less, but requires that the local clock be in reasonably good sync with the repository. SVN try does a svn status -u to find the latest repository revision number (emitted on the last line in the Status against revision: NN message). It then performs an svn diff -r NN to find out how your tree differs from the repository version, and sends the resulting patch to the buildmaster. If your tree is not up to date, this will result in the try tree being created with the latest revision, then backwards patches applied to bring it back to the version you actually checked out (plus your actual code changes), but this will still result in the correct tree being used for the build. bzr try does a bzr revision-info to find the base revision, then a bzr diff -r$base.. to obtain the patch. Mercurial hg parents --template '{node}\n' emits the full revision id (as opposed to the common 12-char truncated) which is a SHA1 hash of the current revision’s contents. This is used as the base revision. hg diff then provides the patch relative to that revision. For try to work, your working directory must only have patches that are available from the same remotely-available repository that the build process’ source.Mercurial will use. Perforce try does a p4 changes -m1 ... to determine the latest changelist and implicitly assumes that the local tree is synced to this revision. This is followed by a p4 diff -du to obtain the patch. A p4 patch differs slightly from a normal diff. It contains full depot paths and must be converted to paths relative to the branch top. To convert the following restriction is imposed. The p4base (see P4Source ) is assumed to be //depot Darcs try does a darcs changes --context to find the list of all patches back to and including the last tag that was made. This text file (plus the location of a repository that contains all these patches) is sufficient to re-create the tree. Therefore the contents of this context file are the revision stamp for a Darcs-controlled source tree. It then does a darcs diff -u to compute the patch relative to that revision. Git git branch -v lists all the branches available in the local repository along with the revision ID it points to and a short summary of the last commit. The line containing the currently checked out branch begins with “* “ (star and space) while all the others start with “ “ (two spaces). try scans for this line and extracts the branch name and revision from it. Then it generates a diff against the base revision. Todo I’m not sure if this actually works the way it’s intended since the extracted base revision might not actually exist in the upstream repository. Perhaps we need to add a –remote option to specify the remote tracking branch to generate a diff against. Monotone mtn automate get_base_revision_id emits the full revision id which is a SHA1 hash of the current revision’s contents. This is used as the base revision. mtn diff then provides the patch relative to that revision. For try to work, your working directory must only have patches that are available from the same remotely-available repository that the build process’ source.Monotone will use. patch information You can provide the option –who=dev to designate who is running the try build. This will add the dev to the Reason field on the try build’s status web page. You can also set try_who = dev in the .buildbot/options file. Note that option –who=dev will not work on version 0.8.3 or earlier masters. Similarly, option –comment=COMMENT will specify the comment for the patch, which is also displayed in the patch information. The corresponding config-file option is try_comment . Sending properties You can set properties to send with your change using either the option –property=key=value option, which sets a single property, or the option –properties=key1=value1,key2=value2… option, which sets multiple comma-separated properties. Either of these can be specified multiple times. Note that the option –properties option uses commas to split on properties, so if your property value itself contains a comma, you’ll need to use the option –property option to set it. try –diff Sometimes you might have a patch from someone else that you want to submit to the buildbot. For example, a user may have created a patch to fix some specific bug and sent it to you by email. You’ve inspected the patch and suspect that it might do the job (and have at least confirmed that it doesn’t do anything evil). Now you want to test it out. One approach would be to check out a new local tree, apply the patch, run your local tests, then use buildbot try to run the tests on other platforms. An alternate approach is to use the buildbot try --diff form to have the buildbot test the patch without using a local tree. This form takes a option –diff argument which points to a file that contains the patch you want to apply. By default this patch will be applied to the TRUNK revision, but if you give the optional option –baserev argument, a tree of the given revision will be used as a starting point instead of TRUNK. You can also use buildbot try --diff=- to read the patch from stdin . Each patch has a patchlevel associated with it. This indicates the number of slashes (and preceding pathnames) that should be stripped before applying the diff. This exactly corresponds to the option -p or option –strip argument to the patch utility. By default buildbot try --diff uses a patchlevel of 0, but you can override this with the option -p argument. When you use option –diff , you do not need to use any of the other options that relate to a local tree, specifically option –vc , option –try-topfile , or option –try-topdir . These options will be ignored. Of course you must still specify how to get to the buildmaster (with option –connect , option –tryhost , etc). 2.7.1.3. Other Tools These tools are generally used by buildmaster administrators. sendchange This command is used to tell the buildmaster about source changes. It is intended to be used from within a commit script, installed on the VC server. It requires that you have a PBChangeSource ( PBChangeSource ) running in the buildmaster (by being set in c['change_source'] ). buildbot sendchange --master {MASTERHOST}:{PORT} --auth {USER}:{PASS} --who {USER} {FILENAMES..} The option –auth option specifies the credentials to use to connect to the master, in the form user:pass . If the password is omitted, then sendchange will prompt for it. If both are omitted, the old default (username “change” and password “changepw”) will be used. Note that this password is well-known, and should not be used on an internet-accessible port. The option –master and option –username arguments can also be given in the options file (see .buildbot config directory ). There are other (optional) arguments which can influence the Change that gets submitted: --branch (or option branch ) This provides the (string) branch specifier. If omitted, it defaults to None , indicating the default branch . All files included in this Change must be on the same branch. --category (or option category ) This provides the (string) category specifier. If omitted, it defaults to None , indicating no category . The category property can be used by schedulers to filter what changes they listen to. --project (or option project ) This provides the (string) project to which this change applies, and defaults to ‘’. The project can be used by schedulers to decide which builders should respond to a particular change. --repository (or option repository ) This provides the repository from which this change came, and defaults to '' . --revision This provides a revision specifier, appropriate to the VC system in use. --revision_file This provides a filename which will be opened and the contents used as the revision specifier. This is specifically for Darcs, which uses the output of darcs changes --context as a revision specifier. This context file can be a couple of kilobytes long, spanning a couple lines per patch, and would be a hassle to pass as a command-line argument. --property This parameter is used to set a property on the Change generated by sendchange . Properties are specified as a name : value pair, separated by a colon. You may specify many properties by passing this parameter multiple times. --comments This provides the change comments as a single argument. You may want to use option –logfile instead. --logfile This instructs the tool to read the change comments from the given file. If you use - as the filename, the tool will read the change comments from stdin. --encoding Specifies the character encoding for all other parameters, defaulting to 'utf8' . --vc Specifies which VC system the Change is coming from, one of: cvs , svn , darcs , hg , bzr , git , mtn , or p4 . Defaults to None . user Note that in order to use this command, you need to configure a CommandlineUserManager instance in your master.cfg file, which is explained in Users Options . This command allows you to manage users in buildbot’s database. No extra requirements are needed to use this command, aside from the Buildmaster running. For details on how Buildbot manages users, see Users . --master The user command can be run virtually anywhere provided a location of the running buildmaster. The option –master argument is of the form MASTERHOST : PORT . --username PB connection authentication that should match the arguments to CommandlineUserManager . --passwd PB connection authentication that should match the arguments to CommandlineUserManager . --op There are four supported values for the option –op argument: add , update , remove , and get . Each are described in full in the following sections. --bb_username Used with the option –op=update option, this sets the user’s username for web authentication in the database. It requires option –bb_password to be set along with it. --bb_password Also used with the option –op=update option, this sets the password portion of a user’s web authentication credentials into the database. The password is first encrypted prior to storage for security reasons. --ids When working with users, you need to be able to refer to them by unique identifiers to find particular users in the database. The option –ids option lets you specify a comma separated list of these identifiers for use with the user command. The option –ids option is used only when using option –op=remove or option –op=get . --info Users are known in buildbot as a collection of attributes tied together by some unique identifier (see Users ). These attributes are specified in the form {TYPE}={VALUE} when using the option –info option. These {TYPE}={VALUE} pairs are specified in a comma separated list, so for example: --info=svn=jdoe,git='John Doe <joe@example.com>' The option –info option can be specified multiple times in the user command, as each specified option will be interpreted as a new user. Note that option –info is only used with option –op=add or with option –op=update , and whenever you use option –op=update you need to specify the identifier of the user you want to update. This is done by prepending the option –info arguments with {ID:} . If we were to update 'jschmo' from the previous example, it would look like this: --info=jdoe:git='Joe Doe <joe@example.com>' Note that option –master , option –username , option –passwd , and option –op are always required to issue the user command. The option –master , option –username , and option –passwd options can be specified in the option file with keywords user_master , user_username , and user_passwd , respectively. If user_master is not specified, then option –master from the options file will be used instead. Below are examples of how each command should look. Whenever a user command is successful, results will be shown to whoever issued the command. For option –op=add : buildbot user --master={MASTERHOST} --op=add \ --username={USER} --passwd={USERPW} \ --info={TYPE}={VALUE},... For option –op=update : buildbot user --master={MASTERHOST} --op=update \ --username={USER} --passwd={USERPW} \ --info={ID}:{TYPE}={VALUE},... For option –op=remove : buildbot user --master={MASTERHOST} --op=remove \ --username={USER} --passwd={USERPW} \ --ids={ID1},{ID2},... For option –op=get : buildbot user --master={MASTERHOST} --op=get \ --username={USER} --passwd={USERPW} \ --ids={ID1},{ID2},... A note on option –op=update : when updating the option –bb_username and option –bb_password , the option –info doesn’t need to have additional {TYPE}={VALUE} pairs to update and can just take the {ID} portion. 2.7.1.4. .buildbot config directory Many of the buildbot tools must be told how to contact the buildmaster that they interact with. This specification can be provided as a command-line argument, but most of the time it will be easier to set them in an options file. The buildbot command will look for a special directory named .buildbot , starting from the current directory (where the command was run) and crawling upwards, eventually looking in the user’s home directory. It will look for a file named options in this directory, and will evaluate it as a Python script, looking for certain names to be set. You can just put simple name = 'value' pairs in this file to set the options. For a description of the names used in this file, please see the documentation for the individual buildbot sub-commands. The following is a brief sample of what this file’s contents could be. # for status-reading tools masterstatus = 'buildbot.example.org:12345' # for 'sendchange' or the debug port master = 'buildbot.example.org:18990' Note carefully that the names in the options file usually do not match the command-line option name. master Equivalent to option –master for sendchange . It is the location of the pb.PBChangeSource for `sendchange . username Equivalent to option –username for the sendchange command. branch Equivalent to option –branch for the sendchange command. category Equivalent to option –category for the sendchange command. try_connect Equivalent to option –connect , this specifies how the try command should deliver its request to the buildmaster. The currently accepted values are ssh and pb . try_builders Equivalent to option –builders , specifies which builders should be used for the try build. try_vc Equivalent to option –vc for try , this specifies the version control system being used. try_branch Equivalent to option –branch , this indicates that the current tree is on a non-trunk branch. try_topdir try_topfile Use try_topdir , equivalent to option –try-topdir , to explicitly indicate the top of your working tree, or try_topfile , equivalent to option –try-topfile to name a file that will only be found in that top-most directory. try_host try_username try_dir When try_connect is ssh , the command will use try_host for option –tryhost , try_username for option –username , and try_dir for option –trydir . Apologies for the confusing presence and absence of ‘try’. try_username try_password try_master Similarly, when try_connect is pb , the command will pay attention to try_username for option –username , try_password for option –passwd , and try_master for option –master . try_wait masterstatus try_wait and masterstatus (equivalent to option –wait and master , respectively) are used to ask the try command to wait for the requested build to complete. 2.7.2. buildbot-worker buildbot-worker command-line tool is used for worker management only and does not provide any additional functionality. One can create, start, stop and restart the worker. 2.7.2.1. create-worker This creates a new directory and populates it with files that let it be used as a worker’s base directory. You must provide several arguments, which are used to create the initial buildbot.tac file. The option -r option is advisable here, just like for create-master . buildbot-worker create-worker -r {BASEDIR} {MASTERHOST}:{PORT} {WORKERNAME} {PASSWORD} The create-worker options are described in Worker Options . 2.7.2.2. start This starts a worker which was already created in the given base directory. The daemon is launched in the background, with events logged to a file named twistd.log . buildbot-worker start [--nodaemon] BASEDIR The option –nodaemon option instructs Buildbot to skip daemonizing. The process will start in the foreground. It will only return to the command-line when it is stopped. 2.7.2.3. restart buildbot-worker restart [--nodaemon] BASEDIR This restarts a worker which is already running. It is equivalent to a stop followed by a start . The option –nodaemon option has the same meaning as for start . 2.7.2.4. stop This terminates the daemon worker running in the given directory. buildbot stop BASEDIR Previous Next © Copyright Buildbot Team Members. Built with Sphinx using a theme provided by Read the Docs . | 2026-01-13T09:30:34 |
https://docs.aws.amazon.com/lambda/latest/dg/getting-started.html#get-started-invoke-manually | Create your first Lambda function - AWS Lambda Create your first Lambda function - AWS Lambda Documentation AWS Lambda Developer Guide Prerequisites Create the function Invoke the function Clean up Next steps Create your first Lambda function To get started with Lambda, use the Lambda console to create a function. In a few minutes, you can create and deploy a function and test it in the console. As you carry out the tutorial, you'll learn some fundamental Lambda concepts, like how to pass arguments to your function using the Lambda event object . You'll also learn how to return log outputs from your function, and how to view your function's invocation logs in Amazon CloudWatch Logs. To keep things simple, you create your function using either the Python or Node.js runtime. With these interpreted languages, you can edit function code directly in the console's built-in code editor. With compiled languages like Java and C#, you must create a deployment package on your local build machine and upload it to Lambda. To learn about deploying functions to Lambda using other runtimes, see the links in the Additional resources and next steps section. Tip To learn how to build serverless solutions , check out the Serverless Developer Guide . Prerequisites If you do not have an AWS account, complete the following steps to create one. To sign up for an AWS account Open https://portal.aws.amazon.com/billing/signup . Follow the online instructions. Part of the sign-up procedure involves receiving a phone call or text message and entering a verification code on the phone keypad. When you sign up for an AWS account, an AWS account root user is created. The root user has access to all AWS services and resources in the account. As a security best practice, assign administrative access to a user, and use only the root user to perform tasks that require root user access . AWS sends you a confirmation email after the sign-up process is complete. At any time, you can view your current account activity and manage your account by going to https://aws.amazon.com/ and choosing My Account . After you sign up for an AWS account, secure your AWS account root user, enable AWS IAM Identity Center, and create an administrative user so that you don't use the root user for everyday tasks. Secure your AWS account root user Sign in to the AWS Management Console as the account owner by choosing Root user and entering your AWS account email address. On the next page, enter your password. For help signing in by using root user, see Signing in as the root user in the AWS Sign-In User Guide . Turn on multi-factor authentication (MFA) for your root user. For instructions, see Enable a virtual MFA device for your AWS account root user (console) in the IAM User Guide . Create a user with administrative access Enable IAM Identity Center. For instructions, see Enabling AWS IAM Identity Center in the AWS IAM Identity Center User Guide . In IAM Identity Center, grant administrative access to a user. For a tutorial about using the IAM Identity Center directory as your identity source, see Configure user access with the default IAM Identity Center directory in the AWS IAM Identity Center User Guide . Sign in as the user with administrative access To sign in with your IAM Identity Center user, use the sign-in URL that was sent to your email address when you created the IAM Identity Center user. For help signing in using an IAM Identity Center user, see Signing in to the AWS access portal in the AWS Sign-In User Guide . Assign access to additional users In IAM Identity Center, create a permission set that follows the best practice of applying least-privilege permissions. For instructions, see Create a permission set in the AWS IAM Identity Center User Guide . Assign users to a group, and then assign single sign-on access to the group. For instructions, see Add groups in the AWS IAM Identity Center User Guide . Create a Lambda function with the console In this example, your function takes a JSON object containing two integer values labeled "length" and "width" . The function multiplies these values to calculate an area and returns this as a JSON string. Your function also prints the calculated area, along with the name of its CloudWatch log group. Later in the tutorial, you’ll learn to use CloudWatch Logs to view records of your functions’ invocation. To create a Hello world Lambda function with the console Open the Functions page of the Lambda console. Choose Create function . Select Author from scratch . In the Basic information pane, for Function name , enter myLambdaFunction . For Runtime , choose either Node.js 24 or Python 3.14 . Leave architecture set to x86_64 , and then choose Create function . In addition to a simple function that returns the message Hello from Lambda! , Lambda also creates an execution role for your function. An execution role is an AWS Identity and Access Management (IAM) role that grants a Lambda function permission to access AWS services and resources. For your function, the role that Lambda creates grants basic permissions to write to CloudWatch Logs. Use the console's built-in code editor to replace the Hello world code that Lambda created with your own function code. Node.js To modify the code in the console Choose the Code tab. In the console's built-in code editor, you should see the function code that Lambda created. If you don't see the index.mjs tab in the code editor, select index.mjs in the file explorer as shown on the following diagram. Paste the following code into the index.mjs tab, replacing the code that Lambda created. export const handler = async (event, context) => { const length = event.length; const width = event.width; let area = calculateArea(length, width); console.log(`The area is $ { area}`); console.log('CloudWatch log group: ', context.logGroupName); let data = { "area": area, }; return JSON.stringify(data); function calculateArea(length, width) { return length * width; } }; In the DEPLOY section, choose Deploy to update your function's code: Understanding your function code Before you move to the next step, let's take a moment to look at the function code and understand some key Lambda concepts. The Lambda handler: Your Lambda function contains a Node.js function named handler . A Lambda function in Node.js can contain more than one Node.js function, but the handler function is always the entry point to your code. When your function is invoked, Lambda runs this method. When you created your Hello world function using the console, Lambda automatically set the name of the handler method for your function to handler . Be sure not to edit the name of this Node.js function. If you do, Lambda won’t be able to run your code when you invoke your function. To learn more about the Lambda handler in Node.js, see Define Lambda function handler in Node.js . The Lambda event object: The function handler takes two arguments, event and context . An event in Lambda is a JSON formatted document that contains data for your function to process. If your function is invoked by another AWS service, the event object contains information about the event that caused the invocation. For example, if your function is invoked when an object is uploaded to an Amazon Simple Storage Service (Amazon S3) bucket, the event contains the name of the bucket and the object key. In this example, you’ll create an event in the console by entering a JSON formatted document with two key-value pairs. The Lambda context object: The second argument that your function takes is context . Lambda passes the context object to your function automatically. The context object contains information about the function invocation and execution environment. You can use the context object to output information about your function's invocation for monitoring purposes. In this example, your function uses the logGroupName parameter to output the name of its CloudWatch log group. To learn more about the Lambda context object in Node.js, see Using the Lambda context object to retrieve Node.js function information . Logging in Lambda: With Node.js, you can use console methods like console.log and console.error to send information to your function's log. The example code uses console.log statements to output the calculated area and the name of the function's CloudWatch Logs group. You can also use any logging library that writes to stdout or stderr . To learn more, see Log and monitor Node.js Lambda functions . To learn about logging in other runtimes, see the 'Building with' pages for the runtimes you're interested in. Python To modify the code in the console Choose the Code tab. In the console's built-in code editor, you should see the function code that Lambda created. If you don't see the lambda_function.py tab in the code editor, select lambda_function.py in the file explorer as shown on the following diagram. Paste the following code into the lambda_function.py tab, replacing the code that Lambda created. import json import logging logger = logging.getLogger() logger.setLevel(logging.INFO) def lambda_handler(event, context): # Get the length and width parameters from the event object. The # runtime converts the event object to a Python dictionary length = event['length'] width = event['width'] area = calculate_area(length, width) print(f"The area is { area}") logger.info(f"CloudWatch logs group: { context.log_group_name}") # return the calculated area as a JSON string data = { "area": area} return json.dumps(data) def calculate_area(length, width): return length*width In the DEPLOY section, choose Deploy to update your function's code: Understanding your function code Before you move to the next step, let's take a moment to look at the function code and understand some key Lambda concepts. The Lambda handler: Your Lambda function contains a Python function named lambda_handler . A Lambda function in Python can contain more than one Python function, but the handler function is always the entry point to your code. When your function is invoked, Lambda runs this method. When you created your Hello world function using the console, Lambda automatically set the name of the handler method for your function to lambda_handler . Be sure not to edit the name of this Python function. If you do, Lambda won’t be able to run your code when you invoke your function. To learn more about the Lambda handler in Python, see Define Lambda function handler in Python . The Lambda event object: The function lambda_handler takes two arguments, event and context . An event in Lambda is a JSON formatted document that contains data for your function to process. If your function is invoked by another AWS service, the event object contains information about the event that caused the invocation. For example, if your function is invoked when an object is uploaded to an Amazon Simple Storage Service (Amazon S3) bucket, the event contains the name of the bucket and the object key. In this example, you’ll create an event in the console by entering a JSON formatted document with two key-value pairs. The Lambda context object: The second argument that your function takes is context . Lambda passes the context object to your function automatically. The context object contains information about the function invocation and execution environment. You can use the context object to output information about your function's invocation for monitoring purposes. In this example, your function uses the log_group_name parameter to output the name of its CloudWatch log group. To learn more about the Lambda context object in Python, see Using the Lambda context object to retrieve Python function information . Logging in Lambda: With Python, you can use either a print statement or a Python logging library to send information to your function's log. To illustrate the difference in what's captured, the example code uses both methods. In a production application, we recommend that you use a logging library. To learn more, see Log and monitor Python Lambda functions . To learn about logging in other runtimes, see the 'Building with' pages for the runtimes you're interested in. Invoke the Lambda function using the console code editor To invoke your function using the Lambda console code editor, create a test event to send to your function. The event is a JSON formatted document containing two key-value pairs with the keys "length" and "width" . To create the test event In the TEST EVENTS section of the console code editor, choose Create test event . For Event Name , enter myTestEvent . In the Event JSON section, replace the default JSON with the following: { "length": 6, "width": 7 } Choose Save . To test your function and view invocation records In the TEST EVENTS section of the console code editor, choose the run icon next to your test event: When your function finishes running, the response and function logs are displayed in the OUTPUT tab. You should see results similar to the following: Node.js Status: Succeeded Test Event Name: myTestEvent Response " { \"area\":42}" Function Logs START RequestId: 5c012b0a-18f7-4805-b2f6-40912935034a Version: $LATEST 2024-08-31T23:39:45.313Z 5c012b0a-18f7-4805-b2f6-40912935034a INFO The area is 42 2024-08-31T23:39:45.331Z 5c012b0a-18f7-4805-b2f6-40912935034a INFO CloudWatch log group: /aws/lambda/myLambdaFunction END RequestId: 5c012b0a-18f7-4805-b2f6-40912935034a REPORT RequestId: 5c012b0a-18f7-4805-b2f6-40912935034a Duration: 20.67 ms Billed Duration: 21 ms Memory Size: 128 MB Max Memory Used: 66 MB Init Duration: 163.87 ms Request ID 5c012b0a-18f7-4805-b2f6-40912935034a Python Status: Succeeded Test Event Name: myTestEvent Response " { \"area\": 42}" Function Logs START RequestId: 2d0b1579-46fb-4bf7-a6e1-8e08840eae5b Version: $LATEST The area is 42 [INFO] 2024-08-31T23:43:26.428Z 2d0b1579-46fb-4bf7-a6e1-8e08840eae5b CloudWatch logs group: /aws/lambda/myLambdaFunction END RequestId: 2d0b1579-46fb-4bf7-a6e1-8e08840eae5b REPORT RequestId: 2d0b1579-46fb-4bf7-a6e1-8e08840eae5b Duration: 1.42 ms Billed Duration: 2 ms Memory Size: 128 MB Max Memory Used: 39 MB Init Duration: 123.74 ms Request ID 2d0b1579-46fb-4bf7-a6e1-8e08840eae5b When you invoke your function outside of the Lambda console, you must use CloudWatch Logs to view your function's execution results. To view your function's invocation records in CloudWatch Logs Open the Log groups page of the CloudWatch console. Choose the log group for your function ( /aws/lambda/myLambdaFunction ). This is the log group name that your function printed to the console. Scroll down and choose the Log stream for the function invocations you want to look at. You should see output similar to the following: Node.js INIT_START Runtime Version: nodejs:22.v13 Runtime Version ARN: arn:aws:lambda:us-west-2::runtime:e3aaabf6b92ef8755eaae2f4bfdcb7eb8c4536a5e044900570a42bdba7b869d9 START RequestId: aba6c0fc-cf99-49d7-a77d-26d805dacd20 Version: $LATEST 2024-08-23T22:04:15.809Z 5c012b0a-18f7-4805-b2f6-40912935034a INFO The area is 42 2024-08-23T22:04:15.810Z aba6c0fc-cf99-49d7-a77d-26d805dacd20 INFO CloudWatch log group: /aws/lambda/myLambdaFunction END RequestId: aba6c0fc-cf99-49d7-a77d-26d805dacd20 REPORT RequestId: aba6c0fc-cf99-49d7-a77d-26d805dacd20 Duration: 17.77 ms Billed Duration: 18 ms Memory Size: 128 MB Max Memory Used: 67 MB Init Duration: 178.85 ms Python INIT_START Runtime Version: python:3.13.v16 Runtime Version ARN: arn:aws:lambda:us-west-2::runtime:ca202755c87b9ec2b58856efb7374b4f7b655a0ea3deb1d5acc9aee9e297b072 START RequestId: 9d4096ee-acb3-4c25-be10-8a210f0a9d8e Version: $LATEST The area is 42 [INFO] 2024-09-01T00:05:22.464Z 9315ab6b-354a-486e-884a-2fb2972b7d84 CloudWatch logs group: /aws/lambda/myLambdaFunction END RequestId: 9d4096ee-acb3-4c25-be10-8a210f0a9d8e REPORT RequestId: 9d4096ee-acb3-4c25-be10-8a210f0a9d8e Duration: 1.15 ms Billed Duration: 2 ms Memory Size: 128 MB Max Memory Used: 40 MB Clean up When you're finished working with the example function, delete it. You can also delete the log group that stores the function's logs, and the execution role that the console created. To delete the Lambda function Open the Functions page of the Lambda console. Select the function that you created. Choose Actions , Delete . Type confirm in the text input field and choose Delete . To delete the log group Open the Log groups page of the CloudWatch console. Select the function's log group ( /aws/lambda/myLambdaFunction ). Choose Actions , Delete log group(s) . In the Delete log group(s) dialog box, choose Delete . To delete the execution role Open the Roles page of the AWS Identity and Access Management (IAM) console. Select the function's execution role (for example, myLambdaFunction-role- 31exxmpl ). Choose Delete . In the Delete role dialog box, enter the role name, and then choose Delete . Additional resources and next steps Now that you’ve created and tested a simple Lambda function using the console, take these next steps: Learn to add dependencies to your function and deploy it using a .zip deployment package. Choose your preferred language from the following links. Node.js Deploy Node.js Lambda functions with .zip file archives Typescript Deploy transpiled TypeScript code in Lambda with .zip file archives Python Working with .zip file archives for Python Lambda functions Ruby Deploy Ruby Lambda functions with .zip file archives Java Deploy Java Lambda functions with .zip or JAR file archives Go Deploy Go Lambda functions with .zip file archives C# Build and deploy C# Lambda functions with .zip file archives To learn how to invoke a Lambda function using another AWS service, see Tutorial: Using an Amazon S3 trigger to invoke a Lambda function . Choose one of the following tutorials for more complex examples of using Lambda with other AWS services. Tutorial: Using Lambda with API Gateway : Create an Amazon API Gateway REST API that invokes a Lambda function. Using a Lambda function to access an Amazon RDS database : Use a Lambda function to write data to an Amazon Relational Database Service (Amazon RDS) database through RDS Proxy. Using an Amazon S3 trigger to create thumbnail images : Use a Lambda function to create a thumbnail every time an image file is uploaded to an Amazon S3 bucket. Javascript is disabled or is unavailable in your browser. To use the Amazon Web Services Documentation, Javascript must be enabled. Please refer to your browser's Help pages for instructions. Document Conventions Designing an application Example apps and patterns Did this page help you? - Yes Thanks for letting us know we're doing a good job! If you've got a moment, please tell us what we did right so we can do more of it. Did this page help you? - No Thanks for letting us know this page needs work. We're sorry we let you down. If you've got a moment, please tell us how we can make the documentation better. | 2026-01-13T09:30:34 |
https://es-la.facebook.com/login/?next=https%3A%2F%2Fl.facebook.com%2Fl.php%3Fu%3Dhttps%253A%252F%252Fwww.instagram.com%252F%26amp%253Bh%3DAT0_eO-stakg9vLsOUo7Lt26VLQ_aYkr9Pf8ZZaLhPMiLcqEKHlcgGyJNGUNiyBkcQSC6SVtvR-ocoHfFkGBRUIIfK4kqcuSRuVlDS1_g0KFGeSi6wHVGd63HL5D3r9fcZfhU2T8Lb5znjek | Facebook Facebook Correo o teléfono Contraseña ¿Olvidaste tu cuenta? Crear cuenta nueva Se te bloqueó temporalmente Se te bloqueó temporalmente Parece que hiciste un uso indebido de esta función al ir muy rápido. Se te bloqueó su uso temporalmente. Back Español 한국어 English (US) Tiếng Việt Bahasa Indonesia ภาษาไทย 中文(简体) 日本語 Português (Brasil) Français (France) Deutsch Registrarte Iniciar sesión Messenger Facebook Lite Video Meta Pay Tienda de Meta Meta Quest Ray-Ban Meta Meta AI Más contenido de Meta AI Instagram Threads Centro de información de votación Política de privacidad Centro de privacidad Información Crear anuncio Crear página Desarrolladores Empleo Cookies Opciones de anuncios Condiciones Ayuda Importación de contactos y no usuarios Configuración Registro de actividad Meta © 2026 | 2026-01-13T09:30:34 |
http://docs.buildbot.net/current/manual/cmdline.html#other-tools | 2.7. Command-line Tool — Buildbot 4.3.0 documentation Buildbot 1. Buildbot Tutorial 2. Buildbot Manual 2.1. Introduction 2.2. Installation 2.3. Concepts 2.4. Secret Management 2.5. Configuration 2.6. Customization 2.7. Command-line Tool 2.7.1. buildbot 2.7.1.1. Administrator Tools 2.7.1.2. Developer Tools 2.7.1.3. Other Tools 2.7.1.4. .buildbot config directory 2.7.2. buildbot-worker 2.7.2.1. create-worker 2.7.2.2. start 2.7.2.3. restart 2.7.2.4. stop 2.8. Resources 2.9. Optimization 2.10. Plugin Infrastructure in Buildbot 2.11. Deployment 2.12. Upgrading 3. Buildbot Development 4. Release Notes 5. Older Release Notes 6. API Indices Buildbot 2. Buildbot Manual 2.7. Command-line Tool View page source 2.7. Command-line Tool This section describes command-line tools available after buildbot installation. The two main command-line tools are buildbot and buildbot-worker . The former handles a Buildbot master and the former handles a Buildbot worker. Every command-line tool has a list of global options and a set of commands which have their own options. One can run these tools in the following way: buildbot [global options] command [command options] buildbot-worker [global options] command [command options] The buildbot command is used on the master, while buildbot-worker is used on the worker. Global options are the same for both tools which perform the following actions: --help Print general help about available commands and global options and exit. All subsequent arguments are ignored. --verbose Set verbose output. --version Print current buildbot version and exit. All subsequent arguments are ignored. You can get help on any command by specifying --help as a command option: buildbot command --help You can also use manual pages for buildbot and buildbot-worker for quick reference on command-line options. The remainder of this section describes each buildbot command. See Command Line Index for a full list. 2.7.1. buildbot The buildbot command-line tool can be used to start or stop a buildmaster or buildbot, and to interact with a running buildmaster. Some of its subcommands are intended for buildmaster admins, while some are for developers who are editing the code that the buildbot is monitoring. 2.7.1.1. Administrator Tools The following buildbot sub-commands are intended for buildmaster administrators: create-master buildbot create-master -r {BASEDIR} This creates a new directory and populates it with files that allow it to be used as a buildmaster’s base directory. You will usually want to use the option -r option to create a relocatable buildbot.tac . This allows you to move the master directory without editing this file. upgrade-master buildbot upgrade-master {BASEDIR} This upgrades a previously created buildmaster’s base directory for a new version of buildbot master source code. This will copy the web server static files, and potentially upgrade the db. start buildbot start [--nodaemon] {BASEDIR} This starts a buildmaster which was already created in the given base directory. The daemon is launched in the background, with events logged to a file named twistd.log . The option –nodaemon option instructs Buildbot to skip daemonizing. The process will start in the foreground. It will only return to the command-line when it is stopped. Additionally, the user can set the environment variable START_TIMEOUT to specify the amount of time the script waits for the master to start until it declares the operation as failure. restart buildbot restart [--nodaemon] {BASEDIR} Restart the buildmaster. This is equivalent to stop followed by start The option –nodaemon option has the same meaning as for start . stop buildbot stop {BASEDIR} This terminates the daemon (either buildmaster or worker) running in the given directory. The --clean option shuts down the buildmaster cleanly. With --no-wait option buildbot stop command will send buildmaster shutdown signal and will immediately exit, not waiting for complete buildmaster shutdown. sighup buildbot sighup {BASEDIR} This sends a SIGHUP to the buildmaster running in the given directory, which causes it to re-read its master.cfg file. checkconfig buildbot checkconfig {BASEDIR|CONFIG_FILE} This checks if the buildmaster configuration is well-formed and contains no deprecated or invalid elements. If no arguments are used or the base directory is passed as the argument the config file specified in buildbot.tac is checked. If the argument is the path to a config file then it will be checked without using the buildbot.tac file. cleanupdb buildbot cleanupdb {BASEDIR|CONFIG_FILE} [-q] This command is frontend for various database maintenance jobs: optimiselogs: This optimization groups logs into bigger chunks to apply higher level of compression. This script runs for as long as it takes to finish the job including the time needed to check master.cfg file. copy-db buildbot copy-db {DESTINATION_URL} {BASEDIR} [-q] This command copies all buildbot data from source database configured in the buildbot configuration file to the destination database. The URL of the destination database is specified on the command line. The destination database may have different type from the source database. The destination database must be empty. The script will initialize it in the same way as if a new Buildbot installation was created. Source database must be already upgraded to the current Buildbot version by the buildbot upgrade-master command. 2.7.1.2. Developer Tools These tools are provided for use by the developers who are working on the code that the buildbot is monitoring. try This lets a developer to ask the question What would happen if I committed this patch right now? . It runs the unit test suite (across multiple build platforms) on the developer’s current code, allowing them to make sure they will not break the tree when they finally commit their changes. The buildbot try command is meant to be run from within a developer’s local tree, and starts by figuring out the base revision of that tree (what revision was current the last time the tree was updated), and a patch that can be applied to that revision of the tree to make it match the developer’s copy. This (revision, patch) pair is then sent to the buildmaster, which runs a build with that SourceStamp . If you want, the tool will emit status messages as the builds run, and will not terminate until the first failure has been detected (or the last success). There is an alternate form which accepts a pre-made patch file (typically the output of a command like svn diff ). This --diff form does not require a local tree to run from. See try –diff concerning the --diff command option. For this command to work, several pieces must be in place: the Try_Jobdir or : Try_Userpass , as well as some client-side configuration. Locating the master The try command needs to be told how to connect to the try scheduler, and must know which of the authentication approaches described above is in use by the buildmaster. You specify the approach by using --connect=ssh or --connect=pb (or try_connect = 'ssh' or try_connect = 'pb' in .buildbot/options ). For the PB approach, the command must be given a option –master argument (in the form HOST : PORT ) that points to TCP port that you picked in the Try_Userpass scheduler. It also takes a option –username and option –passwd pair of arguments that match one of the entries in the buildmaster’s userpass list. These arguments can also be provided as try_master , try_username , and try_password entries in the .buildbot/options file. For the SSH approach, the command must be given option –host and option –username , to get to the buildmaster host. It must also be given option –jobdir , which points to the inlet directory configured above. The jobdir can be relative to the user’s home directory, but most of the time you will use an explicit path like ~buildbot/project/trydir . These arguments can be provided in .buildbot/options as try_host , try_username , try_password , and try_jobdir . If you need to use something different from the default ssh command for connecting to the remote system, you can use –ssh command line option or try_ssh in the configuration file. The SSH approach also provides a option –buildbotbin argument to allow specification of the buildbot binary to run on the buildmaster. This is useful in the case where buildbot is installed in a virtualenv on the buildmaster host, or in other circumstances where the buildbot command is not on the path of the user given by option –username . The option –buildbotbin argument can be provided in .buildbot/options as try_buildbotbin The following command line arguments are deprecated, but retained for backward compatibility: --tryhost is replaced by option –host --trydir is replaced by option –jobdir --master is replaced by option –masterstatus Likewise, the following .buildbot/options file entries are deprecated, but retained for backward compatibility: try_dir is replaced by try_jobdir masterstatus is replaced by try_masterstatus Waiting for results If you provide the option –wait option (or try_wait = True in .buildbot/options ), the buildbot try command will wait until your changes have either been proven good or bad before exiting. Unless you use the option –quiet option (or try_quiet=True ), it will emit a progress message every 60 seconds until the builds have completed. The SSH connection method does not support waiting for results. Choosing the Builders A trial build is performed on multiple Builders at the same time, and the developer gets to choose which Builders are used (limited to a set selected by the buildmaster admin with the TryScheduler ’s builderNames= argument). The set you choose will depend upon what your goals are: if you are concerned about cross-platform compatibility, you should use multiple Builders, one from each platform of interest. You might use just one builder if that platform has libraries or other facilities that allow better test coverage than what you can accomplish on your own machine, or faster test runs. The set of Builders to use can be specified with multiple option –builder arguments on the command line. It can also be specified with a single try_builders option in .buildbot/options that uses a list of strings to specify all the Builder names: try_builders = [ "full-OSX" , "full-win32" , "full-linux" ] If you are using the PB approach, you can get the names of the builders that are configured for the try scheduler using the get-builder-names argument: buildbot try --get-builder-names --connect = pb --master = ... --username = ... --passwd = ... Specifying the VC system The try command also needs to know how to take the developer’s current tree and extract the (revision, patch) source-stamp pair. Each VC system uses a different process, so you start by telling the try command which VC system you are using, with an argument like option –vc=cvs or option –vc=git . This can also be provided as try_vc in .buildbot/options . The following names are recognized: bzr cvs darcs hg git mtn p4 svn Finding the top of the tree Some VC systems (notably CVS and SVN) track each directory more-or-less independently, which means the try command needs to move up to the top of the project tree before it will be able to construct a proper full-tree patch. To accomplish this, the try command will crawl up through the parent directories until it finds a marker file. The default name for this marker file is .buildbot-top , so when you are using CVS or SVN you should touch .buildbot-top from the top of your tree before running buildbot try . Alternatively, you can use a filename like ChangeLog or README , since many projects put one of these files in their top-most directory (and nowhere else). To set this filename, use --topfile=ChangeLog , or set it in the options file with try_topfile = 'ChangeLog' . You can also manually set the top of the tree with --topdir=~/trees/mytree , or try_topdir = '~/trees/mytree' . If you use try_topdir , in a .buildbot/options file, you will need a separate options file for each tree you use, so it may be more convenient to use the try_topfile approach instead. Other VC systems which work on full projects instead of individual directories (Darcs, Mercurial, Git, Monotone) do not require try to know the top directory, so the option –try-topfile and option –try-topdir arguments will be ignored. If the try command cannot find the top directory, it will abort with an error message. The following command line arguments are deprecated, but retained for backward compatibility: --try-topdir is replaced by option –topdir --try-topfile is replaced by option –topfile Determining the branch name Some VC systems record the branch information in a way that try can locate it. For the others, if you are using something other than the default branch, you will have to tell the buildbot which branch your tree is using. You can do this with either the option –branch argument, or a try_branch entry in the .buildbot/options file. Determining the revision and patch Each VC system has a separate approach for determining the tree’s base revision and computing a patch. CVS try pretends that the tree is up to date. It converts the current time into a option -D time specification, uses it as the base revision, and computes the diff between the upstream tree as of that point in time versus the current contents. This works, more or less, but requires that the local clock be in reasonably good sync with the repository. SVN try does a svn status -u to find the latest repository revision number (emitted on the last line in the Status against revision: NN message). It then performs an svn diff -r NN to find out how your tree differs from the repository version, and sends the resulting patch to the buildmaster. If your tree is not up to date, this will result in the try tree being created with the latest revision, then backwards patches applied to bring it back to the version you actually checked out (plus your actual code changes), but this will still result in the correct tree being used for the build. bzr try does a bzr revision-info to find the base revision, then a bzr diff -r$base.. to obtain the patch. Mercurial hg parents --template '{node}\n' emits the full revision id (as opposed to the common 12-char truncated) which is a SHA1 hash of the current revision’s contents. This is used as the base revision. hg diff then provides the patch relative to that revision. For try to work, your working directory must only have patches that are available from the same remotely-available repository that the build process’ source.Mercurial will use. Perforce try does a p4 changes -m1 ... to determine the latest changelist and implicitly assumes that the local tree is synced to this revision. This is followed by a p4 diff -du to obtain the patch. A p4 patch differs slightly from a normal diff. It contains full depot paths and must be converted to paths relative to the branch top. To convert the following restriction is imposed. The p4base (see P4Source ) is assumed to be //depot Darcs try does a darcs changes --context to find the list of all patches back to and including the last tag that was made. This text file (plus the location of a repository that contains all these patches) is sufficient to re-create the tree. Therefore the contents of this context file are the revision stamp for a Darcs-controlled source tree. It then does a darcs diff -u to compute the patch relative to that revision. Git git branch -v lists all the branches available in the local repository along with the revision ID it points to and a short summary of the last commit. The line containing the currently checked out branch begins with “* “ (star and space) while all the others start with “ “ (two spaces). try scans for this line and extracts the branch name and revision from it. Then it generates a diff against the base revision. Todo I’m not sure if this actually works the way it’s intended since the extracted base revision might not actually exist in the upstream repository. Perhaps we need to add a –remote option to specify the remote tracking branch to generate a diff against. Monotone mtn automate get_base_revision_id emits the full revision id which is a SHA1 hash of the current revision’s contents. This is used as the base revision. mtn diff then provides the patch relative to that revision. For try to work, your working directory must only have patches that are available from the same remotely-available repository that the build process’ source.Monotone will use. patch information You can provide the option –who=dev to designate who is running the try build. This will add the dev to the Reason field on the try build’s status web page. You can also set try_who = dev in the .buildbot/options file. Note that option –who=dev will not work on version 0.8.3 or earlier masters. Similarly, option –comment=COMMENT will specify the comment for the patch, which is also displayed in the patch information. The corresponding config-file option is try_comment . Sending properties You can set properties to send with your change using either the option –property=key=value option, which sets a single property, or the option –properties=key1=value1,key2=value2… option, which sets multiple comma-separated properties. Either of these can be specified multiple times. Note that the option –properties option uses commas to split on properties, so if your property value itself contains a comma, you’ll need to use the option –property option to set it. try –diff Sometimes you might have a patch from someone else that you want to submit to the buildbot. For example, a user may have created a patch to fix some specific bug and sent it to you by email. You’ve inspected the patch and suspect that it might do the job (and have at least confirmed that it doesn’t do anything evil). Now you want to test it out. One approach would be to check out a new local tree, apply the patch, run your local tests, then use buildbot try to run the tests on other platforms. An alternate approach is to use the buildbot try --diff form to have the buildbot test the patch without using a local tree. This form takes a option –diff argument which points to a file that contains the patch you want to apply. By default this patch will be applied to the TRUNK revision, but if you give the optional option –baserev argument, a tree of the given revision will be used as a starting point instead of TRUNK. You can also use buildbot try --diff=- to read the patch from stdin . Each patch has a patchlevel associated with it. This indicates the number of slashes (and preceding pathnames) that should be stripped before applying the diff. This exactly corresponds to the option -p or option –strip argument to the patch utility. By default buildbot try --diff uses a patchlevel of 0, but you can override this with the option -p argument. When you use option –diff , you do not need to use any of the other options that relate to a local tree, specifically option –vc , option –try-topfile , or option –try-topdir . These options will be ignored. Of course you must still specify how to get to the buildmaster (with option –connect , option –tryhost , etc). 2.7.1.3. Other Tools These tools are generally used by buildmaster administrators. sendchange This command is used to tell the buildmaster about source changes. It is intended to be used from within a commit script, installed on the VC server. It requires that you have a PBChangeSource ( PBChangeSource ) running in the buildmaster (by being set in c['change_source'] ). buildbot sendchange --master {MASTERHOST}:{PORT} --auth {USER}:{PASS} --who {USER} {FILENAMES..} The option –auth option specifies the credentials to use to connect to the master, in the form user:pass . If the password is omitted, then sendchange will prompt for it. If both are omitted, the old default (username “change” and password “changepw”) will be used. Note that this password is well-known, and should not be used on an internet-accessible port. The option –master and option –username arguments can also be given in the options file (see .buildbot config directory ). There are other (optional) arguments which can influence the Change that gets submitted: --branch (or option branch ) This provides the (string) branch specifier. If omitted, it defaults to None , indicating the default branch . All files included in this Change must be on the same branch. --category (or option category ) This provides the (string) category specifier. If omitted, it defaults to None , indicating no category . The category property can be used by schedulers to filter what changes they listen to. --project (or option project ) This provides the (string) project to which this change applies, and defaults to ‘’. The project can be used by schedulers to decide which builders should respond to a particular change. --repository (or option repository ) This provides the repository from which this change came, and defaults to '' . --revision This provides a revision specifier, appropriate to the VC system in use. --revision_file This provides a filename which will be opened and the contents used as the revision specifier. This is specifically for Darcs, which uses the output of darcs changes --context as a revision specifier. This context file can be a couple of kilobytes long, spanning a couple lines per patch, and would be a hassle to pass as a command-line argument. --property This parameter is used to set a property on the Change generated by sendchange . Properties are specified as a name : value pair, separated by a colon. You may specify many properties by passing this parameter multiple times. --comments This provides the change comments as a single argument. You may want to use option –logfile instead. --logfile This instructs the tool to read the change comments from the given file. If you use - as the filename, the tool will read the change comments from stdin. --encoding Specifies the character encoding for all other parameters, defaulting to 'utf8' . --vc Specifies which VC system the Change is coming from, one of: cvs , svn , darcs , hg , bzr , git , mtn , or p4 . Defaults to None . user Note that in order to use this command, you need to configure a CommandlineUserManager instance in your master.cfg file, which is explained in Users Options . This command allows you to manage users in buildbot’s database. No extra requirements are needed to use this command, aside from the Buildmaster running. For details on how Buildbot manages users, see Users . --master The user command can be run virtually anywhere provided a location of the running buildmaster. The option –master argument is of the form MASTERHOST : PORT . --username PB connection authentication that should match the arguments to CommandlineUserManager . --passwd PB connection authentication that should match the arguments to CommandlineUserManager . --op There are four supported values for the option –op argument: add , update , remove , and get . Each are described in full in the following sections. --bb_username Used with the option –op=update option, this sets the user’s username for web authentication in the database. It requires option –bb_password to be set along with it. --bb_password Also used with the option –op=update option, this sets the password portion of a user’s web authentication credentials into the database. The password is first encrypted prior to storage for security reasons. --ids When working with users, you need to be able to refer to them by unique identifiers to find particular users in the database. The option –ids option lets you specify a comma separated list of these identifiers for use with the user command. The option –ids option is used only when using option –op=remove or option –op=get . --info Users are known in buildbot as a collection of attributes tied together by some unique identifier (see Users ). These attributes are specified in the form {TYPE}={VALUE} when using the option –info option. These {TYPE}={VALUE} pairs are specified in a comma separated list, so for example: --info=svn=jdoe,git='John Doe <joe@example.com>' The option –info option can be specified multiple times in the user command, as each specified option will be interpreted as a new user. Note that option –info is only used with option –op=add or with option –op=update , and whenever you use option –op=update you need to specify the identifier of the user you want to update. This is done by prepending the option –info arguments with {ID:} . If we were to update 'jschmo' from the previous example, it would look like this: --info=jdoe:git='Joe Doe <joe@example.com>' Note that option –master , option –username , option –passwd , and option –op are always required to issue the user command. The option –master , option –username , and option –passwd options can be specified in the option file with keywords user_master , user_username , and user_passwd , respectively. If user_master is not specified, then option –master from the options file will be used instead. Below are examples of how each command should look. Whenever a user command is successful, results will be shown to whoever issued the command. For option –op=add : buildbot user --master={MASTERHOST} --op=add \ --username={USER} --passwd={USERPW} \ --info={TYPE}={VALUE},... For option –op=update : buildbot user --master={MASTERHOST} --op=update \ --username={USER} --passwd={USERPW} \ --info={ID}:{TYPE}={VALUE},... For option –op=remove : buildbot user --master={MASTERHOST} --op=remove \ --username={USER} --passwd={USERPW} \ --ids={ID1},{ID2},... For option –op=get : buildbot user --master={MASTERHOST} --op=get \ --username={USER} --passwd={USERPW} \ --ids={ID1},{ID2},... A note on option –op=update : when updating the option –bb_username and option –bb_password , the option –info doesn’t need to have additional {TYPE}={VALUE} pairs to update and can just take the {ID} portion. 2.7.1.4. .buildbot config directory Many of the buildbot tools must be told how to contact the buildmaster that they interact with. This specification can be provided as a command-line argument, but most of the time it will be easier to set them in an options file. The buildbot command will look for a special directory named .buildbot , starting from the current directory (where the command was run) and crawling upwards, eventually looking in the user’s home directory. It will look for a file named options in this directory, and will evaluate it as a Python script, looking for certain names to be set. You can just put simple name = 'value' pairs in this file to set the options. For a description of the names used in this file, please see the documentation for the individual buildbot sub-commands. The following is a brief sample of what this file’s contents could be. # for status-reading tools masterstatus = 'buildbot.example.org:12345' # for 'sendchange' or the debug port master = 'buildbot.example.org:18990' Note carefully that the names in the options file usually do not match the command-line option name. master Equivalent to option –master for sendchange . It is the location of the pb.PBChangeSource for `sendchange . username Equivalent to option –username for the sendchange command. branch Equivalent to option –branch for the sendchange command. category Equivalent to option –category for the sendchange command. try_connect Equivalent to option –connect , this specifies how the try command should deliver its request to the buildmaster. The currently accepted values are ssh and pb . try_builders Equivalent to option –builders , specifies which builders should be used for the try build. try_vc Equivalent to option –vc for try , this specifies the version control system being used. try_branch Equivalent to option –branch , this indicates that the current tree is on a non-trunk branch. try_topdir try_topfile Use try_topdir , equivalent to option –try-topdir , to explicitly indicate the top of your working tree, or try_topfile , equivalent to option –try-topfile to name a file that will only be found in that top-most directory. try_host try_username try_dir When try_connect is ssh , the command will use try_host for option –tryhost , try_username for option –username , and try_dir for option –trydir . Apologies for the confusing presence and absence of ‘try’. try_username try_password try_master Similarly, when try_connect is pb , the command will pay attention to try_username for option –username , try_password for option –passwd , and try_master for option –master . try_wait masterstatus try_wait and masterstatus (equivalent to option –wait and master , respectively) are used to ask the try command to wait for the requested build to complete. 2.7.2. buildbot-worker buildbot-worker command-line tool is used for worker management only and does not provide any additional functionality. One can create, start, stop and restart the worker. 2.7.2.1. create-worker This creates a new directory and populates it with files that let it be used as a worker’s base directory. You must provide several arguments, which are used to create the initial buildbot.tac file. The option -r option is advisable here, just like for create-master . buildbot-worker create-worker -r {BASEDIR} {MASTERHOST}:{PORT} {WORKERNAME} {PASSWORD} The create-worker options are described in Worker Options . 2.7.2.2. start This starts a worker which was already created in the given base directory. The daemon is launched in the background, with events logged to a file named twistd.log . buildbot-worker start [--nodaemon] BASEDIR The option –nodaemon option instructs Buildbot to skip daemonizing. The process will start in the foreground. It will only return to the command-line when it is stopped. 2.7.2.3. restart buildbot-worker restart [--nodaemon] BASEDIR This restarts a worker which is already running. It is equivalent to a stop followed by a start . The option –nodaemon option has the same meaning as for start . 2.7.2.4. stop This terminates the daemon worker running in the given directory. buildbot stop BASEDIR Previous Next © Copyright Buildbot Team Members. Built with Sphinx using a theme provided by Read the Docs . | 2026-01-13T09:30:34 |
https://penneo.com/da/book-a-demo/ | Book en 20-minutters demo - Penneo Produkter Penneo Sign Validator Hvorfor Penneo Integrationer Løsninger Anvendelsesscenarier Digital signering Dokumenthåndtering Udfyld og underskriv PDF-formularer Automatisering af underskriftsprocesser Overholdelse af eIDAS Brancher Revision og regnskab Finans og bank Advokatydelser Ejendom Administration og HR Priser Ressourcer Vidensunivers Trust Center Produktopdateringer SIGN Hjælpecenter KYC Hjælpecenter Systemstatus LOG PÅ Penneo Sign Log ind på Penneo Sign. LOG PÅ Penneo KYC Log ind på Penneo KYC. LOG PÅ BOOK ET MØDE GRATIS PRØVEPERIODE DA EN NO FR NL Produkter Penneo Sign Validator Hvorfor Penneo Integrationer Løsninger Revision og regnskab Finans og bank Advokatydelser Ejendom Administration og HR Anvendelsesscenarier Digital signering Dokumenthåndtering Udfyld og underskriv PDF-formularer Automatisering af underskriftsprocesser Overholdelse af eIDAS Priser Ressourcer Vidensunivers Trust Center Produktopdateringer SIGN Hjælpecenter KYC Hjælpecenter Systemstatus BOOK ET MØDE GRATIS PRØVEPERIODE LOG PÅ DA EN NO FR NL Penneo Sign Log ind på Penneo Sign. LOG PÅ Penneo KYC Log ind på Penneo KYC. LOG PÅ Bruger du stadig tid på at jagte underskrifter? Med Penneos digitale signeringsløsning sparer du tid, styrker din datasikkerhed og tilbyder dine kunder en intuitiv underskriftsoplevelse med MitID og MitID Erhverv – helt uden papir og post. 7.000.000+ dokumenter blev underskrevet med Penneo i 2024. 3.000+ virksomheder bruger Penneo. Book en 20-minutters demo " * " indikerer påkrævede felter Phone Dette felt er til validering og bør ikke ændres. Fornavn * Efternavn * E-mail * Telefon * BE +32 AD +376 AU +61 AT +43 BG +359 CA +1 HR +385 CY +357 CZ +420 DK +45 EE +372 FO +298 FI +358 FR +33 DE +49 GR +30 GL +299 GG +44 HU +36 IS +354 IE +353 IM +44 IT +39 JP +81 LV +371 LI +423 LT +370 LU +352 MO +853 MK +389 MD +373 MC +377 ME +382 NL +31 NO +47 PL +48 PT +351 RO +40 SM +378 SK +421 ES +34 SE +46 CH +41 UA +380 GB +44 US +1 Single line text * Firmanavn * Dette felt er skjult, når du får vist formularen Land * Land Åland Islands Albania Andorra Australia Austria Belarus Belgium Bosnia and Herzegovina Bulgaria Canada China Croatia Cyprus Czech Republic Denmark Estonia Faroe Islands Finland France Georgia Germany Greece Greenland Hong Kong Hungary Iceland India Indonesia Ireland Isle of Man Israel Italy Japan Latvia Liechtenstein Lithuania Luxembourg Macau Macedonia Moldova Monaco Montenegro Netherlands New Zealand Norway Poland Portugal Romania Russia San Marino Serbia Singapore Slovakia Slovenia Spain Sweden Switzerland Taiwan Turkey Ukraine United Kingdom United States Land Dette felt er skjult, når du får vist formularen Form Dette felt er skjult, når du får vist formularen Language Dette felt er skjult, når du får vist formularen utm_source Dette felt er skjult, når du får vist formularen utm_medium Dette felt er skjult, når du får vist formularen utm_campaign Dette felt er skjult, når du får vist formularen utm_content Dette felt er skjult, når du får vist formularen utm_term Dette felt er skjult, når du får vist formularen gclid Dette felt er skjult, når du får vist formularen gbraid Dette felt er skjult, når du får vist formularen wbraid Dette felt er skjult, når du får vist formularen uuid * Jeg accepterer Penneos privatlivspolitik. * Jeg vil gerne modtage nyheder om Penneo og dets produkter. Jeg kan til enhver tid afmelde mig. Produkter Penneo Sign Priser Integrationer Åben API Validator Hvorfor Penneo Løsninger Revision og regnskab Finans og bank Advokatydelser Ejendom Administration og HR Anvendelsesscenarier Digital signering Dokumenthåndtering Udfyld og underskriv PDF-formularer Automatisering af underskriftsprocesser Overholdelse af eIDAS Ressourcer Vidensunivers Trust Center Produktopdateringer SUPPORT SIGN Hjælpecenter KYC Hjælpecenter Systemstatus Virksomhed Om os Karriere Privatlivspolitik Vilkår Brug af cookies Accessibility Statement Whistleblower Policy Kontakt os PENNEO A/S - Gærtorvet 1-5, DK-1799 København V - CVR: 35633766 | 2026-01-13T09:30:34 |
https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/lambda-generating-http-responses.html | Work with requests and responses - Amazon CloudFront Work with requests and responses - Amazon CloudFront Documentation Amazon CloudFront Developer Guide Use functions with origin failover Generate HTTP responses in request triggers Update HTTP responses in origin response triggers Access the request body by choosing the include body option Work with requests and responses To use Lambda@Edge requests and responses, see the following topics: Topics Use Lambda@Edge functions with origin failover Generate HTTP responses in request triggers Update HTTP responses in origin response triggers Access the request body by choosing the include body option Use Lambda@Edge functions with origin failover You can use Lambda@Edge functions with CloudFront distributions that you've set up with origin groups, for example, for origin failover that you configure to help ensure high availability. To use a Lambda function with an origin group, specify the function in an origin request or origin response trigger for an origin group when you create the cache behavior. For more information, see the following: Create origin groups: Create an origin group How origin failover works with Lambda@Edge: Use origin failover with Lambda@Edge functions Generate HTTP responses in request triggers When CloudFront receives a request, you can use a Lambda function to generate an HTTP response that CloudFront returns directly to the viewer without forwarding the response to the origin. Generating HTTP responses reduces the load on the origin, and typically also reduces latency for the viewer. Some common scenarios for generating HTTP responses include the following: Returning a small webpage to the viewer Returning an HTTP 301 or 302 status code to redirect the user to another webpage Returning an HTTP 401 status code to the viewer when the user hasn't authenticated A Lambda@Edge function can generate an HTTP response when the following CloudFront events occur: Viewer request events When a function is triggered by a viewer request event, CloudFront returns the response to the viewer and doesn't cache it. Origin request events When a function is triggered by an origin request event, CloudFront checks the edge cache for a response that was previously generated by the function. If the response is in the cache, the function isn't executed and CloudFront returns the cached response to the viewer. If the response isn't in the cache, the function is executed, CloudFront returns the response to the viewer, and also caches it. To see some sample code for generating HTTP responses, see Lambda@Edge example functions . You can also replace the HTTP responses in response triggers. For more information, see Update HTTP responses in origin response triggers . Programming model This section describes the programming model for using Lambda@Edge to generate HTTP responses. Topics Response object Errors Required fields Response object The response you return as the result parameter of the callback method should have the following structure (note that only the status field is required). const response = { body: 'content', bodyEncoding: 'text' | 'base64', headers: { 'header name in lowercase': [ { key: 'header name in standard case', value: 'header value' }], ... }, status: 'HTTP status code (string)', statusDescription: 'status description' }; The response object can include the following values: body The body, if any, that you want CloudFront to return in the generated response. bodyEncoding The encoding for the value that you specified in the body . The only valid encodings are text and base64 . If you include body in the response object but omit bodyEncoding , CloudFront treats the body as text. If you specify bodyEncoding as base64 but the body is not valid base64, CloudFront returns an error. headers Headers that you want CloudFront to return in the generated response. Note the following: The keys in the headers object are lowercase versions of standard HTTP header names. Using lowercase keys gives you case-insensitive access to the header values. Each header (for example, headers["accept"] or headers["host"] ) is an array of key-value pairs. For a given header, the array contains one key-value pair for each value in the generated response. key (optional) is the case-sensitive name of the header as it appears in an HTTP request; for example, accept or host . Specify value as a header value. If you do not include the header key portion of the key-value pair, Lambda@Edge automatically inserts a header key using the header name that you provide. Regardless of how you've formatted the header name, the header key that is inserted is automatically formatted with initial capitalization for each part, separated by hyphens (-). For example, you can add a header like the following, without a header key: 'content-type': [ { value: 'text/html;charset=UTF-8' }] In this example, Lambda@Edge creates the following header key: Content-Type . For information about restrictions on header usage, see Restrictions on edge functions . status The HTTP status code. Provide the status code as a string. CloudFront uses the provided status code for the following: Return in the response Cache in the CloudFront edge cache, when the response was generated by a function that was triggered by an origin request event Log in CloudFront Access logs (standard logs) If the status value isn't between 200 and 599, CloudFront returns an error to the viewer. statusDescription The description that you want CloudFront to return in the response, to accompany the HTTP status code. You don't need to use standard descriptions, such as OK for an HTTP status code of 200. Errors The following are possible errors for generated HTTP responses. Response Contains a Body and Specifies 204 (No Content) for Status When a function is triggered by a viewer request, CloudFront returns an HTTP 502 status code (Bad Gateway) to the viewer when both of the following are true: The value of status is 204 (No Content) The response includes a value for body This is because Lambda@Edge imposes the optional restriction found in RFC 2616, which states that an HTTP 204 response does not need to contain a message body. Restrictions on the Size of the Generated Response The maximum size of a response that is generated by a Lambda function depends on the event that triggered the function: Viewer request events – 40 KB Origin request events – 1 MB If the response is larger than the allowed size, CloudFront returns an HTTP 502 status code (Bad Gateway) to the viewer. Required fields The status field is required. All other fields are optional. Update HTTP responses in origin response triggers When CloudFront receives an HTTP response from the origin server, if there is an origin-response trigger associated with the cache behavior, you can modify the HTTP response to override what was returned from the origin. Some common scenarios for updating HTTP responses include the following: Changing the status to set an HTTP 200 status code and creating static body content to return to the viewer when an origin returns an error status code (4xx or 5xx). For sample code, see Example: Use an origin response trigger to update the error status code to 200 . Changing the status to set an HTTP 301 or HTTP 302 status code, to redirect the user to another website when an origin returns an error status code (4xx or 5xx). For sample code, see Example: Use an origin response trigger to update the error status code to 302 . Note The function must return a status value between 200 and 599 (inclusive), otherwise CloudFront returns an error to the viewer. You can also replace the HTTP responses in viewer and origin request events. For more information, see Generate HTTP responses in request triggers . When you're working with the HTTP response, Lambda@Edge does not expose the body that is returned by the origin server to the origin-response trigger. You can generate a static content body by setting it to the desired value, or remove the body inside the function by setting the value to be empty. If you don't update the body field in your function, the original body returned by the origin server is returned back to viewer. Access the request body by choosing the include body option You can opt to have Lambda@Edge expose the body in a request for writable HTTP methods (POST, PUT, DELETE, and so on), so that you can access it in your Lambda function. You can choose read-only access, or you can specify that you'll replace the body. To enable this option, choose Include Body when you create a CloudFront trigger for your function that's for a viewer request or origin request event. For more information, see Add triggers for a Lambda@Edge function , or to learn about using Include Body with your function, see Lambda@Edge event structure . Scenarios when you might want to use this feature include the following: Processing web forms, like "contact us" forms, without sending customer input data back to origin servers. Gathering web beacon data that's sent by viewer browsers and processing it at the edge. For sample code, see Lambda@Edge example functions . Note If the request body is large, Lambda@Edge truncates it. For detailed information about the maximum size and truncation, see Restrictions on the request body with the include body option . Javascript is disabled or is unavailable in your browser. To use the Amazon Web Services Documentation, Javascript must be enabled. Please refer to your browser's Help pages for instructions. Document Conventions Event structure Example functions Did this page help you? - Yes Thanks for letting us know we're doing a good job! If you've got a moment, please tell us what we did right so we can do more of it. Did this page help you? - No Thanks for letting us know this page needs work. We're sorry we let you down. If you've got a moment, please tell us how we can make the documentation better. | 2026-01-13T09:30:34 |
https://support.microsoft.com/et-ee/windows/andmete-vaatamine-privaatsuss%C3%A4tete-armatuurlaual-03d3e27f-1981-5ff4-ba1c-d6b1031ae433 | Andmete vaatamine privaatsussätete armatuurlaual - Microsofti tugiteenus Seotud teemad × Windowsi turve, ohutus ja privaatsus Overview Turbe, ohutuse ja privaatsuse ülevaade Windowsi turve Windowsi turbe kasutajaabi Windowsi turve tagab kaitse Enne Xboxi või Windowsi arvuti müümist, kinkimist või taaskasutusse andmist Ründevara eemaldamine Windowsi arvutist Windowsi ohutus Windowsi ohutuse kasutajaabi Brauseriajaloo kuvamine ja kustutamine Microsoft Edge’is Küpsiste kustutamine ja haldamine Windowsi uuesti installimisel saate väärtusliku sisu ohutult eemaldada Kaotsiläinud Windowsi seadme leidmine ja lukustamine Windowsi privaatsus Windowsi privaatsuse kasutajaabi Rakenduste kasutatavad Windowsi privaatsussätted Andmete vaatamine privaatsussätete armatuurlaual Põhisisu juurde Microsoft Tugi Tugi Tugi Avaleht Microsoft 365 Office Tooted Microsoft 365 Outlook Microsoft Teams OneDrive Microsoft Copilot OneNote Windows rohkem… Seadmed Surface Arvuti tarvikud Xbox Arvutimängud HoloLens Surface Hub Riistvara garantiid Konto ja arveldamine konto Microsoft Store ja arveldamine Ressursid Mis on uut? Kogukonnafoorumid Microsoft 365 administraatorid Väikeettevõtete portaal Arendaja Haridus Teatage tehnilise toega seotud pettusest Tooteohutus Rohkem Osta Microsoft 365 Kogu Microsoft Global Microsoft 365 Teams Copilot Windows Surface Xbox Tugi Tarkvara Tarkvara Windowsi rakendused AI OneDrive Outlook Üleminek Skype'ilt Teamsile OneNote Microsoft Teams Arvutid ja seadmed Arvutid ja seadmed Accessories Meelelahutus Meelelahutus PC-mängud Äri Äri Microsofti turve Azure Dynamics 365 Microsoft 365 ettevõtteversioon Microsoft Industry Microsoft Power Platform Windows 365 Arendaja ja IT Arendaja ja IT Microsofti arendaja Microsoft Learn Tehisintellekti-turuplatsi rakenduste tugi Microsofti tehnoloogiakogukond Microsoft Marketplace Visual Studio Marketplace Rewards Muud Muud Tasuta allalaadimised ja turve Kuva saidikaart Otsing Spikri otsing Tulemid puuduvad Loobu Logi sisse Logige sisse Microsofti kontoga Logige sisse või looge konto. Tere! Valige mõni muu konto. Teil on mitu kontot Valige konto, millega soovite sisse logida. Seotud teemad Windowsi turve, ohutus ja privaatsus Overview Turbe, ohutuse ja privaatsuse ülevaade Windowsi turve Windowsi turbe kasutajaabi Windowsi turve tagab kaitse Enne Xboxi või Windowsi arvuti müümist, kinkimist või taaskasutusse andmist Ründevara eemaldamine Windowsi arvutist Windowsi ohutus Windowsi ohutuse kasutajaabi Brauseriajaloo kuvamine ja kustutamine Microsoft Edge’is Küpsiste kustutamine ja haldamine Windowsi uuesti installimisel saate väärtusliku sisu ohutult eemaldada Kaotsiläinud Windowsi seadme leidmine ja lukustamine Windowsi privaatsus Windowsi privaatsuse kasutajaabi Rakenduste kasutatavad Windowsi privaatsussätted Andmete vaatamine privaatsussätete armatuurlaual Andmete vaatamine privaatsussätete armatuurlaual Rakenduskoht Privacy Windows 10 Windows 11 Microsofti konto andmelaud Märkus.: Microsoft on värskendamas seda, kuidas me küsime teilt luba kasutada teie hääleandmeid meie kõnetuvastustehnoloogiat kasutavate Microsofti toodete paremaks muutmiseks. See võib mõjutada andmeid, mida näete oma privaatsussätete armatuurlaual. Lisateavet nende muudatuste kohta vt teemast Kuidas kaitseb Microsoft kõnetuvastustehnoloogiat täiustades minu privaatsust? Kui olete Microsofti toodete ja teenuste kasutamisel oma Microsofti kontoga sisse loginud, saate oma andmed salvestada pilvkeskkonda, et saaksite oma kasutuskogemust paremaks muuta. Privaatsussätete armatuurlaud pakub tööriistu, mille abil saate neid andmeid kuvada ja kustutada ning hallata kasutatavate toodete privaatsussätteid. Armatuurlaual kuvatavad andmed võivad sisaldada andmeid, mis on seotud teie Bingi ja Cortana otsingutega, Microsoft Edge’i sirvimise ja asukoha, hääle, meedia ning rakenduste ja teenustega seotud tegevusega. Kui olete oma andmed kustutanud, kustutame need armatuurlaualt ja hakkame neid oma süsteemidest eemaldama. Rakenduste ja teenuste andmeid võidakse jagada teenusepakkujatega ja muude tootjate rakendustega, millesse logite sisse Oma Microsofti kontoga. Kui otsustate selle teabe kustutada, kustutame kõik tegevusandmed kõnealuste rakenduste kohta, rakenduse käivitamise või sulgemise aja, rakenduse kasutamise aja ja muu diagnostikateabe. Kui soovite eemaldada ka tegevusandmed, mis on seotud teie brauseri küpsistega, peaksite küpsised Microsoft Edge'is või Internet Exploreris kustutama. Kui kasutate mõnda muud brauserit, lugege selle brauseri juhiseid. Saate hallata oma andmeid ja sätteid privaatsussätete armatuurlaua järgmistel lehtedel. Konto tegevusajaloo haldamiseks avage oma privaatsussätete ja -teabe armatuurlaua avaleht . Reklaamisätete haldamiseks avage leht Reklaamisätted . Kui kasutate uut Microsoft Edge’i, kuvatakse sirvimistegevust järgmistel juhtudel. Kui lülitate sisse sirvimisajaloo. Lisateave Kui lülitate sisse Bingi, Microsoft Newsi ja muude Microsofti teenuste jaoks isikupärastatud reklaami ja kasutuskogemuse. Lisateave Kui kasutate uut Microsoft Edge’i pärandversiooni, kuvatakse sirvimistegevust järgmistel juhtudel. Kui olete Windowsi oma Microsofti kontoga sisse logitud. Valige sätte Diagnostikaandmed suvandiks Täielik . Kui lülitate sisse Cortana Windowsis ja Microsoft Edge’is. Kui lülitate Cortanas sisse sirvimisajaloo. Lisateabe saamiseks Microsoft Edge’i kohta lugege artikleid Lisateave Microsoft Edge’i, sirvimisandmete ja privaatsuse kohta ning Microsoft Edge’i InPrivate-sirvimine . Otsingutegevuste andmed kuvatakse järgmistel juhtudel. Otsite Bingi kaudu ja olete Bingi sisse logitud oma Microsofti kontoga, ehkki ka sel juhul saate siiski vaadata oma otsingutegevusi Bing.com-i otsinguajaloo lehel. Satute Cortana kaudu otsinguid tehes Bingi lehtedele. Otsingutegevuste andmeid ei kuvata, kui teete otsinguid Cortana rakenduse kaudu telefonis, mis kasutab iOS-i või Androidi operatsioonisüsteemi. Lugege Microsofti privaatsusavaldust , et saada lisateavet kogutava teabe kohta või lugege lisateavet Windowsi privaatsuse kohta . Kogutavate andmete määramine Andmeid, mida Microsoft kogub, kasutatakse teie turvalisuse tagamiseks ning meie tarkvara, teenuste ja seadmete täiustamiseks. Saate valida, milliseid andmeid soovite jagada. Windows 10 seadmes privaatsussätete muutmiseks valige Start > Sätted > Privaatsus . privaatsussätete muutmiseks Windows 11 seadmes valige Start > Sätted > Privaatsus & turvalisus . Näpunäited andmete vaatamiseks Kui andmete kuvamine privaatsussätete armatuurlaual võtab palju aega, siis kontrollige järgmist. Teie seade on sisse lülitatud ja vooluvõrku ühendatud. Teie seadmel on pidev Interneti-ühendus ning te ei kasuta mahupõhist Interneti-ühendust. Akusäästja on välja lülitatud, kui teie seade töötab akutoitel. Selle kontrollimiseks valige Start > Sätted > Süsteem ja seejärel valige Windows 11 Nupp Aku Windows 10 või Toide & b - Windows 11. Veenduge, et säte Akusäästja oleks välja lülitatud. Kui teile ei kuvata oodatud andmeid, võivad põhjused olla järgmised. Te ei loginud sisse oma Microsofti kontoga. Olete andmed hiljuti kustutanud ja lülitanud välja sätted, mis lubavad Microsoftil andmeid koguda. Te ei kasuta funktsiooni või teenust, mille andmeid proovite vaadata. Võimalik, et olete selle kasutamiseks liiga noor või funktsioon või teenus pole teie riigis või regioonis toetatud. Andmeid ei saa praegu kuvada. Microsoft näitab neid, kui need on saadaval. Andmed pole privaatsussätete armatuurlaual saadaval. Selleks et saada lisateavet kasutatavate toodete kohta, külastage lehte Microsofti privaatsus ja valige teid huvitavad tooted (nt Windows või Xbox). Isikuandmete puhul, mida me armatuurlauale ei lisa, pöörduge meie privaatsusmeeskonna poole . Märkused: Privaatsussätete armatuurlaual kuvatakse meie kogutud andmed. Kui soovite näha Microsofti konto sisselogimistegevuse andmeid, saate vaadata hiljutisi tegevusi . Kui muretsete, et keegi sai volitamata juurdepääsu teie kontole, lugege teemat Microsofti konto taastamine . Teatud andmeid ei pruugita kuvada ega kustutada meie privaatsusavalduse tõttu (nt teatud seadused keelavad meil andmeid, nt arvelduskonto numbreid, riigiasutuste väljastatud identifitseerimisnumbreid või andmed, mis võivad avaldada mõju teiste isikute õigustele ja vabadustele). Lisateavet leiate teema Privaatsusavaldus jaotisest „Juurdepääs isikuandmetele ja nende haldamine“. TELLIGE RSS-KANALID Kas vajate veel abi? Kas soovite rohkem valikuvariante? Tutvustus Kogukonnafoorum Kontaktteave Siin saate tutvuda tellimusega kaasnevate eelistega, sirvida koolituskursusi, õppida seadet kaitsma ja teha veel palju muud. Microsoft 365 tellimuse eelised Microsoft 365 koolitus Microsofti turbeteenus Hõlbustuskeskus Kogukonnad aitavad teil küsimusi esitada ja neile vastuseid saada, anda tagasisidet ja saada nõu rikkalike teadmistega asjatundjatelt. Nõu küsimine Microsofti kogukonnafoorumis Microsofti spetsialistide kogukonnafoorum Windows Insideri programmis osalejad Microsoft 365 Insideri programmis osalejad Leidke lahendused levinud probleemidele või võtke ühendust klienditeenindajaga. Võrgutugi Kas sellest teabest oli abi? Jah Ei Aitäh! Veel tagasisidet Microsoftile? Kas saaksite aidata meil teenust paremaks muuta? (Saatke Microsoftile tagasisidet, et saaksime aidata.) Kui rahul te keelekvaliteediga olete? Mis mõjutas teie hinnangut? Leidsin oma probleemile lahenduse Juhised olid selged Tekstist oli lihtne aru saada Tekstis pole žargooni Piltidest oli abi Tõlkekvaliteet Tekst ei vastanud minu ekraanipildile Valed juhised Liiga tehniline Pole piisavalt teavet Pole piisavalt pilte Tõlkekvaliteet Kas soovite anda veel tagasisidet? (Valikuline) Saada tagasiside Kui klõpsate nuppu Edasta, kasutatakse teie tagasisidet Microsofti toodete ja teenuste täiustamiseks. IT-administraator saab neid andmeid koguda. Privaatsusavaldus. Täname tagasiside eest! × Mis on uut? Copilot organisatsioonidele Copilot isiklikuks kasutuseks Microsoft 365 Windows 11 rakendused Microsoft Store Konto profiil Allalaadimiskeskus Tagastused Tellimuse jälgimine Ringlussevõtt Commercial Warranties Haridus Microsoft Education Haridusseadmed Microsoft Teams haridusasutustele Microsoft 365 Education Office Education Haridustöötajate koolitus ja arendus Pakkumised õpilastele ja vanematele Azure õpilastele Äri Microsofti turve Azure Dynamics 365 Microsoft 365 Microsoft Advertising Microsoft 365 Copilot Microsoft Teamsi jaoks Arendaja ja IT Microsofti arendaja Microsoft Learn Tehisintellekti-turuplatsi rakenduste tugi Microsofti tehnoloogiakogukond Microsoft Marketplace Microsoft Power Platform Marketplace Rewards Visual Studio Ettevõte Töökohad Teave Microsofti kohta Privaatsus Microsoftis Investorid Jätkusuutlikkus Eesti (Eesti) Teie privaatsusvalikutest loobumise ikoon Teie privaatsusvalikud Teie privaatsusvalikutest loobumise ikoon Teie privaatsusvalikud Tarbijaseisundi privaatsus Võtke Microsoftiga ühendust Privaatsus Halda küpsiseid Kasutustingimused Kaubamärgid Reklaamide kohta EU Compliance DoCs © Microsoft 2026 | 2026-01-13T09:30:34 |
https://docs.aws.amazon.com/id_id/AmazonCloudFront/latest/DeveloperGuide/lambda-edge-how-it-works-tutorial.html#lambda-edge-how-it-works-tutorial-create-function | Tutorial: Buat fungsi Lambda @Edge dasar (konsol) - Amazon CloudFront Tutorial: Buat fungsi Lambda @Edge dasar (konsol) - Amazon CloudFront Dokumentasi Amazon CloudFront Panduan Developerr Langkah 1: Mendaftar untuk Akun AWS Langkah 2: Buat CloudFront distribusi Langkah 3: Buat fungsi Anda Langkah 4: Tambahkan CloudFront pemicu untuk menjalankan fungsi Langkah 5: Verifikasi bahwa fungsi berjalan Langkah 6: Memecahkan masalah Langkah 7: Bersihkan sumber daya contoh Anda Informasi Terkait Terjemahan disediakan oleh mesin penerjemah. Jika konten terjemahan yang diberikan bertentangan dengan versi bahasa Inggris aslinya, utamakan versi bahasa Inggris. Tutorial: Buat fungsi Lambda @Edge dasar (konsol) Tutorial ini menunjukkan kepada Anda bagaimana memulai dengan Lambda @Edge dengan membuat dan mengonfigurasi contoh fungsi Node.js yang berjalan di. CloudFront Contoh ini menambahkan header keamanan HTTP ke respons saat CloudFront mengambil file. (Ini dapat meningkatkan keamanan dan privasi untuk situs web.) Anda tidak memerlukan situs web Anda sendiri untuk tutorial ini. Namun, ketika Anda memilih untuk membuat solusi Lambda @Edge Anda sendiri, Anda mengikuti langkah-langkah serupa dan memilih dari opsi yang sama. Topik Langkah 1: Mendaftar untuk Akun AWS Langkah 2: Buat CloudFront distribusi Langkah 3: Buat fungsi Anda Langkah 4: Tambahkan CloudFront pemicu untuk menjalankan fungsi Langkah 5: Verifikasi bahwa fungsi berjalan Langkah 6: Memecahkan masalah Langkah 7: Bersihkan sumber daya contoh Anda Informasi Terkait Langkah 1: Mendaftar untuk Akun AWS Jika Anda belum melakukannya, daftar untuk Akun AWS. Untuk informasi selengkapnya, lihat Mendaftar untuk Akun AWS . Langkah 2: Buat CloudFront distribusi Sebelum membuat contoh fungsi Lambda@Edge, Anda harus memiliki CloudFront yang dapat dikerjakan, yang mencakup asal muasal untuk menyajikan konten. Untuk contoh ini, Anda membuat CloudFront distribusi yang menggunakan bucket Amazon S3 sebagai asal distribusi. Jika Anda sudah memiliki lingkungan untuk digunakan, Anda dapat melewati langkah ini. Untuk membuat CloudFront distribusi dengan asal Amazon S3 Buat bucket Amazon S3 dengan satu atau dua file, seperti file citra, untuk konten sampel. Untuk bantuan, ikuti langkah dalam Unggah konten Anda ke Amazon S3 . Pastikan Anda mengatur izin untuk memberikan akses baca publik ke objek dalam keranjang Anda. Buat CloudFront distribusi dan tambahkan bucket S3 Anda sebagai asal, dengan mengikuti langkah-langkah di Buat distribusi CloudFront web . Jika Anda sudah memiliki distribusi, Anda dapat menambahkan bucket sebagai asal distribusi tersebut. Tip Catat ID distribusi Anda. Kemudian dalam tutorial ini ketika Anda menambahkan CloudFront pemicu untuk fungsi Anda, Anda harus memilih ID untuk distribusi Anda dalam daftar dropdown—misalnya,. E653W22221KDDL Langkah 3: Buat fungsi Anda Pada langkah ini, Anda membuat fungsi Lambda dari templat cetak biru di konsol Lambda. Fungsi menambahkan kode untuk memperbarui header keamanan di CloudFront distribusi. Untuk membuat fungsi Lambda Masuk ke Konsol Manajemen AWS dan buka AWS Lambda konsol di https://console.aws.amazon.com/lambda/ . penting Pastikan Anda berada di AS-Timur-1 (Virginia N.) ( Wilayah AWS us-east-1). Anda harus berada di Wilayah ini untuk membuat fungsi Lambda@Edge. Pilih Buat fungsi . Pada halaman fungsi Buat , pilih Gunakan cetak biru , lalu filter untuk CloudFront cetak biru dengan memasukkan di bidang pencarian. cloudfront catatan CloudFront cetak biru hanya tersedia di Wilayah AS-Timur-1 ( Virginia N.) (us-east-1). Pilih cetak biru header Modify HTTP response sebagai template untuk fungsi Anda. Masukkan informasi tentang fungsi Anda berikut ini: Nama fungsi — Masukkan nama untuk fungsi Anda. Peran eksekusi - Pilih cara mengatur izin untuk fungsi Anda. Untuk menggunakan templat kebijakan izin Lambda @Edge dasar yang direkomendasikan, pilih Buat peran baru dari AWS templat kebijakan. Nama peran — Masukkan nama untuk peran yang dibuat oleh templat kebijakan. Templat kebijakan — Lambda secara otomatis menambahkan templat kebijakan Izin Lambda @Edge Dasar karena Anda memilih CloudFront cetak biru sebagai dasar fungsi Anda. Template kebijakan ini menambahkan izin peran eksekusi yang memungkinkan CloudFront untuk menjalankan fungsi Lambda untuk Anda CloudFront di lokasi di seluruh dunia. Untuk informasi selengkapnya, lihat Siapkan izin dan peran IAM untuk Lambda @Edge . Pilih Buat fungsi di bagian bawah halaman. Di panel Deploy to Lambda @Edge yang muncul, pilih Batal. (Untuk tutorial ini, Anda harus memodifikasi kode fungsi sebelum menerapkan fungsi ke Lambda @Edge.) Gulir ke bawah ke bagian Sumber kode halaman. Ganti kode templat dengan fungsi yang memodifikasi header keamanan yang dikembalikan oleh Anda. Misalnya, Anda dapat menggunakan kode yang serupa dengan yang berikut ini: 'use strict'; export const handler = (event, context, callback) => { //Get contents of response const response = event.Records[0].cf.response; const headers = response.headers; //Set new headers headers['strict-transport-security'] = [ { key: 'Strict-Transport-Security', value: 'max-age= 63072000; includeSubdomains; preload'}]; headers['content-security-policy'] = [ { key: 'Content-Security-Policy', value: "default-src 'none'; img-src 'self'; script-src 'self'; style-src 'self'; object-src 'none'"}]; headers['x-content-type-options'] = [ { key: 'X-Content-Type-Options', value: 'nosniff'}]; headers['x-frame-options'] = [ { key: 'X-Frame-Options', value: 'DENY'}]; headers['x-xss-protection'] = [ { key: 'X-XSS-Protection', value: '1; mode=block'}]; headers['referrer-policy'] = [ { key: 'Referrer-Policy', value: 'same-origin'}]; //Return modified response callback(null, response); }; Pilih File , Simpan untuk menyimpan kode yang diperbarui. Pilih Deploy . Lanjutkan ke bagian berikutnya untuk menambahkan CloudFront pemicu untuk menjalankan fungsi. Langkah 4: Tambahkan CloudFront pemicu untuk menjalankan fungsi Sekarang Anda memiliki fungsi Lambda untuk memperbarui header keamanan, konfigurasikan CloudFront memicu untuk menjalankan fungsi Anda untuk menambahkan header dalam respons apa pun yang CloudFront dari tempat awal distribusi Anda. Untuk mengkonfigurasi CloudFront pemicu untuk fungsi Anda Di konsol Lambda, pada halaman Ikhtisar fungsi untuk fungsi Anda, pilih Tambah pemicu. Untuk konfigurasi Trigger , pilih CloudFront . Pilih Terapkan ke Lambda @Edge . Di panel Deploy to Lambda @Edge, di bawah pemicu CloudFront Konfigurasi , masukkan informasi berikut: Distribusi — ID CloudFront distribusi untuk dikaitkan dengan fungsi Anda. Dalam daftar dropdown, pilih ID distribusi. Perilaku cache — Perilaku cache yang digunakan dengan pemicu. Untuk contoh ini, biarkan nilai disetel ke * , yang berarti perilaku cache default distribusi Anda. Untuk informasi selengkapnya, lihat Pengaturan perilaku cache dalam topik Semua referensi pengaturan distribusi . CloudFront event - Pemicu yang menentukan kapan fungsi Anda berjalan. Kami ingin fungsi header keamanan berjalan setiap kali CloudFront mengembalikan respons dari asal. Dalam daftar dropdown, pilih Respons asal . Untuk informasi selengkapnya, lihat Tambahkan pemicu untuk fungsi Lambda @Edge . Pilih kotak centang Konfirmasi penerapan ke Lambda @Edge. Pilih Deploy untuk menambahkan pemicu dan mereplikasi fungsi ke AWS lokasi di seluruh dunia. Tunggu fungsi mereplikasi. Ini biasanya memerlukan waktu beberapa menit. Anda dapat memeriksa untuk melihat apakah replikasi selesai oleh menuju ke CloudFront konsol dan melihat distribusi Anda. Tunggu status distribusi berubah dari Deploying ke tanggal dan waktu, yang berarti bahwa fungsi Anda telah direplikasi. Untuk memverifikasi bahwa fungsi bekerja, ikuti langkah-langkah di bagian berikutnya. Langkah 5: Verifikasi bahwa fungsi berjalan Sekarang setelah Anda membuat fungsi Lambda dan mengonfigurasi pemicu untuk menjalankannya untuk CloudFront distribusi, periksa untuk memastikan bahwa fungsi tersebut memenuhi apa yang Anda harapkan. Dalam contoh ini, kami memeriksa header HTTP yang CloudFront kembali, untuk memastikan bahwa judul keamanan ditambahkan. Untuk memverifikasi bahwa fungsi Lambda@Edge Anda menambahkan header keamanan Dalam peramban, masukkan URL untuk file dalam buket S3. Misalnya, Anda mungkin menggunakan URL yang serupa dengan https://d111111abcdef8.cloudfront.net/image.jpg . Untuk informasi selengkapnya tentang nama CloudFront domain yang akan digunakan dalam URL file, lihat Kustomisasi format URL untuk file di CloudFront . Buka toolbar Web Developer browser Anda. Misalnya, di jendela browser Anda di Chrome, buka menu konteks (klik kanan), lalu pilih Periksa . Pilih Jaringan tab. Muat ulang halaman untuk menampilkan citra Anda, lalu pilih permintaan HTTP di panel kiri. Anda melihat header HTTP yang ditampilkan dalam panel terpisah. Lihat daftar header HTTP untuk memverifikasi bahwa header keamanan yang diharapkan disertakan dalam daftar. Misalnya, Anda mungkin melihat header yang mirip dengan yang ditampilkan di screenshot berikut. Jika header keamanan disertakan dalam daftar header Anda, bagus! Anda telah berhasil membuat fungsi Lambda@Edge pertama Anda. Jika CloudFront mengembalikan kesalahan atau ada masalah lain, lanjutkan ke langkah berikutnya untuk memecahkan masalah. Langkah 6: Memecahkan masalah Jika CloudFront mengembalikan kesalahan atau tidak menambahkan header keamanan seperti yang diharapkan, Anda dapat menyelidiki eksekusi fungsi Anda dengan melihat CloudWatch Log. Pastikan untuk menggunakan log yang disimpan di AWS lokasi yang paling dekat dengan lokasi di mana fungsi dijalankan. Misalnya, jika Anda melihat file dari London, coba ubah Wilayah dalam CloudWatch konsol ke Eropa (London). Untuk memeriksa CloudWatch log untuk fungsi Lambda@Edge Anda Masuk ke Konsol Manajemen AWS dan buka CloudWatch konsol di https://console.aws.amazon.com/cloudwatch/ . Perubahan Wilayah ke lokasi yang ditampilkan saat Anda melihat file di browser Anda. Di sinilah fungsi beroperasi. Di panel kiri, pilih Log untuk melihat log untuk distribusi Anda. Untuk informasi selengkapnya, lihat Pantau CloudFront metrik dengan Amazon CloudWatch . Langkah 7: Bersihkan sumber daya contoh Anda Jika Anda membuat bucket dan CloudFront distribusi Amazon S3 hanya untuk tutorial ini, hapus AWS sumber daya yang Anda alokasikan sehingga Anda tidak lagi dikenakan biaya. Setelah Anda menghapus AWS sumber daya, konten apa pun yang Anda tambahkan tidak lagi tersedia. Tugas Hapus ember S3 Hapus fungsi Lambda Hapus CloudFront distribusi Hapus ember S3 Sebelum Anda menghapus buket Amazon S3, pastikan pembuatan log dinonaktifkan untuk buket. Jika tidak, AWS terus menulis log ke bucket Anda saat Anda menghapusnya. Untuk menonaktifkan pembuatan log untuk bucket Buka konsol Amazon S3 di. https://console.aws.amazon.com/s3/ Pilih keranjang Anda, lalu pilih Properti . Dari Properti , pilih Pencatatan . Hapus kotak centang Diaktifkan . Pilih Simpan . Sekarang, Anda dapat menghapus bucket Anda. Untuk informasi selengkapnya, lihat Menghapus bucket di Panduan Pengguna Konsol Layanan Penyimpanan Sederhana Amazon . Hapus fungsi Lambda Untuk instruksi untuk menghapus asosiasi fungsi Lambda dan opsional fungsi itu sendiri, lihat. Hapus fungsi dan replika Lambda @Edge Hapus CloudFront distribusi Sebelum Anda menghapus CloudFront distribusi, Anda harus menonaktifkannya. Distribusi yang dinonaktifkan tidak lagi berfungsi, dan tidak dikenakan biaya. Anda dapat mengaktifkan distribusi yang dinonaktifkan kapan saja. Setelah Anda menghapus distribusi yang dinonaktifkan, maka tidak lagi tersedia. Untuk menonaktifkan dan menghapus CloudFront distribusi Buka CloudFront konsol di https://console.aws.amazon.com/cloudfront/v4/home . Pilih distribusi yang ingin Anda nonaktifkan, lalu pilih Nonaktifkan . Saat diminta untuk mengonfirmasi, pilih Ya, Nonaktifkan . Pilih distribusi yang dinonaktifkan, lalu pilih Hapus . Saat diminta konfirmasi, pilih Ya, Hapus . Informasi Terkait Sekarang, setelah Anda memiliki gagasan dasar tentang cara kerja fungsi Lambda@Edge, pelajari lebih lanjut dengan membaca hal berikut: Lambda @Edge contoh fungsi Praktik Terbaik Desain Lambda @Edge Mengurangi Latensi dan Menggeser Komputasi ke Edge dengan Lambda @Edge Javascript dinonaktifkan atau tidak tersedia di browser Anda. Untuk menggunakan Dokumentasi AWS, Javascript harus diaktifkan. Lihat halaman Bantuan browser Anda untuk petunjuk. Konvensi Dokumen Memulai dengan Lambda @Edge Mengatur izin dan peran IAM Apakah halaman ini membantu Anda? - Ya Terima kasih telah memberitahukan bahwa hasil pekerjaan kami sudah baik. Jika Anda memiliki waktu luang, beri tahu kami aspek apa saja yang sudah bagus, agar kami dapat menerapkannya secara lebih luas. Apakah halaman ini membantu Anda? - Tidak Terima kasih telah memberi tahu kami bahwa halaman ini perlu ditingkatkan. Maaf karena telah mengecewakan Anda. Jika Anda memiliki waktu luang, beri tahu kami bagaimana dokumentasi ini dapat ditingkatkan. | 2026-01-13T09:30:34 |
https://docs.aws.amazon.com/ja_jp/AmazonCloudFront/latest/DeveloperGuide/lambda-edge-event-request-response.html | Lambda@Edge がリクエストとレスポンスで機能する仕組み - Amazon CloudFront Lambda@Edge がリクエストとレスポンスで機能する仕組み - Amazon CloudFront ドキュメント Amazon CloudFront デベロッパーガイド Lambda@Edge がリクエストとレスポンスで機能する仕組み CloudFront ディストリビューションを Lambda@Edge 関数に関連付けると、CloudFront エッジロケーションでリクエストとレスポンスがインターセプトされます。Lambda 関数は、次の CloudFront イベントの発生時に実行できます。 CloudFront がビューワーからリクエストを受信したとき (ビューワーリクエスト) CloudFront がリクエストをオリジンに転送する前 (オリジンリクエスト) CloudFront がオリジンからレスポンスを受信したとき (オリジンレスポンス) CloudFront がビューワーにレスポンスを返す前 (ビューワーレスポンス) AWS WAF を使用している場合、Lambda@Edge ビューワーリクエストは AWS WAF ルールの適用後に実行されます。 詳細については、「 リクエストとレスポンスを使用する 」および「 Lambda@Edge イベント構造 」を参照してください。 ブラウザで JavaScript が無効になっているか、使用できません。 AWS ドキュメントを使用するには、JavaScript を有効にする必要があります。手順については、使用するブラウザのヘルプページを参照してください。 ドキュメントの表記規則 Lambda@Edge でカスタマイズする Lambda@Edge の使用方法 このページは役に立ちましたか? - はい ページが役に立ったことをお知らせいただき、ありがとうございます。 お時間がある場合は、何が良かったかお知らせください。今後の参考にさせていただきます。 このページは役に立ちましたか? - いいえ このページは修正が必要なことをお知らせいただき、ありがとうございます。ご期待に沿うことができず申し訳ありません。 お時間がある場合は、ドキュメントを改善する方法についてお知らせください。 | 2026-01-13T09:30:34 |
https://docs.aws.amazon.com/id_id/AmazonCloudFront/latest/DeveloperGuide/troubleshooting-response-errors.html | Memecahkan masalah kode status respons kesalahan di CloudFront - Amazon CloudFront Memecahkan masalah kode status respons kesalahan di CloudFront - Amazon CloudFront Dokumentasi Amazon CloudFront Panduan Developerr Terjemahan disediakan oleh mesin penerjemah. Jika konten terjemahan yang diberikan bertentangan dengan versi bahasa Inggris aslinya, utamakan versi bahasa Inggris. Memecahkan masalah kode status respons kesalahan di CloudFront Jika CloudFront meminta objek dari asal Anda, dan asal mengembalikan kode status HTTP 4xx atau 5xx, ada masalah dengan komunikasi antara CloudFront dan asal Anda. Topik ini juga mencakup langkah-langkah pemecahan masalah untuk kode status ini saat menggunakan Lambda @Edge atau Fungsi. CloudFront Topik berikut memberikan penjelasan rinci tentang penyebab potensial di balik respons kesalahan ini dan menawarkan step-by-step panduan tentang cara mendiagnosis dan menyelesaikan masalah yang mendasarinya. Topik Kode status HTTP 400 (Permintaan Buruk) Kode status HTTP 401 (Tidak Sah) Kode status HTTP 403 (Metode tidak valid) Kode status HTTP 403 (Izin Ditolak) Kode status HTTP 404 (Tidak Ditemukan) Kode status HTTP 412 (Prasyarat Gagal) Kode status HTTP 500 (Kesalahan Server Internal) Kode status HTTP 502 (Gerbang Buruk) Kode status HTTP 503 (Layanan Tidak Tersedia) Kode status HTTP 504 (Gateway Timeout) Javascript dinonaktifkan atau tidak tersedia di browser Anda. Untuk menggunakan Dokumentasi AWS, Javascript harus diaktifkan. Lihat halaman Bantuan browser Anda untuk petunjuk. Konvensi Dokumen Memecahkan masalah distribusi Kode status HTTP 400 (Permintaan Buruk) Apakah halaman ini membantu Anda? - Ya Terima kasih telah memberitahukan bahwa hasil pekerjaan kami sudah baik. Jika Anda memiliki waktu luang, beri tahu kami aspek apa saja yang sudah bagus, agar kami dapat menerapkannya secara lebih luas. Apakah halaman ini membantu Anda? - Tidak Terima kasih telah memberi tahu kami bahwa halaman ini perlu ditingkatkan. Maaf karena telah mengecewakan Anda. Jika Anda memiliki waktu luang, beri tahu kami bagaimana dokumentasi ini dapat ditingkatkan. | 2026-01-13T09:30:34 |
https://www.php.net/manual/en/function.session-module-name.php | PHP: session_module_name - Manual update page now Downloads Documentation Get Involved Help Search docs Getting Started Introduction A simple tutorial Language Reference Basic syntax Types Variables Constants Expressions Operators Control Structures Functions Classes and Objects Namespaces Enumerations Errors Exceptions Fibers Generators Attributes References Explained Predefined Variables Predefined Exceptions Predefined Interfaces and Classes Predefined Attributes Context options and parameters Supported Protocols and Wrappers Security Introduction General considerations Installed as CGI binary Installed as an Apache module Session Security Filesystem Security Database Security Error Reporting User Submitted Data Hiding PHP Keeping Current Features HTTP authentication with PHP Cookies Sessions Handling file uploads Using remote files Connection handling Persistent Database Connections Command line usage Garbage Collection DTrace Dynamic Tracing Function Reference Affecting PHP's Behaviour Audio Formats Manipulation Authentication Services Command Line Specific Extensions Compression and Archive Extensions Cryptography Extensions Database Extensions Date and Time Related Extensions File System Related Extensions Human Language and Character Encoding Support Image Processing and Generation Mail Related Extensions Mathematical Extensions Non-Text MIME Output Process Control Extensions Other Basic Extensions Other Services Search Engine Extensions Server Specific Extensions Session Extensions Text Processing Variable and Type Related Extensions Web Services Windows Only Extensions XML Manipulation GUI Extensions Keyboard Shortcuts ? This help j Next menu item k Previous menu item g p Previous man page g n Next man page G Scroll to bottom g g Scroll to top g h Goto homepage g s Goto search (current page) / Focus search box session_name » « session_id PHP Manual Function Reference Session Extensions Sessions Session Functions Change language: English German Spanish French Italian Japanese Brazilian Portuguese Russian Turkish Ukrainian Chinese (Simplified) Other session_module_name (PHP 4, PHP 5, PHP 7, PHP 8) session_module_name — Get and/or set the current session module Description session_module_name ( ? string $module = null ): string | false session_module_name() gets the name of the current session module, which is also known as session.save_handler . Parameters module If module is specified and not null , that module will be used instead. Passing "user" to this parameter is forbidden. Instead session_set_save_handler() has to be called to set a user defined session handler. Return Values Returns the name of the current session module, or false on failure. Changelog Version Description 8.0.0 module is nullable now. 7.2.0 It is now explicitly forbidden to set the module name to "user" . Formerly, this has been silently ignored. Found A Problem? Learn How To Improve This Page • Submit a Pull Request • Report a Bug ＋ add a note User Contributed Notes 2 notes up down 5 raees at steelbrain dot com dot pk ¶ 11 years ago This function is used to set the Session Module at site or script level. The global configuration can be done in php.ini under the [Session] section and with the name of "session.save_handler". The sessions are saved in files by default, like so: session.save_handler = files But with this configuration you set one of your websites to use some other session module (if you have them installed and extension loaded with PHP), like so: <?php // NOTE: You must use this function before starting session with session_start(); to make it work properly session_module_name ( 'memcache' ); // or pgsql or redis etc // You'll need to define a save path also, if the module is other than files, like so: session_save_path ( 'localhost:11211' ); // memcache uses port 11211 // or you can use multiple for load balancing: session_save_path ( 'localhost:11211:41,otherhost:11211:60' ) // First part is hostname or path to socket, next is port and the last is the weight for that server //The function also returns the value of the current session module. echo session_module_name (); // will print memcache in our case // or maybe a check if( session_module_name () != 'memcache' ){ // Do something, throw an exception maybe } up down -3 Anonymous ¶ 10 years ago was looking for a rather comprehensive list of modules, and found http://stackoverflow.com/questions/8415962/what-exactly-phps-function-session-module-name-is-for but there are more. ＋ add a note Session Functions session_​abort session_​cache_​expire session_​cache_​limiter session_​commit session_​create_​id session_​decode session_​destroy session_​encode session_​gc session_​get_​cookie_​params session_​id session_​module_​name session_​name session_​regenerate_​id session_​register_​shutdown session_​reset session_​save_​path session_​set_​cookie_​params session_​set_​save_​handler session_​start session_​status session_​unset session_​write_​close Copyright © 2001-2026 The PHP Documentation Group My PHP.net Contact Other PHP.net sites Privacy policy ↑ and ↓ to navigate • Enter to select • Esc to close • / to open Press Enter without selection to search using Google | 2026-01-13T09:30:34 |
https://zh-cn.facebook.com/login/?next=https%3A%2F%2Fl.facebook.com%2Fl.php%3Fu%3Dhttps%253A%252F%252Fwww.instagram.com%252F%26amp%253Bh%3DAT3lN7wpIGgWaTyXErk4SF1WCKEs9PDHJPdbiN3Yl_7Rba5JxYLIit5nb079Cw1WWMDlqJeHCsuW7di_wtBhIrbQwVsBpN2U3fkPKWMYiOrU-c_JuLCa8u7nUnpt80Nm-EprkKK9rPoa2_sw | Facebook Facebook 邮箱或手机号 密码 忘记账户了？ 创建新账户 你暂时被禁止使用此功能 你暂时被禁止使用此功能 似乎你过度使用了此功能，因此暂时被阻止，不能继续使用。 Back 中文(简体) 한국어 English (US) Tiếng Việt Bahasa Indonesia ภาษาไทย Español 日本語 Português (Brasil) Français (France) Deutsch 注册 登录 Messenger Facebook Lite 视频 Meta Pay Meta 商店 Meta Quest Ray-Ban Meta Meta AI Meta AI 更多内容 Instagram Threads 选民信息中心 隐私政策 隐私中心 关于 创建广告 创建公共主页 开发者 招聘信息 Cookie Ad Choices 条款 帮助 联系人上传和非用户 设置 动态记录 Meta © 2026 | 2026-01-13T09:30:34 |
https://llvmweekly.org/issue/560 | LLVM Weekly - #560, September 23rd 2024 LLVM Weekly - #560, September 23rd 2024 Welcome to the five hundred and sixtieth issue of LLVM Weekly, a weekly newsletter (published every Monday) covering developments in LLVM, Clang, and related projects. LLVM Weekly is brought to you by Alex Bradbury . Subscribe to future issues at http://llvmweekly.org and pass it on to anyone else you think may be interested. Please send any tips or feedback to asb@asbradbury.org , @llvmweekly or @asbradbury on Twitter, or @llvmweekly@fosstodon.org or @asb@fosstodon.org . News and articles from around the web and events LLVM 19.1.0 is now released . Congratulations everyone! Andrew Kallai wrote on the LLVM blog about their GSoC project, statistical analysis of LLVM IR compilation . According to the LLVM calendar in the coming week there will be the following: Office hours with the following hosts: Kristof Beyls, Johannes Doerfert, Amara Emerson. Online sync-ups on the following topics: pointer authentication, new contributors, OpenMP, Flang, SPIR-V, RISC-V, LLVM libc, MLIR, MLGO. For more details see the LLVM calendar , getting involved documentation on online sync ups and office hours . On the forums Aaron Ballman proposed Nikita Popov as new lead mantainer of LLVM, with Chis Lattner moving to emeritus lead maintainer for LLVM. The proposal has had resounding support so far. Haojian Wu started a thread detailing current progress and plans in the area of Clang lifetime analysis improvements . J Ryan Stinnett started an RFC thread on a new debug info coverage tool for measauring how well local variables are covered by debug info like DWARF. (As a sidenote, I’m not sure how I missed this one. If you see an RFC that’s likely of broad interest that I overlooked, don’t hesitate to drop me a note!). A follow-up post explains how it compares to existing tools . Utkarsh Saxena proposed introducing [[clang::lifetime_capture_by(x)]] to indicate when a function parameter’s reference is capture by another function parameter or this . The 70th edition of MLIR News is now available . David Spickett started an RFC thread on converting LLVM’s release notes to markdown , which also caused some discussion about improving our methodology for assembling the release notes. Derrick McKee proposed upstreaming of a new compartmentalisation technique that they recently published alongside collaborators recently published . Aaron Ballman attempted to summarise the [tentative consensus on the RFC to embed sources in BMIs](https://discourse.llvm.org/t/rfc-modules-should-we-embed-sources-to-the-bmi/81029/33. Aaron Ballman initiated a discussion on deprecating and eventually removing RenderScript support . LLVM commits LLVM’s developer policy was updated, replacing “code owners” with “maintainers”. c0719d8 . The noext attribute can now be used on call parameters to explicitly indicate that it is neither sign- or zero- extended (i.e. it’s anyext). 1412022 . A scheduling model was added for the AArch64 Neoverse N3. e45f9aa . The InitUndef pass was enabled for non-AMDGPU targets. dfa5429 . Documentation was added on RISC-V GP relaxation and the small data limit option. 76a85b0 . The SLP vectorizer learned to vectorize gathered loads. 1833d41 . A scheduling model was added for the RISC-V Syntacore SCR7. 09fc178 . An initial SPIR-V structurizer was added, which determines the correct merge and continue blocks for SPIR-V. 1ed65fe . Unrolling was implemented as a VPlan-to-VPlan transform. 8ec4067 . Clang commits clang-rename was moved, being superseded by clangd. 40c45b6 . The clang pseudo parser was removed as it is incomplete and unmaintained. ed8f788 . Clang now has a UEFI x86_64 toolchain definition. d1335fb . An -fmodules-embed-all-files option was added. f41f6ea . __builtin_common_type is now provided. f5be5cd . Other project commits LLVM’s libc implemented ctime. 000a3f0 . libcxx’s internal __compressed_pair structure was replaced with [[no_unique_address]] , improving compile times and O0 code-gen. 27c8338 . lldb-dap’s README was improved. 65c5706 . MLIR’s OpenMP (omp) dialect documentation was improved. 0f86cb3 , 8b82fc6 , 551134c , 06e8c6a , 79ec1e7 , and more. A vector to XeGPU conversion pass was added to MLIR. 02d34d8 . Subscribe at LLVMWeekly.org . | 2026-01-13T09:30:34 |
https://id-id.facebook.com/login/?next=https%3A%2F%2Fl.facebook.com%2Fl.php%3Fu%3Dhttps%253A%252F%252Fwww.instagram.com%252F%26amp%253Bh%3DAT1KY84hKm_-by-YRr4vpnWKQpQpwSlqcHtHuJaVKw1bW8wItTohGpLUCnyGOFaKEl24B0RlP8zqhkc8lgjUOBrHeD_3-x2x1wAeaDTMaMg12_UywdHBUwoulr3RtwamghKKTr5Z0_NPtXeL | Facebook Facebook Email atau telepon Kata Sandi Lupa akun? Buat Akun Baru Anda Diblokir Sementara Anda Diblokir Sementara Sepertinya Anda menyalahgunakan fitur ini dengan menggunakannya terlalu cepat. Anda dilarang menggunakan fitur ini untuk sementara. Back Bahasa Indonesia 한국어 English (US) Tiếng Việt ภาษาไทย Español 中文(简体) 日本語 Português (Brasil) Français (France) Deutsch Daftar Masuk Messenger Facebook Lite Video Meta Pay Meta Store Meta Quest Ray-Ban Meta Meta AI Konten Meta AI lainnya Instagram Threads Pusat Informasi Pemilu Kebijakan Privasi Pusat Privasi Tentang Buat Iklan Buat Halaman Developer Karier Cookie Pilihan Iklan Ketentuan Bantuan Pengunggahan Kontak & Non-Pengguna Pengaturan Log aktivitas Meta © 2026 | 2026-01-13T09:30:34 |
https://llvmweekly.org/issue/564 | LLVM Weekly - #564, October 21st 2024 LLVM Weekly - #564, October 21st 2024 Welcome to the five hundred and sixty-fourth issue of LLVM Weekly, a weekly newsletter (published every Monday) covering developments in LLVM, Clang, and related projects. LLVM Weekly is brought to you by Alex Bradbury . Subscribe to future issues at http://llvmweekly.org and pass it on to anyone else you think may be interested. Please send any tips or feedback to asb@asbradbury.org , @llvmweekly or @asbradbury on Twitter, or @llvmweekly@fosstodon.org or @asb@fosstodon.org . News and articles from around the web and events LLVM 19.1.2 was released . Shafik Yaghmour authored a blog post about triaging clang C++ frontend bugs . Shourya Goel wrote on the LLVM project blog about their GSoC project ‘ the 1001 thresholds in LLVM ’. Alex Bradbury wrote for the RISE project blog on recent (and ongoing) work at Igalia on RISC-V LLVM continuous integration . See the LLVM calendar as usual for upcoming office hours and sync-ups. I’m not going to list them this week as I think it’s quite likely many of these will end up cancelled due to the LLVM developers meeting this week. On the forums Nikita Popov proposed guidelines for fuzzer-generated issues . Louis Dionne shared a PSA that LLVM 19.1.2 removes some libc++abi re-exported symbols on Apple platforms . Sjoerd Meijer started a discussion on enabling loop interchange in LLVM . Reid Kleckner provided an updated on the LLVM project governance proposal , providing meeting notes from the review managers meeting. Tom Stellard provided shared notes from a further meeting that approved the proposal with some changes. Nikita Popov shared thoughts on sinking in LLVM . Sjoerd Meijer is seeking input on LLVM test suite improvements Sebastian Perta kicked off an RFC thread on changes needed to libcxx for 16 bit architectures like RL78 . Martin Storsjö proposes adding ffmpeg to LLVM’s test suite . Alex Voicu posted a proposal on changing the SPIR-V backend’s address space mappings . LLVM commits Initial support for interleaved loads was added to the SLP vectoriser. f9bc00e . Documentation was added on how to get permissions to manage a buildbot worker from the web interface. 57cd6d8 . Initial support for code coverage in WebAssembly/WASI was added. d4efc3e . icmp now has a samesign flag. 9efb07f , 095d49d . AArch64 feature definitions were added for the new extensions introduced in Armv9.6. b584478 . The requirement that commits have a public email address was documented. bf1a554 . New inline assembly constraints were added for RISC-V, intended to be helpful for use alongside .insn . 228f88f . Clang commits User-documentation was added for -Wunsafe-buffer-usage . 5000c68 . A RemoveEmptyLinesInUnwrappedLines option was added to clang-format. d989c24 . clangd can now provide inlay hints for default function arguments. 2eb1699 . Other project commits Flang’s pointer component logic in its AliasAnalysis implementation was replaced. 7323533 . Infrastructure was added to start complex.h support in LLVM’s libc. f4ba6a6 . The JSON symbol file format that LLDB supports was documented. 7437f3e . The conversion of privatisation for omp.parallel in MLIR was rewritten. 621fcf8 . Subscribe at LLVMWeekly.org . | 2026-01-13T09:30:34 |
https://logging.apache.org/log4j/2.x/download.html#sbom | Download :: Apache Log4j a subproject of Apache Logging Services Home Download Release notes Support Versioning and maintenance policy Security Manual Getting started Installation API Loggers Event Logger Simple Logger Status Logger Fluent API Fish tagging Levels Markers Thread Context Messages Flow Tracing Implementation Architecture Configuration Configuration file Configuration properties Programmatic configuration Appenders File appenders Rolling file appenders Database appenders Network Appenders Message queue appenders Delegating Appenders Layouts JSON Template Layout Pattern Layout Lookups Filters Scripts JMX Extending Plugins Performance Asynchronous loggers Garbage-free logging References Plugin reference Java API reference Resources F.A.Q. Migrating from Log4j 1 Migrating from Logback Migrating from SLF4J Building GraalVM native images Integrating with Hibernate Integrating with Jakarta EE Integrating with service-oriented architectures Development Components Log4j IOStreams Log4j Spring Boot Support Log4j Spring Cloud Configuration JUL-to-Log4j bridge Log4j-to-JUL bridge Related projects Log4j Jakarta EE Log4j JMX GUI Log4j Kotlin Log4j Scala Log4j Tools Log4j Transformation Tools Home Download Edit this Page Download You can manually download all published Log4j distributions, verify them, and see their licensing information by following the instructions in the Download page of Logging Services . Are you looking for the Log4j installation instructions ? Proceed to Installation . Are you looking for the list of changes associated with a particular release? Proceed to Release notes . Source distribution You can download the source code of the latest Log4j release using the links below: Table 1. Source distribution files Sources apache-log4j-2.25.3-src.zip Checksum apache-log4j-2.25.3-src.zip.sha512 Signature apache-log4j-2.25.3-src.zip.asc Signing keys KEYS Binary distribution A set of binaries of Log4j is available through two main distribution channels: ASF Nexus Repository All the binary artifacts are available on the Apache Software Foundation repository.apache.org Nexus repository . Its content is mirrored to the Maven Central repository . See Components for more information on the GAV coordinates of the artifacts. Binary distribution archive All the artifacts in the ASF Nexus repository are also available in a single ZIP archive: Table 2. Binary distribution files Binaries apache-log4j-2.25.3-bin.zip Checksum apache-log4j-2.25.3-bin.zip.sha512 Signature apache-log4j-2.25.3-bin.zip.asc Signing keys KEYS The authenticity of the Log4j binary release is independently verified by the Reproducible Builds for Maven Central Repository project. You can check the reproducibility status of the artifacts on their org.apache.logging.log4j:log4j RB check page. Software Bill of Materials (SBOM) Each Log4j artifact is accompanied by a Software Bill of Materials (SBOM). See the Download page of Logging Services page for details. Available versions Below you can find the list of available Log4j versions and their associated maintenance status; Active Development, Active Maintenance, End-of-Maintenance, and End-of-Life. Refer to Versioning and maintenance policy for details. Table 3. Maintenance status of selected Log4j versions Version Status Latest release First stable release EOM EOL Notes 3.0.x AD 3.0.0-beta3 2.26.x AD 2.25.x AM 2.25.3 2025-12-15 2.24.x EOM 2.24.3 2024-09-03 2025-06-13 2.12.x EOM 2.12.4 2019-06-23 2021-12-29 Last release supporting Java 7 2.3.x EOM 2.3.2 2015-05-09 2021-12-29 Last release supporting Java 6 1.x EOL 1.2.17 2000-01-08 2014-07-12 2015-08-05 Last release supporting Java 1.4 Click to see all past versions Table 4. Maintenance status of all Log4j versions Version Status Latest release First release EOM EOL 3.0.x AD 3.0.0-beta3 2.26.x AD 2.25.x AM 2.25.2 2025-06-13 2.24.x EOM 2.24.3 2024-09-03 2025-06-13 2.23.x EOM 2.23.1 2024-02-17 2024-09-03 2.22.x EOM 2.22.1 2023-11-17 2024-02-17 2.21.x EOM 2.21.1 2023-10-12 2023-11-17 2.20.x EOM 2.20.0 2023-02-17 2023-10-12 2.19.x EOM 2.19.0 2022-09-09 2023-02-17 2.18.x EOM 2.18.0 2022-06-28 2022-09-09 2.17.x EOM 2.17.2 2021-12-17 2022-06-28 2.16.x EOM 2.16.0 2021-12-13 2021-12-17 2.15.x EOM 2.15.0 2021-12-06 2021-12-13 2.14.x EOM 2.14.1 2020-11-06 2021-12-06 2.13.x EOM 2.13.3 2019-12-11 2020-11-06 2.12.x EOM 2.12.4 2019-06-23 2021-12-29 2.11.x EOM 2.11.2 2018-03-11 2019-06-23 2.10.x EOM 2.10.0 2017-11-18 2018-03-11 2.9.x EOM 2.9.1 2017-08-26 2017-11-18 2.8.x EOM 2.8.2 2017-01-21 2017-08-26 2.7.x EOM 2.7 2016-10-02 2017-01-21 2.6.x EOM 2.6.2 2016-05-25 2016-10-02 2.5.x EOM 2.5 2015-12-06 2016-05-25 2.4.x EOM 2.4.1 2015-09-20 2015-12-06 2.3.x EOM 2.3.2 2015-05-09 2021-12-29 2.2.x EOM 2.2 2015-02-22 2015-05-09 2.1.x EOM 2.1 2014-10-19 2015-02-22 2.0.x EOM 2.0.2 2014-07-12 2014-10-19 1.x EOL 1.2.17 2000-01-08 2014-07-12 2015-08-05 Copyright © 1999-2025 The Apache Software Foundation . Licensed under the Apache Software License, Version 2.0 . Please read our privacy policy . Apache, Log4j, and the Apache feather logo are trademarks or registered trademarks of The Apache Software Foundation. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. | 2026-01-13T09:30:34 |
https://docs.aws.amazon.com/de_de/AmazonCloudFront/latest/DeveloperGuide/lambda-edge-permissions.html | Einrichten von IAM-Berechtigungen und -Rollen für Lambda@Edge - Amazon CloudFront Einrichten von IAM-Berechtigungen und -Rollen für Lambda@Edge - Amazon CloudFront Dokumentation Amazon CloudFront Entwicklerhandbuch IAM-Berechtigungen sind erforderlich, um Lambda @Edge -Funktionen mit Distributionen zu verknüpfen CloudFront Funktionsausführungsrolle für Service-Prinzipale Serviceverknüpfte Rollen für Lambda@Edge Die vorliegende Übersetzung wurde maschinell erstellt. Im Falle eines Konflikts oder eines Widerspruchs zwischen dieser übersetzten Fassung und der englischen Fassung (einschließlich infolge von Verzögerungen bei der Übersetzung) ist die englische Fassung maßgeblich. Einrichten von IAM-Berechtigungen und -Rollen für Lambda@Edge Um Lambda@Edge zu konfigurieren, benötigen Sie die folgenden IAM-Berechtigungen und -Rollen für AWS Lambda: IAM-Berechtigungen — Mit diesen Berechtigungen können Sie Ihre Lambda-Funktion erstellen und sie Ihrer CloudFront Distribution zuordnen. Eine Ausführungsrolle für die Lambda-Funktion (IAM-Rolle) – Die Lambda-Service-Prinzipale übernehmen diese Rolle, um die Funktion auszuführen. Dienstgebundene Rollen für Lambda @Edge — Die dienstverknüpften Rollen ermöglichen es bestimmten, Lambda-Funktionen in Protokolldateien AWS-Services zu replizieren AWS-Regionen und deren Verwendung zu ermöglichen CloudWatch. CloudFront IAM-Berechtigungen sind erforderlich, um Lambda @Edge -Funktionen mit Distributionen zu verknüpfen CloudFront Zusätzlich zu den IAM-Berechtigungen, die Sie für Lambda benötigen, benötigen Sie die folgenden Berechtigungen, um Lambda-Funktionen Distributionen zuzuordnen: CloudFront lambda:GetFunction – Gewährt die Berechtigung, Konfigurationsinformationen für die Lambda-Funktion und eine vorsignierte URL zum Herunterladen einer .zip -Datei abzurufen, die die Funktion enthält. lambda:EnableReplication* – Gewährt die Berechtigung für die Ressourcenrichtlinie, sodass der Lambda-Replikationsservice den Code und die Konfiguration der Funktion abrufen kann. lambda:DisableReplication* – Gewährt die Berechtigung für die Ressourcenrichtlinie, sodass der Lambda-Replikationsservice die Funktion löschen kann. Wichtig Sie müssen das Sternchen ( * ) am Ende der Aktionen lambda:EnableReplication * und lambda:DisableReplication * hinzufügen. Geben Sie für die Ressource den ARN der Funktionsversion an, die Sie ausführen möchten, wenn ein CloudFront Ereignis eintritt, wie im folgenden Beispiel: arn:aws:lambda:us-east-1:123456789012:function: TestFunction :2 iam:CreateServiceLinkedRole — Erteilt die Erlaubnis, eine serviceverknüpfte Rolle zu erstellen, in der Lambda @Edge Lambda-Funktionen repliziert. CloudFront Nachdem Sie Lambda@Edge zum ersten Mal konfiguriert haben, wird die serviceverknüpfte Rolle automatisch für Sie erstellt. Sie müssen diese Berechtigung nicht zu anderen Distributionen hinzufügen, die Lambda@Edge verwenden. cloudfront:UpdateDistribution oder cloudfront:CreateDistribution – Gewährt die Berechtigung, eine Distribution zu aktualisieren oder zu erstellen. Weitere Informationen finden Sie unter den folgenden Themen: Identity and Access Management für Amazon CloudFront Zugriffsberechtigungen für Lambda-Ressourcen im Entwicklerhandbuch für AWS Lambda Funktionsausführungsrolle für Service-Prinzipale Sie müssen eine IAM-Rolle erstellen, die die Service-Prinzipale lambda.amazonaws.com und edgelambda.amazonaws.com übernehmen können, wenn sie Ihre Funktion ausführen. Tipp Wenn Sie Ihre Funktion in der Lambda-Konsole erstellen, können Sie wählen, ob Sie mithilfe einer AWS Richtlinienvorlage eine neue Ausführungsrolle erstellen möchten. Dieser Schritt fügt automatisch die erforderlichen Lambda@Edge-Berechtigungen hinzu, um Ihre Funktion auszuführen. Siehe Schritt 5 im Tutorial: Erstellen einer einfachen Lambda@Edge-Funktion . Weitere Informationen zum manuellen Erstellen einer IAM-Rolle finden Sie unter Erstellen von Rollen und Anfügen von Richtlinien (Konsole) im IAM-Benutzerhandbuch . Beispiel: Rollenvertrauensrichtlinie Diese Rolle können Sie unter der Registerkarte Vertrauensstellung in der IAM-Konsole hinzufügen. Fügen Sie diese Richtlinie nicht unter der Registerkarte Berechtigungen hinzu. JSON { "Version":"2012-10-17", "Statement": [ { "Effect": "Allow", "Principal": { "Service": [ "lambda.amazonaws.com", "edgelambda.amazonaws.com" ] }, "Action": "sts:AssumeRole" } ] } Weitere Informationen zu den Berechtigungen, die Sie der Ausführungsrolle erteilen müssen, finden Sie unter Zugriffsberechtigungen für Lambda-Ressourcen im Entwicklerhandbuch für AWS Lambda . Hinweise Standardmäßig werden Daten in CloudWatch Logs geschrieben, wenn ein CloudFront Ereignis eine Lambda-Funktion auslöst. Wenn Sie diese Protokolle verwenden möchten, benötigt die Ausführungsrolle die Berechtigung, Daten in CloudWatch Logs zu schreiben. Sie können die vordefinierte AWSLambdaBasicExecutionRole verwenden, um der Ausführungsrolle die Berechtigung zu erteilen. Weitere Hinweise zu CloudWatch Protokollen finden Sie unter Protokolle für Edge-Funktionen . Wenn Ihr Lambda-Funktionscode auf andere AWS Ressourcen zugreift, z. B. auf das Lesen eines Objekts aus einem S3-Bucket, benötigt die Ausführungsrolle die Erlaubnis, diese Aktion auszuführen. Serviceverknüpfte Rollen für Lambda@Edge Lambda@Edge verwendet serviceverknüpfte IAM-Rollen . Eine serviceverknüpfte Rolle ist ein spezieller Typ von IAM-Rolle, der direkt mit einem Service verknüpft ist. Serviceverknüpfte Rollen werden vom Service vorab definiert und beinhalten alle Berechtigungen, die dieser zum Aufrufen anderer AWS -Services in Ihrem Namen benötigt. Lambda@Edge verwendet die folgenden serviceverknüpften IAM-Rollen: AWSServiceRoleForLambdaReplicator – Lambda@Edge verwendet diese Rolle, um es Lambda@Edge zu ermöglichen, Funktionen in AWS-Regionen zu replizieren. Wenn Sie zum ersten Mal einen Lambda @Edge -Trigger hinzufügen CloudFront, AWSServiceRoleForLambdaReplicator wird automatisch eine Rolle mit dem Namen erstellt, damit Lambda @Edge Funktionen replizieren kann. AWS-Regionen Diese Rolle ist für die Verwendung von Lambda@Edge-Funktionen erforderlich. Die ARN für die Rolle AWSServiceRoleForLambdaReplicator sieht wie im folgenden Beispiel aus: arn:aws:iam::123456789012:role/aws-service-role/replicator.lambda.amazonaws.com/AWSServiceRoleForLambdaReplicator AWSServiceRoleForCloudFrontLogger — CloudFront verwendet diese Rolle, um Protokolldateien in die Datei zu übertragen. CloudWatch Sie können Protokolldateien verwenden, um Lambda@Edge-Validierungsfehler zu beheben. Die AWSServiceRoleForCloudFrontLogger Rolle wird automatisch erstellt, wenn Sie eine Lambda @Edge -Funktionsassoziation hinzufügen, an die Lambda @Edge -Fehlerprotokolldateien übertragen werden können CloudFront . CloudWatch Der ARN für die AWSServiceRoleForCloudFrontLogger-Rolle sieht so aus: arn:aws:iam::account_number:role/aws-service-role/logger.cloudfront.amazonaws.com/AWSServiceRoleForCloudFrontLogger Eine serviceverknüpfte Rolle vereinfacht das Einrichten und Verwenden von Lambda@Edge, da Sie die erforderlichen Berechtigungen nicht manuell hinzufügen müssen. Lambda@Edge definiert die Berechtigungen seiner servicegebundenen Rollen. Nur Lambda@Edge kann die Rollen übernehmen. Die definierten Berechtigungen umfassen die Vertrauens- und Berechtigungsrichtlinie. Sie können die Berechtigungsrichtlinie keiner anderen IAM-Entität zuordnen. Sie müssen alle zugehörigen Ressourcen CloudFront oder Lambda @Edge -Ressourcen entfernen, bevor Sie eine serviceverknüpfte Rolle löschen können. Dies trägt zum Schutz Ihrer Lambda@Edge-Ressourcen bei, sodass Sie keine serviceverknüpfte Rolle entfernen, die noch für den Zugriff auf aktive Ressourcen erforderlich ist. Weitere Informationen zu serviceverknüpften Rollen finden Sie unter Dienstbezogene Rollen für CloudFront . Serviceverknüpfte Rollenberechtigungen für Lambda@Edge Lambda@Edge verwendet zwei servicegebundene Rollen. Diese heißen AWSServiceRoleForLambdaReplicator und AWSServiceRoleForCloudFrontLogger . In den folgenden Abschnitten werden die Berechtigungen für jede dieser Rollen beschrieben. Inhalt Serviceverknüpfte Rollenberechtigungen für Lambda Replicator Berechtigungen für dienstverknüpfte Rollen für den Logger CloudFront Serviceverknüpfte Rollenberechtigungen für Lambda Replicator Diese serviceverknüpfte Rolle ermöglicht Lambda das Replizieren von Lambda@Edge-Funktionen zu AWS-Regionen. Die serviceverknüpfte Rolle AWSServiceRoleForLambdaReplicator vertraut dem Service replicator.lambda.amazonaws.com , sodass dieser die Rolle annehmen kann. Die Rollenberechtigungsrichtlinie erlaubt Lambda@Edge die Durchführung der folgenden Aktionen für die angegebenen Ressourcen: lambda:CreateFunction auf arn:aws:lambda:*:*:function:* lambda:DeleteFunction auf arn:aws:lambda:*:*:function:* lambda:DisableReplication auf arn:aws:lambda:*:*:function:* iam:PassRole auf all AWS resources cloudfront:ListDistributionsByLambdaFunction auf all AWS resources Berechtigungen für dienstverknüpfte Rollen für den Logger CloudFront Diese dienstbezogene Rolle ermöglicht das CloudFront Pushen von Protokolldateien, CloudWatch sodass Sie Lambda @Edge -Validierungsfehler debuggen können. Die serviceverknüpfte Rolle AWSServiceRoleForCloudFrontLogger vertraut dem Service logger.cloudfront.amazonaws.com , sodass dieser die Rolle annehmen kann. Die Rollenberechtigungsrichtlinie erlaubt Lambda@Edge die Durchführung der folgenden Aktionen für die angegebene arn:aws:logs:*:*:log-group:/aws/cloudfront/* -Ressource: logs:CreateLogGroup logs:CreateLogStream logs:PutLogEvents Sie müssen Berechtigungen konfigurieren, damit eine IAM-Entität (z. B. ein Benutzer, eine Gruppe oder eine Rolle) die mit dem Lambda@Edge-Service verknüpften Rollen löschen kann. Weitere Informationen finden Sie unter serviceverknüpfte Rollenberechtigung im IAM-Benutzerhandbuch . Serviceverknüpfte Rollen für Lambda@Edge erstellen Servicegebundene Rollen für Lambda@Edge werden in der Regel nicht manuell erstellt. In den folgenden Szenarien legt der Service die Rollen für Sie automatisch an: Wenn Sie zum ersten Mal einen Auslöser erstellen, erstellt der Service die Rolle AWSServiceRoleForLambdaReplicator (sofern sie nicht bereits vorhanden ist). Diese Rolle ermöglicht Lambda das Replizieren von Lambda@Edge-Funktionen in AWS-Regionen. Wenn Sie die serviceverknüpfte Rolle löschen, wird die Rolle erneut erstellt, wenn Sie einen neuen Auslöser für Lambda@Edge in einer Verteilung hinzufügen. Wenn Sie eine CloudFront Distribution aktualisieren oder erstellen, die über eine Lambda @Edge -Zuordnung verfügt, erstellt der Dienst die AWSServiceRoleForCloudFrontLogger Rolle (sofern die Rolle noch nicht vorhanden ist). Diese Rolle ermöglicht es CloudFront , Ihre Protokolldateien per Push zu CloudWatch übertragen. Wenn Sie die dienstverknüpfte Rolle löschen, wird die Rolle erneut erstellt, wenn Sie eine CloudFront Distribution aktualisieren oder erstellen, die über eine Lambda @Edge -Zuordnung verfügt. Um diese dienstbezogenen Rollen manuell zu erstellen, können Sie die folgenden Befehle AWS Command Line Interface ()AWS CLI ausführen: So erstellen Sie die AWSServiceRoleForLambdaReplicator-Rolle Führen Sie den folgenden Befehl aus. aws iam create-service-linked-role --aws-service-name replicator.lambda.amazonaws.com So erstellen Sie die AWSServiceRoleForCloudFrontLogger-Rolle Führen Sie den folgenden Befehl aus. aws iam create-service-linked-role --aws-service-name logger.cloudfront.amazonaws.com Bearbeiten von serviceverknüpften Lambda@Edge-Rollen Lambda@Edge verhindert die Bearbeitung der serviceverknüpften Rollen AWSServiceRoleForLambdaReplicator und AWSServiceRoleForCloudFrontLogger. Da möglicherweise verschiedene Entitäten auf die Rolle verweisen, kann der Rollenname nach der Erstellung einer serviceverknüpften Rolle durch den Service nicht bearbeitet werden. Sie können mithilfe von IAM jedoch die Beschreibung der Rolle bearbeiten. Weitere Informationen finden Sie unter Bearbeiten einer serviceverknüpften Rolle im IAM-Benutzerhandbuch . Unterstützt AWS-Regionen für dienstverknüpfte Lambda @Edge -Rollen CloudFront unterstützt die Verwendung von dienstverknüpften Rollen für Lambda @Edge im Folgenden: AWS-Regionen USA Ost (Nord-Virginia) – us-east-1 USA Ost (Ohio) – us-east-2 USA West (Nordkalifornien) – us-west-1 USA West (Oregon) – us-west-2 Asia Pacific (Mumbai) – ap-south-1 Asien-Pazifik (Seoul) – ap-northeast-2 Asia Pacific (Singapore) – ap-southeast-1 Asien-Pazifik (Sydney) – ap-southeast-2 Asien-Pazifik (Tokio) – ap-northeast-1 Europa (Frankfurt) – eu-central-1 Europa (Ireland) – eu-west-1 Europa (London) – eu-west-2 South America (São Paulo) – sa-east-1 JavaScript ist in Ihrem Browser nicht verfügbar oder deaktiviert. Zur Nutzung der AWS-Dokumentation muss JavaScript aktiviert sein. Weitere Informationen finden auf den Hilfe-Seiten Ihres Browsers. Dokumentkonventionen Tutorial: Grundlegende Lambda@Edge-Funktion Schreiben und Erstellen einer Lambda@Edge-Funktion Hat Ihnen diese Seite geholfen? – Ja Vielen Dank, dass Sie uns mitgeteilt haben, dass wir gute Arbeit geleistet haben! Würden Sie sich einen Moment Zeit nehmen, um uns mitzuteilen, was wir richtig gemacht haben, damit wir noch besser werden? Hat Ihnen diese Seite geholfen? – Nein Vielen Dank, dass Sie uns mitgeteilt haben, dass diese Seite überarbeitet werden muss. Es tut uns Leid, dass wir Ihnen nicht weiterhelfen konnten. Würden Sie sich einen Moment Zeit nehmen, um uns mitzuteilen, wie wir die Dokumentation verbessern können? | 2026-01-13T09:30:34 |
https://llvmweekly.org/issue/558 | LLVM Weekly - #558, September 9th 2024 LLVM Weekly - #558, September 9th 2024 Welcome to the five hundred and fifty-eighth issue of LLVM Weekly, a weekly newsletter (published every Monday) covering developments in LLVM, Clang, and related projects. LLVM Weekly is brought to you by Alex Bradbury . Subscribe to future issues at http://llvmweekly.org and pass it on to anyone else you think may be interested. Please send any tips or feedback to asb@asbradbury.org , @llvmweekly or @asbradbury on Twitter, or @llvmweekly@fosstodon.org or @asb@fosstodon.org . News and articles from around the web and events The 2024 LLVM Developers' Meeting program has been released . LLVM 19.1.0-rc4 was released , and 19.1.0-final is planned for 17th September. A number of blog posts about LLVM GSoC projects are now available: GPU libc benchmarking , half-precision in LLVM libc , and compiling GPU kernels using ClangIR . According to the LLVM calendar in the coming week there will be the following: Office hours with the following hosts: Alexey Bader, Aaron Ballman, Alina Sbirlea, Kristof Beyls, Johannes Doerfert, Online sync-ups on the following topics: MLIR C/C++ frontend, alias analysis, pointer authentication, SPIR-V, new contributors, OpenMP, Flang, BOLT, RISC-V, MLIR, embedded toolchains, MLGO. For more details see the LLVM calendar , getting involved documentation on online sync ups and office hours . On the forums Marc Auberer started a discussion on making DenseMap and DenseSet robust against out of memory situations (motivated by an in-memory database use case where crashes may lead to data loss). Reid Kleckner provided an update on the AI tool usage in contributions RFC . Tyler Nowicki posted an RFC on introducing ABI objects for coroutines . Victor Campos proposed an extension of multilib to support selection of library variants that don’t correspond to command-line options . Rahul Joshi shared a PSA on planned changes to TableGen getAllDerivedDefinitions . The LLVM Foundation is hiring a Program Director . “Yshaneh” asked about adding vararg support for a custom backend and received a range of answers. LLVM commits BasicAA learned to track the nuw flag through decomposed expressions. b9bba6c . spirv-sim, a minimal SPIR-V simulator in Python was added for testing purposes. 5914566 . Support was added for AVX10.2-BF16 X86 instructions. 83ad644 . The initialisation performance of APInt was improved. 427e202 . -verify-each was added to llc . 69657eb . With the -emit-jump-table-sizes-section option, LLVM will emit a .llvm_jump_table_sizes section in the output binary containing jump table addresses and entry counts. This may be used by tools that statically reconstruct the control flow of executables. fb6c10d . usub_{cond,sat} operations were added to atomicrmw . 4af249f . Clang commits multilib.yaml now allows you to map a particular multilib to an informative error message. 26bf0b4 . BPF now defaults to the “v3” CPU target. 7852ebc . Other project commits LLVM’s libc bcmp was optimised. 66a03295 . An --icf=safe_thunks mode was added for identical code folding in LLD MachO for Arm64. d175616 . LLDB learned to handle optionally enabled/disabled floating point registers for riscv64. 660e34f . Subscribe at LLVMWeekly.org . | 2026-01-13T09:30:34 |
https://llvmweekly.org/issue/602 | LLVM Weekly - #602, July 14th 2025 LLVM Weekly - #602, July 14th 2025 Welcome to the six hundred and second issue of LLVM Weekly, a weekly newsletter (published every Monday) covering developments in LLVM, Clang, and related projects. LLVM Weekly is brought to you by Alex Bradbury . Subscribe to future issues at https://llvmweekly.org and pass it on to anyone else you think may be interested. Please send any tips or feedback via email: asb@asbradbury.org , or Mastodon: @llvmweekly@fosstodon.org / @asb@fosstodon.org , or Bluesky: @llvmweekly.org / @asbradbury.org . News and articles from around the web and events The deadline for talk submissions and for student travel grant applications for the 2025 US LLVM Developers' Meeting is rapidly approaching . July 15th is the final day. Registration will be opening next week . The next LLVM Bay Area meetup will take place on Monday 21st July . According to the LLVM Calendar in the coming week there will be the following: Office hours with the following hosts: Aaron Ballman, Alexey Bader, Phoebe Wang, Johannes Doerfert. Online sync-ups on the following topics: ClangIR upstreaming, pointer authentication, vectorisation, security response group, OpenMP, Clang C/C++ language working group, Flang, RISC-V, embedded toolchains, HLSL. For more details see the LLVM calendar , getting involved documentation on online sync ups and office hours . On the forums Utkarsh Saxena announced the formation of the Lifetime Safety Breakout Group , forking off from the Memory Safety Working Group. Renato Golin initiated an MLIR discussion on following through on the plan to deprecate the matmul transpose linalg operations . There’s been further debate on the proposal to move towards disallowing struct/array IR values, with some commenters concerned that although they’re less helpful for IR for codegen, there are other LLVM IR use cases that may benefit from them. Jeremy Morse provided an update on debug info improvements via key instructions . LLVM 20.1.8 was released . This is the last planned 20.1.x release. Volodymyr Turanskyy proposed adding a Clang command line option for selecting the C library to use . Michael Jones started an RFC discussion on cleaning up how Linux syscalls are handled within LLVM’s libc implementation . Mingming Liu made an RFC proposal for extending the SamplePGO profile format to include vtable type information , enabling vtable-based indirect call promotion for SampleFDO. LLVM commits A minimal DWARF unwinding information checker was committed. db03408 . Initial slide links and documentation updates were made after the first Qualification Group meeting. 63f19f1 . Definitions (and -mcpu= ) support were added for the Nvidia GB10 (cluster of CortexX925 and Xortex-A725 cores). 84e5451 . As part of refactoring how libcall definitions are managed, you can now define in TableGen a SystemLibrary for a complete set of libcalls subdivided by a predicate based on the triple. TableGen can also be used to set the libcall calling conventions. 5088231 , 58ad996 , b116ee4 . A generic expansion of ISD::FCANONICALIZE was implemented. acdf1c7 . A new command line flag was added to control the estimated cost of a single inline asm IR instruction when inlining. Note that a single “call asm” IR instruction may contain multiple target assembly instructions. cd9236d . Saturated truncate instructions were added to GlobalISel. 4c27279 . The MachinePipeliner now has logic to validate that the generated schedule doesn’t violate loop-carried memory dependencies. c0b82df . MC layer definitions were added for Sparc cryptographic instructions. d86c63d . Clang commits An initial intra-procedural flow-sensitive lifetime analysis was implemented in Clang, as previously proposed by RFC . 3076794 . Clang’s diagnostics were updated to print fully qualified attribute names including scope. e.g. gnu::packed rather than packed . 2e8e254 . New clang-tidy checks were added: llvm-prefer-static-over-anonymous-namespace and readability-use-concise-preprocessor-directives. 2f4a804 , 59b39c0 . clang-tidy is now “eating its own dogfood” and the clang-tidy/ directory in the monorepo features a .clang-tidy file enabling a range of checks. d7a1754 . Other project commits flang gained an -fcomplex-arithmetic= option to select the algorithm used for complex division. c990001 . Various fuzz tests were added to LLVM’s libc. 81614e5 , a9d8843 , 425ed22 . libcxxabi and libunwind can now be used with LLVM’s libc. 9d3b60d . Various MSVC type summaries and formatters were added to LLDB. def7bbb , 45689b2 . Canonical loop operations were added to the OpenMP MLIR dialect. 628c735 , 96bc07d . The convert-xevm-to-llvm pass was introduced to MLIR. 0a34309 . Subscribe at LLVMWeekly.org . | 2026-01-13T09:30:34 |
https://es-la.facebook.com/login/?next=https%3A%2F%2Fl.facebook.com%2Fl.php%3Fu%3Dhttps%253A%252F%252Fwww.instagram.com%252F%26amp%253Bh%3DAT2keGOX2gxggubPvbD2U4v7iuDC9S3X2Lk7QEf_zG6UCPFlqRgkB8gDW-EZJfw1fiHskSqvBHeZQITabHORPi6bmhZQB9HgmigfedLFjaYt-gvk5RTqrih_kcyIODnVVuMY0a6Vs1-agSJ_ | Facebook Facebook Correo o teléfono Contraseña ¿Olvidaste tu cuenta? Crear cuenta nueva Se te bloqueó temporalmente Se te bloqueó temporalmente Parece que hiciste un uso indebido de esta función al ir muy rápido. Se te bloqueó su uso temporalmente. Back Español 한국어 English (US) Tiếng Việt Bahasa Indonesia ภาษาไทย 中文(简体) 日本語 Português (Brasil) Français (France) Deutsch Registrarte Iniciar sesión Messenger Facebook Lite Video Meta Pay Tienda de Meta Meta Quest Ray-Ban Meta Meta AI Más contenido de Meta AI Instagram Threads Centro de información de votación Política de privacidad Centro de privacidad Información Crear anuncio Crear página Desarrolladores Empleo Cookies Opciones de anuncios Condiciones Ayuda Importación de contactos y no usuarios Configuración Registro de actividad Meta © 2026 | 2026-01-13T09:30:34 |
https://llvmweekly.org/issue/559 | LLVM Weekly - #559, September 16th 2024 LLVM Weekly - #559, September 16th 2024 Welcome to the five hundred and fifty-ninth issue of LLVM Weekly, a weekly newsletter (published every Monday) covering developments in LLVM, Clang, and related projects. LLVM Weekly is brought to you by Alex Bradbury . Subscribe to future issues at http://llvmweekly.org and pass it on to anyone else you think may be interested. Please send any tips or feedback to asb@asbradbury.org , @llvmweekly or @asbradbury on Twitter, or @llvmweekly@fosstodon.org or @asb@fosstodon.org . News and articles from around the web and events Manuel Brito wrote on the LLVM blog about their GSoC project to improve the NewGVN pass . The next Portland LLVM social is taking place on September 26th . The 2024 LLVM Developers’ Meeting Embedded Toolchains Workshop is confirmed for October 22nd and will be an unconference. According to the LLVM calendar in the coming week there will be the following: Office hours with the following hosts: Phoebe Wang, Johannes Doerfert, Aaron Ballman. Online sync-ups on the following topics: Flang, vectorizer, security group, new contributors, LLVM/offload, classic flang, C/C++ language working, floating point, OpenMP for flang, MLIR. For more details see the LLVM calendar , getting involved documentation on online sync ups and office hours . On the forums Nathan Gauër posted an RFC on testing the SPIR-V backend using spirv-sim . Stella Laurenzo shares that MLIR no longer builds the pytorch native interface . Alexander Belyaev started an RFC thread on vectors of complx type in MLIR . MDevereau proposed using libm’s logf128 for constant folding . Respondents suggested using an implementation from LLVM’s libc. LLVM commits An API was exposed to initialise the SPIRV target and translate the input LLVM IR module to SPIR-V. bca2b6d . RISC-V large code model is now supported. fef84c5 . Improvements to rematerialisation of vmv.v.i for RISC-V reduce the number of spills in SPEC CPU 2017 by 2.5%. 65dc53b . The llvm.set.rounding intrinsic was implemented for PowerPC. 06c3311 . Functions can now be outlined across modules using data generated from a previous codegen. 0f525452 . A section on AI-generated content was added to the developer policy. 829ea59 . Assembly (MC layer) support was added for the final WebAssembly exception handling proposal. 6bbf7f0 . Support was implemented for the new X86 AVX10.2-SATCVT-DS instructions. a409ebc . Basic skeleton enablement was added for AMD Zen5. 02e4186 . Clang commits The clang-format Visual Studio plugin code was deleted, as Visual Studio has built-in support for running clang-format since VS2017. ddd2af3 . Documentation was added to RTSan on how to disable it. 60efbe9 . diagnose_if was extended to accept more detailed warning information. e7f782e . The target_clones attribute used for function multiversioning is now supported for RISC-V. 9cd9377 . A new update-verify-tests.py tool was added, which takes output from a failed clang -verify test and updates it. 9ceb967 . Other project commits vdso was implemented in LLVM’s libc. d8e124d . LLDB can now calculate the average and the total time for summary providers. 22144e2 . MLIR dialect conversion now handles dropped block arguments and drop operation results in the same way. 6093c26 . A --tosa-reduce-transposes pass was added to MLIR. 00f239e4 . Subscribe at LLVMWeekly.org . | 2026-01-13T09:30:34 |
https://llvmweekly.org/issue/557 | LLVM Weekly - #557, September 2nd 2024 LLVM Weekly - #557, September 2nd 2024 Welcome to the five hundred and fifty-seventh issue of LLVM Weekly, a weekly newsletter (published every Monday) covering developments in LLVM, Clang, and related projects. LLVM Weekly is brought to you by Alex Bradbury . Subscribe to future issues at http://llvmweekly.org and pass it on to anyone else you think may be interested. Please send any tips or feedback to asb@asbradbury.org , @llvmweekly or @asbradbury on Twitter, or @llvmweekly@fosstodon.org or @asb@fosstodon.org . News and articles from around the web and events The next Cambridge Compiler Social will take place on 3rd September 2024 , featuring not one but two talks: Quidditch: An end-to-end deep learning compiler for highly-concurrent accelerators with software-managed caches (Markus Böck) and Mojo’s Wishlist for MLIR 2.0 (Jeff Niu). The call for proposals for the MLIR workshop at the LLVM Developer Meeting is open . According to the LLVM calendar in the coming week there will be the following: Office hours with the following hosts: Renato Golin, Anastasia Stulova, Quentin Colombet, Johannes Doerfert, Online sync-ups on the following topics: Flang, pointer authentication, AArc64, libc++, new contributors, LLVM/Offload, C/C++ language working group, OpenMP for Flang, MLIR, HLSL, MLGO. For more details see the LLVM calendar , getting involved documentation on online sync ups and office hours . On the forums “H. Vetinari” proposed distributing patch releases over the lifecycle of an LLVM version in order to avoid a situation where there are known issues to be addressed, but no more planned point releases and a long wait to the next major release. David Spickett requested feedback on the idea of authoring an LLVM blog post for the flang-new to flang renaming . Miguel A. Arroyo started an RFC thread on adding support for basic block sections on Windows (COFF) . Tulio Magno Quites Machado Filho suggested that LLVM/Clang builds should change to avoid exposing information on downstream git repositories that may be sensitive (e.g. URL). Michael Maitland posted an RFC on support for vectorisation of conditional scalar assignment . Chris Bieneman provided an update on the LLVM governance proposal discussion . LLVM commits The semantics of the experimental.get.vector.length intrinsic were made more strict in order to enable more optimisations. e806370 . The benchmark apps included in the LLVM test-suite were documented. c4a5381 . Optimisation remarks can now be emitted for ArgumentPromotion and DeadArgumentElimination. 470f55f . The amdgpu-sw-lower-lds pass was introduced, lowering local data store (LDS) uses to use dynamically allocated global memory. 7bc9d95 . The DXIL pretty printer now handles target extension type resources. 87157ab . The stepvector intrinsic was moved out of the experimental namespace. 95d2d1c . SimplifyCFG gained a new option to hoist load/stores with conditional faulting. 87c86aa . The Windows release packaging now only builds the AArch64, Arm, and X86 targets. 2a28df6 . The llvm.fake.use intrinsic was introduced to extend variable lifetimes. 3d08ade . Clang commits The clang-tidy contributing guide was updated. 362d37a . RISC-V vector crypto intrinsics are no longer considered experimental. 051054e6f . HLSL multi-argument resolution in Clang vs DXC was documented. 02654f7 . RISC-V vector tuple type support was added. 239127d . Other project commits Range extension thunks are now supported in LLD for ARM64EC targets. efad561 . libcxx’s lit test suite now runs against a version of the library installed in a dummy location in order to more closely approximate the library as shipped to users. 0e8208e . lldb-dap gained support for instruction breakpoints. 89c27d6 . Subscribe at LLVMWeekly.org . | 2026-01-13T09:30:34 |
https://llvmweekly.org/issue/594 | LLVM Weekly - #594, May 19th 2025 LLVM Weekly - #594, May 19th 2025 Welcome to the five hundred and ninety-fourth issue of LLVM Weekly, a weekly newsletter (published every Monday) covering developments in LLVM, Clang, and related projects. LLVM Weekly is brought to you by Alex Bradbury . Subscribe to future issues at https://llvmweekly.org and pass it on to anyone else you think may be interested. Please send any tips or feedback via email: asb@asbradbury.org , or Mastodon: @llvmweekly@fosstodon.org / @asb@fosstodon.org , or Bluesky: @llvmweekly.org / @asbradbury.org . News and articles from around the web and events After they started appearing last week, all recordings from EuroLLVM 2025 now seem to be available on YouTube . The next compiler social in Zurich will take place on May 28th . The call for papers is open for the LLVM-HPC workshop at SC25 (submissions due by August 15th). According to the LLVM Calendar in the coming week there will be the following: Office hours with the following hosts: Phoebe Wang, Johannes Doerfert Online sync-ups on the following topics: ClangIR upsreaming, pointer authentication, security response group, OpenMP, C/C++ language working group, Flang, RISC-V, embedded toolchains. For more details see the LLVM calendar , getting involved documentation on online sync ups and office hours . On the forums LLVM 20.1.5 was released . Tom Stellard gives some advice on how to deal with spam in issues and PRs on LLVM’s GitHub . It tentatively appears consensus was found in the discussion on adding warnings when bypassing the premerge testing . Jon Chesterfield queried if the callinst function type could be required to match the type of the function being called and Nikita Popov gave a good example of why this can’t readily be done. Arysef has an MLIR RFC on supporting !llvm.target as element types of vector and memref . GSoC contributors are getting underway. See the gsoc2025 tag or GSoC category for updates. Welcome to all of those taking part! LLVM commits llvm-symbolizer gained support for gsym files. f4b80b9 . The DXILResourceImplicitBinding pass was implemented. 03934d0 . The new GISelValueTracker printing pass can be used to print the known bits and sign bit of each def in a function. ec406e8 . The EVLIndVarSimplify pass was introduced for EVL-vectorized loops. 0ab67ec . Assembler support was added for the Xandesvpackfph RISC-V extension. Codegen was added for the lea instructions from the XandesPerf extension. 9e27db0 , a788a1a . Multi-member variants are now allowed in DWARF. 386f2ca . MC layer support was added for the RISC-V Q extension. 1e503d0 , 25e91ed , 99e8d22 . Documentation was written on MLGO corpus tooling. a3c4a5c . Profile format definitions were added for static data layout, as part of the work to support profile-guided static data partitioning. f3f2832 . DataLayout::getAddressSize(AS) was introduced, which returns the number of bits that can be used for arithmetic in the given address space. aec685e . Clang commits [counted_by] is now supported on struct pointers. HTMLMustacheGenerator.cpp was added to clang-doc. 3bdfa6f . bugprone-misleading-setting-of-reference was added to clang-tidy. d84b97e . Other project commits The polynomial dialect was removed from MLIR (it has moved to the HEIR project). a3d2b7e . Initial ARM64EC builtins support was added to compiler-rt. 3764ba2 . Basic constant folding was added to std::format in libcxx. 49bced4 . LLDB support for AIX made progress. bcb1227c , c02e6ca . Transpose/broadcast semantics were introduced to MLIR’s linalg.batch_reduce_matmul . d78ff5f . Subscribe at LLVMWeekly.org . | 2026-01-13T09:30:34 |
https://es-la.facebook.com/login/?next=https%3A%2F%2Fl.facebook.com%2Fl.php%3Fu%3Dhttps%253A%252F%252Fwww.instagram.com%252F%26amp%253Bh%3DAT0oK5bRFTTybnDOhYhIZLq01lQic0NLTeIbHIWCatEHpQ1l_XvBDhFFg93NTxyaIWLyhjuKO75pi9dqx6GinsMsCUF3-jXwiN5uEdfkpm7k0xf-caL8YQT8KCcQ_cBSLI1zBjdYsjE75jVT | Facebook Facebook Correo o teléfono Contraseña ¿Olvidaste tu cuenta? Crear cuenta nueva Se te bloqueó temporalmente Se te bloqueó temporalmente Parece que hiciste un uso indebido de esta función al ir muy rápido. Se te bloqueó su uso temporalmente. Back Español 한국어 English (US) Tiếng Việt Bahasa Indonesia ภาษาไทย 中文(简体) 日本語 Português (Brasil) Français (France) Deutsch Registrarte Iniciar sesión Messenger Facebook Lite Video Meta Pay Tienda de Meta Meta Quest Ray-Ban Meta Meta AI Más contenido de Meta AI Instagram Threads Centro de información de votación Política de privacidad Centro de privacidad Información Crear anuncio Crear página Desarrolladores Empleo Cookies Opciones de anuncios Condiciones Ayuda Importación de contactos y no usuarios Configuración Registro de actividad Meta © 2026 | 2026-01-13T09:30:34 |
https://ja-jp.facebook.com/login/?next=https%3A%2F%2Fl.facebook.com%2Fl.php%3Fu%3Dhttps%253A%252F%252Fwww.instagram.com%252F%26amp%253Bh%3DAT0_eO-stakg9vLsOUo7Lt26VLQ_aYkr9Pf8ZZaLhPMiLcqEKHlcgGyJNGUNiyBkcQSC6SVtvR-ocoHfFkGBRUIIfK4kqcuSRuVlDS1_g0KFGeSi6wHVGd63HL5D3r9fcZfhU2T8Lb5znjek | Facebook Facebook メールアドレスまたは電話番号 パスワード アカウントを忘れた場合 新しいアカウントを作成 機能の一時停止 機能の一時停止 この機能の使用ペースが早過ぎるため、機能の使用が一時的にブロックされました。 Back 日本語 한국어 English (US) Tiếng Việt Bahasa Indonesia ภาษาไทย Español 中文(简体) Português (Brasil) Français (France) Deutsch アカウント登録 ログイン Messenger Facebook Lite 動画 Meta Pay Metaストア Meta Quest Ray-Ban Meta Meta AI Meta AIのコンテンツをもっと見る Instagram Threads 投票情報センター プライバシーポリシー プライバシーセンター Facebookについて 広告を作成 ページを作成 開発者 採用情報 Cookie AdChoices 規約 ヘルプ 連絡先のアップロードと非ユーザー 設定 アクティビティログ Meta © 2026 | 2026-01-13T09:30:34 |
https://llvmweekly.org/issue/584 | LLVM Weekly - #584, March 10th 2025 LLVM Weekly - #584, March 10th 2025 Welcome to the five hundred and eighty-fourth issue of LLVM Weekly, a weekly newsletter (published every Monday) covering developments in LLVM, Clang, and related projects. LLVM Weekly is brought to you by Alex Bradbury . Subscribe to future issues at https://llvmweekly.org and pass it on to anyone else you think may be interested. Please send any tips or feedback via email: asb@asbradbury.org , or Mastodon: @llvmweekly@fosstodon.org / @asb@fosstodon.org , or Bluesky: @llvmweekly.org / @asbradbury.org . News and articles from around the web and events The program for the 2025 EuroLLVM program has been announced and early bird registration ends on March 12th. The call for proposals for 2025 AsiaLLVM is open through to March 31st . The event will take place on June 10th in Tokyo. There’s also an open call for program committee and student travel grant review committee members . Fangrui Song blogged about compiling C++ with the Clang API . As warned last time, the US entered daylight savings time over the weekend but much of the rest of the work isn’t in daylight savings yet. So expect some confusion about times or altered meeting slots. According to the LLVM calendar in the coming week there will be the following: Office hours with the following hosts: Alexey Bader, Aaron Ballman, Alina Sbirlea, Kristof Beyls, Johannes Doerfert, MLIR area team. Online sync-ups on the following topics: pointer authentication, alias analysis, OpenMP, Flang, BOLT, LLVM libc, RISC-V, canonical wrapping and non-wrapping types. For more details see the LLVM calendar , getting involved documentation on online sync ups and office hours . On the forums LLVM 20.1.0 has been tagged . On behalf of the Clang Area Team, Aaron Ballman summarised their plans for meeting and for handling RFCs . To highlight one aspect “The RFC process is not being drastically changed. Authors will continue to write their proposals on Discourse (please remember to add [RFC] to the post title) and proposals which have obvious consensus (for or against) will not need to be seen by the area team. However, the Clang Area Team secretary will proactively look for RFCs that appear to not have a clear path forward to add them to the team’s agenda.” Matthias Springer highlighted that match and rewrite are now deprecated in MLIR in favour of matchAndRewrite . Serge Pavlov proposes changes to strict floating point operation representation in IR . In a discussion on plans for NewGVN , Nikia Popov queried if it should be deleted at this point with effort redirected to improving the current GVN (global value numbering) implementation. Nikhil Kalra raised the issue of MLIR bytecode dialect versioning and fallback mechanisms , coming from the perspective of having to support a scenario where bytecode is used as an exchange format and reader of the bytecode may not support the version being sent. Yusuke Minato authored a flang RFC on improving the performance of Fortran::runtime::Assign for derived types . Michael Adams shared version 0.3.0 of lecture slides for using Clang libraries . Sylvestre Ledru and Serge Guelton propose moving llvm-toolchain-integration-test-suite under the LLVM umbrella . If you’re interested in submitting a proposal for LLVM in Google summer of Code this year, but sure to read Anton Korobeynikov’s pinned post on GSoC . Andrzej Warzynski started a thread to discuss the process for code review when upstreaming patches that might have co-authorship . There’s a thread discussing Clang’s ability to accept MISRA check tools , featuring input from the Andrew Banks, Chairman of the MISRA C Working Group. As Aaron Ballman summarises , there doesn’t seem to be a clear path forwards with the current restrictions, but Andrew has offered to discuss these issues at MISRA. Paul Kirth posted an RFC on addressing deficiencies in LLVM’s LTO implementation . LLVM commits The Module data structure now stores a Triple rather than just storing the target triple as a string. 979c275 . Support was added for the RISC-V VLS calling convention. c804e86 . MachineSink, RemoveRedundantDebugValue, FixupStatePointCallerSaved, and ExpandPostRAPseudos was ported to the new pass manager. 77f44a96 , 6abe148 , e0eb4ed . A CI best practices document was started, which currently contains guidance for work on LLVM’s GitHub Actions. 829401f . A pass was added to the SPIR-V backend to remove spv_ptrcast intrinsics. 7c8b127 . The SLPVectorizer spill cost analysis was improved. 855178a . Code generation was implemented for the Qualcomm Xqccmp vendor RISC-V extension and assembler support was added for Qualcomm’s Xqcibm (bit manipulation) extension. e49180d , 6e7e46c . Support was added for the SPIR-V SPV_INTEL_memory_access_aliasing extension. 7a44ff1 . A RISCVLoadStoreOptimizer pass was implemented in order to produce load/store pairs for the relevant MIPS RISC-V vendor extension. 5048a08 . Clang commits An alpha.core.FixedAddressDereference checker was added. da7403e . AST components and semantic analysis for OpenACC’s declare , cache , and routine constructs was implemented. 5d7d66b , d5cec38 , df1e102 . ClangIR lowering can now produce Func , Return , Alloca , Load , and Store ops. fa072bd . Clang’s diagnostics were improved by more consistently pointing to the relevant template parameter. a24523a . Other project commits ranges::swap_ranges was optimised for vector<bool>::iterator yielding up to 611x performance improvements. a12744f . LLD’s WebAssembly linker now supports the custom-page-sizes WebAssembly proposal. 6018930 . libclc headers will no longer be installed. They are intended as an internal implementation detail. a2b0576 . LLDB no longer supports coalescing progress reports as the main user (XCode) is moving to the regular full progress events. a1b14db . MLIR’s match and rewrite functions were deprecated. matchAndRewrite should be used instead. a21cfca320 . Subscribe at LLVMWeekly.org . | 2026-01-13T09:30:34 |
https://th-th.facebook.com/login/?next=https%3A%2F%2Fl.facebook.com%2Fl.php%3Fu%3Dhttps%253A%252F%252Fwww.instagram.com%252F%26amp%253Bh%3DAT1KY84hKm_-by-YRr4vpnWKQpQpwSlqcHtHuJaVKw1bW8wItTohGpLUCnyGOFaKEl24B0RlP8zqhkc8lgjUOBrHeD_3-x2x1wAeaDTMaMg12_UywdHBUwoulr3RtwamghKKTr5Z0_NPtXeL | Facebook Facebook อีเมลหรือโทรศัพท์ รหัสผ่าน ลืมบัญชีใช่หรือไม่ สร้างบัญชีใหม่ คุณถูกบล็อกชั่วคราว คุณถูกบล็อกชั่วคราว ดูเหมือนว่าคุณจะใช้คุณสมบัตินี้ในทางที่ผิดโดยการใช้เร็วเกินไป คุณถูกบล็อกจากการใช้โดยชั่วคราว Back ภาษาไทย 한국어 English (US) Tiếng Việt Bahasa Indonesia Español 中文(简体) 日本語 Português (Brasil) Français (France) Deutsch สมัคร เข้าสู่ระบบ Messenger Facebook Lite วิดีโอ Meta Pay Meta Store Meta Quest Ray-Ban Meta Meta AI เนื้อหาเพิ่มเติมจาก Meta AI Instagram Threads ศูนย์ข้อมูลการลงคะแนนเสียง นโยบายความเป็นส่วนตัว ศูนย์ความเป็นส่วนตัว เกี่ยวกับ สร้างโฆษณา สร้างเพจ ผู้พัฒนา ร่วมงานกับ Facebook คุกกี้ ตัวเลือกโฆษณา เงื่อนไข ความช่วยเหลือ การอัพโหลดผู้ติดต่อและผู้ที่ไม่ได้ใช้บริการ การตั้งค่า บันทึกกิจกรรม Meta © 2026 | 2026-01-13T09:30:34 |
https://id-id.facebook.com/login/?next=https%3A%2F%2Fl.facebook.com%2Fl.php%3Fu%3Dhttps%253A%252F%252Fwww.instagram.com%252F%26amp%253Bh%3DAT0_eO-stakg9vLsOUo7Lt26VLQ_aYkr9Pf8ZZaLhPMiLcqEKHlcgGyJNGUNiyBkcQSC6SVtvR-ocoHfFkGBRUIIfK4kqcuSRuVlDS1_g0KFGeSi6wHVGd63HL5D3r9fcZfhU2T8Lb5znjek | Facebook Facebook Email atau telepon Kata Sandi Lupa akun? Buat Akun Baru Anda Diblokir Sementara Anda Diblokir Sementara Sepertinya Anda menyalahgunakan fitur ini dengan menggunakannya terlalu cepat. Anda dilarang menggunakan fitur ini untuk sementara. Back Bahasa Indonesia 한국어 English (US) Tiếng Việt ภาษาไทย Español 中文(简体) 日本語 Português (Brasil) Français (France) Deutsch Daftar Masuk Messenger Facebook Lite Video Meta Pay Meta Store Meta Quest Ray-Ban Meta Meta AI Konten Meta AI lainnya Instagram Threads Pusat Informasi Pemilu Kebijakan Privasi Pusat Privasi Tentang Buat Iklan Buat Halaman Developer Karier Cookie Pilihan Iklan Ketentuan Bantuan Pengunggahan Kontak & Non-Pengguna Pengaturan Log aktivitas Meta © 2026 | 2026-01-13T09:30:34 |
https://llvmweekly.org/issue/539 | LLVM Weekly - #539, April 29th 2024 LLVM Weekly - #539, April 29th 2024 Welcome to the five hundred and thirty-ninth issue of LLVM Weekly, a weekly newsletter (published every Monday) covering developments in LLVM, Clang, and related projects. LLVM Weekly is brought to you by Alex Bradbury . Subscribe to future issues at http://llvmweekly.org and pass it on to anyone else you think may be interested. Please send any tips or feedback to asb@asbradbury.org , @llvmweekly or @asbradbury on Twitter, or @llvmweekly@fosstodon.org or @asb@fosstodon.org . News and articles from around the web and events Fangrui Song blogged about the removal of -mrelax-all from -O0 . The next Zurich Compiler Social will take place on May 14th and feature the talk “Computing Bounds of SSA Values in MLIR” by Matthias Springer. The next Cambridge UK LLVM social will take place on 16th May . The BAŞARIM 2024 conference (to be held in Ankara, Turkey) has a call for LLVM talks . According to the LLVM calendar in the coming week there will be the following: Office hours with the following hosts: Quentin Colombet, Johannes Doerfert. Online sync-ups on the following topics: Flang, MLIR C/C++ frontend, pointer authentication, new contributors, llvm/offload, classic flang, Clang C/C++ language working group, loop optimisations, OpenMP for flang, MLIR, HLSL, MLGO. For more details see the LLVM calendar , getting involved documentation on online sync ups and office hours . On the forums Tom Stellard and Kristof Beyls posted an RFC proposal to require pull request for contributions , motivated by concerns that without this it isn’t possible to see who actually pushed a commit to the repo. An important point to highlight is that it would still be possible to commit without pre-commit review via a helper script that creates a PR and mrges it. I think it’s fair to say that response has been mixed so far, with plenty of people offering support but also plenty expressing concerns about adding additional friction or breaking workflows. Théo Degioanni kicked off an RFC thread on supporting zero-width integers in CIRCT’s comb dialect . Petr Hosek proposed support for memory regions in ELF via something like __attribute__((memory("special"))) int buffer[1024]; represented in IR as @buffer = dso_local global [1024 x i32] zeroinitializer, memory "special", align 16 . Stephen Tozer posted an RFC to rewrite the instruction insertion interface in order to make the correct usage with respect to correct debug info generation intuitive and easy to verify. Peter Waller proposed an RFC on normalisation of baremetal target triples , addressing issues with the current defaults e.g. aarch64-none-elf currently is normalised to aarch64-none-unknown-elf but should be aarch64-unknown-none-elf (i.e. setting the vendor field to unknown). Andy Kaylor raised an issue about denormal-fp-math and fast-math . Mehdi Amini raised the issue that flang tests seem to be abnormally slow to run on Windows . Huihui Zhang shared an idea for a pass (with prototype implementation) to replace expensive array index computation with precomputed array lookup . LLVM commits The initial calling convention lowering was implemented for the Xtensa backend. 36209d3 . Memory model relaxation annotations are now supported in LLVM IR. See the included documentation for many more details. cf328ff . Targets can now provide target-specified module splitting logic for --lto-partitions . e86ebe4 . RISC-V extension information is now specified RISCVFeatures.td and the relevant C++ logic is primarily produced by TableGen. a6c0282 , b64e483 , 80628ee . Multivalue return is enabled in WebAssembly when the multivalue ABI is used. c921ac7 . By specialising more MatchTable opcodes, the size of AArch64InstructionSelector.cpp.o was reduced by 10% and the MatchTable size by 17%. 9375962 . llvm-objdump now prints disassembled RISC-V instructions in the same byte order as GNU objdump. b27f86b . A HexagonCopyHoisting pass was added. cb508a0 . Clang commits The AArch64 Neoverse-{N3,V3,V3AE} are now supported. a670cda . The bugprone-return-const-ref-from-parameter, modernize-min-max-use-initializer-list, and readability-math-missing-parantheses checks were added to clang-tidy. d56f08b , d3f92e3 , 8dc7db7 . __GCC_DESTRUCTIVE_SIZE and __GCC_CONSTRUCTIVE_SIZE are now defined. 72c373b . -mrelax-all is no longer enabled for O0 on RISC-V. 6b1b4c1 . Bfloat16 intrinsics for the RISC-V Zvfbf* vector extensions are now supported. 3fa6b9c . Other project commits ctx_profile was added to compiler-rt, adding the basic scaffolding for contextual instrumented PGO. 6ad22c8 . LLVM’s libc documented their policy on use of assembly code. 0336116 . Libcxx documentation on modules was updated to describe the use of CMake 3.30’s module support. 033453a . An initial patch towards “step into specific / step in targets” support in LLDB DAP was landed. 2f2e31c3 . MLIR documentation was added on how to use sharded op definitions. 83d0616 . Subscribe at LLVMWeekly.org . | 2026-01-13T09:30:34 |
https://llvmweekly.org/issue/595 | LLVM Weekly - #595, May 26th 2025 LLVM Weekly - #595, May 26th 2025 Welcome to the five hundred and ninety-fifth issue of LLVM Weekly, a weekly newsletter (published every Monday) covering developments in LLVM, Clang, and related projects. LLVM Weekly is brought to you by Alex Bradbury . Subscribe to future issues at https://llvmweekly.org and pass it on to anyone else you think may be interested. Please send any tips or feedback via email: asb@asbradbury.org , or Mastodon: @llvmweekly@fosstodon.org / @asb@fosstodon.org , or Bluesky: @llvmweekly.org / @asbradbury.org . News and articles from around the web and events AsiaLLVM registration will be closing within the coming days , so if you’re hoping to attend now is your final chance to register. The next Portland LLVM social is taking place on May 29th . The GCC compiler backend for rustc can now do a full 3-stage bootstrap of the Rust compiler . According to the LLVM Calendar in the coming week there will be the following: Office hours with the following hosts: Kristof Beyls, Johannes Doerfert, Amara Emerrson. Online sync-ups on the following topics: Flang, C++ modules, LLVM/Offload, SPIR-V, OpenMP in flang, LLVM memory safety working group. For more details see the LLVM calendar , getting involved documentation on online sync ups and office hours . On the forums Tobias Hieta [proposed a slightly modified release process be followed from LLVM 21 onwards]https://discourse.llvm.org/t/rfc-updating-and-aligning-the-llvm-release-process-before-llvm-21/86493). The key change is that the number of release candidates is influenced by the number and scale of changes for the previous ones (meaning a final release might be reached either earlier or later than before). Joshua Cranmer provided some detailed advice on exception handling in LLVM . Justin Cady is seeking some pointers on issues with code coverage accuracy . Arysef posted an RFC on supporting sized target extension types in LLVM vectors . Tom Eccles proposes removing the warning that OpenMP support in Flang is experimental in time for the LLVM 21 release. All respondents are supportive so far. “jjmarr” is interested in caching C++ template instantiations across translation units . LLVM commits Initial support was implemented for integrated distributed ThinLTO. This allows distributed thin LTO without needing special build system support. 6520b21 . A scheduling model was added for the SiFive P800 processor series. b92b548 . Preparatory work was done to allow DLL export annotations in the llvm/CodeGen library. 98595cf . And APInt::clearBits() method was added. d067014 . The semantics of ptrtoint were further clarified in the LangRef. dbfd0fd . The LoongArch LA32S ISA extension is now supported. 746c682 . Assembler/disassembler support was added for the RISC-V ‘Xsfmm*’ (matrix multiplication) vendor specific extension. a0b6cfd . An update_givaluetracking_test_checks.py script was added. a2aa881 . IR2Vec was added as an analysis pass. Part of the MLGO effort, IR2Vec is a program embedding approach designed specifically for LLVM IR. 58ab005 . RISC-V intrinsics were altered to be usable with pointer types of any address space. 86d1d4e . llvm-objdump’s support for “fatbin” offload bundles was extended so that it can now extract offload fatbin bundle entries into separate code object files. 51a03ed . Clang commits ClangIR support for C++ member function calls and iterator-based range for loops was upstreamed. a0c515a , cbcfe66 . DiagnosticOptions was changed not to use an intrusive reference count. 9e306ad . Other project commits BOLT’s gadget scanner saw further development, with support for analysing functions without CFG information and detection of signing oracles. f5401c6 , 48a2836 . ShallowCopy in flang-rt was optimised. c2892b0 . The OpenCL builtins were reorganised within libclc. 32cf55a . A feature test macro header test generator utility was added to libcxx. b12d68e . LLDB now supports 32-bit RISC-V ELF corefiles. dfabd61 . Documentation was added for MLIR’s OpAsmAttr and TypeInterface. 1b69f77 . Subscribe at LLVMWeekly.org . | 2026-01-13T09:30:34 |
https://id-id.facebook.com/login/?next=https%3A%2F%2Fl.facebook.com%2Fl.php%3Fu%3Dhttps%253A%252F%252Fwww.instagram.com%252F%26amp%253Bh%3DAT2keGOX2gxggubPvbD2U4v7iuDC9S3X2Lk7QEf_zG6UCPFlqRgkB8gDW-EZJfw1fiHskSqvBHeZQITabHORPi6bmhZQB9HgmigfedLFjaYt-gvk5RTqrih_kcyIODnVVuMY0a6Vs1-agSJ_ | Facebook Facebook Email atau telepon Kata Sandi Lupa akun? Buat Akun Baru Anda Diblokir Sementara Anda Diblokir Sementara Sepertinya Anda menyalahgunakan fitur ini dengan menggunakannya terlalu cepat. Anda dilarang menggunakan fitur ini untuk sementara. Back Bahasa Indonesia 한국어 English (US) Tiếng Việt ภาษาไทย Español 中文(简体) 日本語 Português (Brasil) Français (France) Deutsch Daftar Masuk Messenger Facebook Lite Video Meta Pay Meta Store Meta Quest Ray-Ban Meta Meta AI Konten Meta AI lainnya Instagram Threads Pusat Informasi Pemilu Kebijakan Privasi Pusat Privasi Tentang Buat Iklan Buat Halaman Developer Karier Cookie Pilihan Iklan Ketentuan Bantuan Pengunggahan Kontak & Non-Pengguna Pengaturan Log aktivitas Meta © 2026 | 2026-01-13T09:30:34 |
https://llvmweekly.org/issue/556 | LLVM Weekly - #556, August 26th 2024 LLVM Weekly - #556, August 26th 2024 Welcome to the five hundred and fifty-sixth issue of LLVM Weekly, a weekly newsletter (published every Monday) covering developments in LLVM, Clang, and related projects. LLVM Weekly is brought to you by Alex Bradbury . Subscribe to future issues at http://llvmweekly.org and pass it on to anyone else you think may be interested. Please send any tips or feedback to asb@asbradbury.org , @llvmweekly or @asbradbury on Twitter, or @llvmweekly@fosstodon.org or @asb@fosstodon.org . News and articles from around the web and events According to the LLVM calendar in the coming week there will be the following: Office hours with the following hosts: Kristof Beyls, Johannes Doerfert, Amara Emerson. Online sync-ups on the following topics: Pointer authentication, SPIR-V, new contributors, OpenMP, Flang, RISC-V, LLVM’s libc, MLIR. For more details see the LLVM calendar , getting involved documentation on online sync ups and office hours . On the forums LLVM 19.1.0-rc3 was released . Andrew Savonichev proposed a new tool similar to llvm-reduce that works on DWARF object files . Brandon Wu shared an RFC on a proposed pass to optimise RISC-V vector register spill . Hongyu Chen, Daniel Thornburgh, and Prabhu Karthikeyan Rajasekaran proposed improvements to linker script handling in LLD . Peter Chou started an RFC thread on adding a templating language to clang-doc . Bill Wendling posted an RFC on adding a __builtin_get_counted_by builtin to Clang . Michael Kruse proposes to use LLVM_ENABLE_RUNTIMES for Flang’s runtime . LLVM commits The CPU definition was added for the Hazard3 RISC-V core used in the Raspberry Pi RP2350. 9fa2386 . A SME peephole optimiser pass was added for AArch64. 6c189ea . Errata workaround passes were added to the SPARC backend for the Gaisler GR712RC and UT700 cores. 7faf1a0 . Vector and vector crypto were added to the RISC-V SiFive P400 scheduler model. 7efa068 . CycleAnalysis gained methods to verify cycles and their nesting. b432afc . The C API was extended with support for creating instructions with custom synchronisation scopes. eb7d535 . An elect.sync intrinsic was added for NVPTX. d5e9691 . Some of the complexity-based canonicalisation was removed from InstCombine on the basis that it’s unreliable / difficult to reason about. a105877 . SPIR-V learned to sort basic blocks as required by the SPIR-V spec. 0c07e7c . Lowering of Mul/Div/Shift operations was implemented for the Xtensa backend. fab515c . A new RISC-V peephole was added to reduce VLs based on demanded VL. 26a8a85 . Clang commits Support for the “RealtimeSanitizer” was added. RTSan can be used to detect real-time violations e.g. calls to methods that aren’t safe for use in functions with deterministic runtime requirements. d010ec6 . -msmall-data-limit was defaulted to 0. Users of GP relaxation are encouraged to specify the customisation options explicitly. d3864d9 . -ffp-model=aggressive was introduced and ffp-model=fast was made more limited in effect. 27e5f50 . Support for -fsanitizer-undefined-ignore-overflow-pattern was added, which disables instrumentation around specific common patterns. 295fe0b . Other project commits LLVM’s libc docs were updated to reflect the new headergen setup. b89fef8 . Initial locale.h support was added to LLVM’s libc. 78d8ab2 . Materializations are now optional in MLIR’s dialect conversion. d7073c5 . Subscribe at LLVMWeekly.org . | 2026-01-13T09:30:34 |
https://llvmweekly.org/issue/601 | LLVM Weekly - #601, July 7th 2025 LLVM Weekly - #601, July 7th 2025 Welcome to the six hundred and first issue of LLVM Weekly, a weekly newsletter (published every Monday) covering developments in LLVM, Clang, and related projects. LLVM Weekly is brought to you by Alex Bradbury . Subscribe to future issues at https://llvmweekly.org and pass it on to anyone else you think may be interested. Please send any tips or feedback via email: asb@asbradbury.org , or Mastodon: @llvmweekly@fosstodon.org / @asb@fosstodon.org , or Bluesky: @llvmweekly.org / @asbradbury.org . News and articles from around the web and events Videos from the inaugural 2025 AsiaLLVM Developers' Meeting are now available on YouTube . The next LLVM meetup in Munich will take place on Thursday July 24th . The next Portland LLVM social will take place on July 10th . Fractal Fir (Michał Kostrubiec) blogged about bootstrapping Rust with GCC . According to the LLVM Calendar in the coming week there will be the following: Office hours with the following hosts: Alina Sbirlea, Johannes Doerfert. Online sync-ups on the following topics: Flang, MLIR C/C++ frontend, modules, libc++, LLVM/Offload, SPIR-V, OpenMP for flang, HLSL, memory safety. For more details see the LLVM calendar , getting involved documentation on online sync ups and office hours . On the forums Tulio Magno Quites Machado Filho proposed adding support to LLD for the GCC LTO format , allowing LLD to link object files that were generated with LTO. Alexis Engelke started an RFC discussion on disallowing struct/array IR values inside functions (in the near term, at least disallowing array/struct loads/stores). Sjoerd Meijer discussed plans for moving away from type-based getelementptr , to a ptradd that just adds an offset to a pointer. Specifically, raising questions about the impact on loop interchange and DependenceAnalysis. Notes were shared from the first LLVM Qualification working group sync-up . Yaxun (Sam) Liu provided a summary of the discussions on GNU Make jobserver support in LLVM so far and and noted that a PR is up for review . There’s going to be an LLVM 20.1.8 release, due to be cut on Tuesday . Kristof Beyls returned to the thread on improving the documentation of what is considered a security issue in LLVM to note that a PR is now available for review . The MLIR area team shared the proposed list of MLIR maintainers . The 75th edition of the MLIR newsletter is now out , providing the usual summary of updates from the MLIR ecosystem. Gleb Gladilov made observations about issues with the current API for building MLIR operations and suggested alternatives . LLVM commits The dead_on_return attribute was added, indicating the memory poitned to by the argument is dead upon function return. f1cc0b6 . LLVM’s developer policy now documents how to ask for permissions other than commit access (e.g. triage permissions). cd60247 . An attributor was added for identifying invariant loads. f393211 . LLVM’s ArrayRef now has consume_front and consume_back methods. 2725765 . LLVM’s developer policy received a bunch of clarifications and wording tweaks. f01017c . Code generation for WebAssembly global addresses with offsets was improved. cbc2ac5 . Clang commits Clang will now verify that alignments specified in the Clang TargetInfo match those specified by the LLVM data layout. 5fa4eb1 . A faster algorithm is was adaopted for the misc-confusable-identifiers clang-tidy check. c56c349 . The work to remove the RISCVToolchain and migrate it to the BareMetal toolchain was completed. f8cb798 . The _sys Clang builtin (matching the MSVC intrinsic) became supported for AArch64. ed27f18 . Other project commits The XeVM dialect was added to MLIR (“In short, XeVM is the nvvm or rocdl for Intel GPU”). b9b2661 . ELF LLD now supports integrated distributed ThinLTO (DLTO), which allows distribution of ThinLTO backend compilations via external systems like Incredibuild. 3b4e793 . flat_set was made constexpr in libcxx. 9eb4fc7 . Subscribe at LLVMWeekly.org . | 2026-01-13T09:30:34 |
https://llvmweekly.org/issue/551 | LLVM Weekly - #551, July 22nd 2024 LLVM Weekly - #551, July 22nd 2024 Welcome to the five hundred and fifty-first issue of LLVM Weekly, a weekly newsletter (published every Monday) covering developments in LLVM, Clang, and related projects. LLVM Weekly is brought to you by Alex Bradbury . Subscribe to future issues at http://llvmweekly.org and pass it on to anyone else you think may be interested. Please send any tips or feedback to asb@asbradbury.org , @llvmweekly or @asbradbury on Twitter, or @llvmweekly@fosstodon.org or @asb@fosstodon.org . News and articles from around the web and events Luke Lau blogged about changes to how the RISC-V LLVM backend inserts vsetvli (vector configuration) instructions , focusing particularly on how to break up such a potentially disruptive change into incrementally reviewable patches. Fangrui Song blogged about rethinking mapping symbols for efficiency . According to the LLVM calendar in the coming week there will be the following: Office hours with the following hosts: Johannes Doerfert, Amara Emerson. Online sync-ups on the following topics: Flang, pointer authentication, new contributors, LLVM/Offload, classic Flang, loop optimisations, OpenMP for Flang, MLIR. For more details see the LLVM calendar , getting involved documentation on online sync ups and office hours . On the forums MLIR News #68 is now available . Tom Stellard proposed changing the process for requesting commit access . Vladislav Dzhidzhoev started an RFC discussion on allowing LLDB shell tests to be run against a remote target platform . Min-Yih Hsu proposes refining the semantics of experimental.get.vector.length with the hope of constraining the semantics enough to allow more optimisations, while hopefully being generic enough for future targets. Alexander Belyaev kicked off an MLIR RFC discussion on modeling how data is laid out in registers with respects to the threads of a warp . Jon Chesterfield started a discussion on the use of user branches in the LLVM repo . Sjoerd Meijer started a new RFC thread proposing to revisit the decision and approach to deprecating Ofast , highlighting issuse such as compatibility with GCC. The LLVM 19.x branch will happen tomorrow 23rd of July . “Harini0924” proposed enabling the lit internal shell for tests by default , outlining how this an increase speed of test execution and avoid issues due to inconsistencies in shell behaviour across platforms. Michael Kruse suggested refactoring Clang’s CGAtomic.cpp to a new LLVMFrontendAtomiC library in order to reuse the logic for Flang. A number of respondents are suggesting that with advances in atomics lowering at the IR level, the amount of logic needed by frontends should be much reduced so this may not be necessary. LLVM commits llvm.memcpy.inline no longer requires a constant length. 522fd53 . 3DNow intrinsics and builtin support was removed. f0eb558 . A dxil::ResourceInfo utility was added to generate resource metadata and annotations for DXIL and documentation was added for resource handling. 48f55ba , 9be5f4f . Hooks were added to prefer fixed over scalable vectorisation on AArch64 if the cost model calculates equal cost for them. c5329c8 . An llvm.experimental.vector.compress intrinsic was added. 177ce19 . More work on SandboxIR was committed. 5338bd3 , c5432d3 . APFloat learned to handle the “f8E4M3” floating point type. f363317 . Three-way integer comparison instructions were added to GlobalISel. 1cc1072 . Codegen support was added for the Arm64EC hybrid_patchable attribute. 6cc8774 . Clang commits A deprecation warning is now emitted for -Ofast . 2ef7cbf . Clang’s lifetime analysis was extended to support assignments for pointer-like objects. 3eba28d . The source file name for template instantiations is now shown in -ftime-trace . cd495d2 . Function pointer re-signing was implemented for PAC. f6b06b4 . API notes can now be used to add Clang attributes to C++ methods. 8a79dc7 . clangd gained initial support for C++20 modules. fe6c240 . Other project commits An implementation of __init_riscv_feature_bits was added to compiler-rt. a41a4ac . Basic -mtune supported was introduced to flang. f1d3fe7 . fp16 support in libclc was improved. 7e6a739 . LLDB now has a frame recogniser for __builtin_verbose_trap which can display the failure-reason string. 8a27ef6 . Initial vector type legalisation for function signatures was added to MLIR for SPIRV. 6867e49 . Subscribe at LLVMWeekly.org . | 2026-01-13T09:30:34 |
https://www.php.net/manual/pt_BR/function.session-name.php | PHP: session_name - Manual update page now Downloads Documentation Get Involved Help Search docs Getting Started Introduction A simple tutorial Language Reference Basic syntax Types Variables Constants Expressions Operators Control Structures Functions Classes and Objects Namespaces Enumerations Errors Exceptions Fibers Generators Attributes References Explained Predefined Variables Predefined Exceptions Predefined Interfaces and Classes Predefined Attributes Context options and parameters Supported Protocols and Wrappers Security Introduction General considerations Installed as CGI binary Installed as an Apache module Session Security Filesystem Security Database Security Error Reporting User Submitted Data Hiding PHP Keeping Current Features HTTP authentication with PHP Cookies Sessions Handling file uploads Using remote files Connection handling Persistent Database Connections Command line usage Garbage Collection DTrace Dynamic Tracing Function Reference Affecting PHP's Behaviour Audio Formats Manipulation Authentication Services Command Line Specific Extensions Compression and Archive Extensions Cryptography Extensions Database Extensions Date and Time Related Extensions File System Related Extensions Human Language and Character Encoding Support Image Processing and Generation Mail Related Extensions Mathematical Extensions Non-Text MIME Output Process Control Extensions Other Basic Extensions Other Services Search Engine Extensions Server Specific Extensions Session Extensions Text Processing Variable and Type Related Extensions Web Services Windows Only Extensions XML Manipulation GUI Extensions Keyboard Shortcuts ? This help j Next menu item k Previous menu item g p Previous man page g n Next man page G Scroll to bottom g g Scroll to top g h Goto homepage g s Goto search (current page) / Focus search box session_regenerate_id » « session_module_name Manual do PHP Referência das Funções Extensões de Sessão Sessões Funções para Sessão Selecione a língua: English German Spanish French Italian Japanese Brazilian Portuguese Russian Turkish Ukrainian Chinese (Simplified) Other session_name (PHP 4, PHP 5, PHP 7, PHP 8) session_name — Obtém e/ou define o nome da sessão atual Descrição session_name ( ? string $name = null ): string | false session_name() retorna o nome da sessão atual. Se name for informado, session_name() irá atualizar o nome da sessão e retornar o nome da sessão antiga . Se um novo nome de sessão for informado no parâmetro name , session_name() modificará o cookie HTTP (e exibir o conteúdo quando session.use_trans_sid estiver habilitado). Assim que o cookie HTTP tiver sido enviado, chamar session_name() gerará um E_WARNING . session_name() deve ser chamada antes de session_start() para a sessão funcionar apropriadamente. O nome da sessão é redefinido para o padrão guardado em session.name na inicialização da requisição. Por isso, deve-se chamar session_name() para cada requisição (e antes que session_start() seja chamada). Parâmetros name O nome da sessão, que é usado em cookies e URLs (por exemplo, PHPSESSID ). Ele deve conter apenas caracteres alfanuméricos; deve ser curto e descritivo (para usuários com avisos de cookie habilitados). Se name for informado e diferente de null , o nome da sessão atual será modificado para o novo valor. Aviso O nome da sessão não pode consistir apenas de dígitos, pelo menos uma letra deve estar presente. Caso contrário um novo ID de sessão é gerado toda vez. Valor Retornado Retorna o nome da sessão atual. Se name for informado e a função atualizar o nome da sessão, o nome da sessão antiga será retornado, ou false em caso de falha. Registro de Alterações Versão Descrição 8.0.0 name é anulável agora. 7.2.0 session_name() verifica status de sessão; anteriormente, apenas verificava status de cookie. Portanto, a versão antiga de session_name() permitia chamar session_name() após session_start() , que poderia travar o PHP e resultar em comportamento inesperado. Exemplos Exemplo #1 Exemplo de session_name() <?php /* define o nome da sessão para WebsiteID */ $previous_name = session_name ( "WebsiteID" ); echo "O nome da sessão anterior era $previous_name <br />" ; ?> Veja Também session.name (diretiva de configuração) Melhore Esta Página Aprenda Como Melhorar Esta Página • Envie uma Solicitação de Modificação • Reporte um Problema ＋ adicionar nota Notas de Usuários 9 notes up down 146 Hongliang Qiang ¶ 21 years ago This may sound no-brainer: the session_name() function will have no essential effect if you set session.auto_start to "true" in php.ini . And the obvious explanation is the session already started thus cannot be altered before the session_name() function--wherever it is in the script--is executed, same reason session_name needs to be called before session_start() as documented. I know it is really not a big deal. But I had a quite hard time before figuring this out, and hope it might be helpful to someone like me. up down 65 php at wiz dot cx ¶ 17 years ago if you try to name a php session "example.com" it gets converted to "example_com" and everything breaks. don't use a period in your session name. up down 40 relsqui at chiliahedron dot com ¶ 16 years ago Remember, kids--you MUST use session_name() first if you want to use session_set_cookie_params() to, say, change the session timeout. Otherwise it won't work, won't give any error, and nothing in the documentation (that I've seen, anyway) will explain why. Thanks to brandan of bildungsroman.com who left a note under session_set_cookie_params() explaining this or I'd probably still be throwing my hands up about it. up down 21 Joseph Dalrymple ¶ 14 years ago For those wondering, this function is expensive! On a script that was executing in a consistent 0.0025 seconds, just the use of session_name("foo") shot my execution time up to ~0.09s. By simply sacrificing session_name("foo"), I sped my script up by roughly 0.09 seconds. up down 10 Victor H ¶ 10 years ago As Joseph Dalrymple said, adding session_name do slow down a little bit the execution time. But, what i've observed is that it decreased the fluctuation between requests. Requests on my script fluctuated between 0,045 and 0,022 seconds. With session_name("myapp"), it goes to 0,050 and 0,045. Not a big deal, but that's a point to note. For those with problems setting the name, when session.auto_start is set to 1, you need to set the session.name on php.ini! up down 3 mmulej at gmail dot com ¶ 4 years ago Hope this is not out of php.net noting scope. session_name('name') must be set before session_start() because the former changes ini settings and the latter reads them. For the same reason session_set_cookie_params($options) must be set before session_start() as well. I find it best to do the following. function is_session_started() { if (php_sapi_name() === 'cli') return false; if (version_compare(phpversion(), '5.4.0', '>=')) return session_status() === PHP_SESSION_ACTIVE; return session_id() !== ''; } if (!is_session_started()) { session_name($session_name); session_set_cookie_params($cookie_options); session_start(); } up down 0 tony at marston-home dot demon dot co dot uk ¶ 7 years ago The description that session_name() gets and/or sets the name of the current session is technically wrong. It does nothing but deal with the value originally supplied by the session.name value within the php.ini file. Thus:- $name = session_name(); is functionally equivalent to $name = ini_get('session.name'); and session_name('newname); is functionally equivalent to ini_set('session.name','newname'); This also means that: $old_name = session_name('newname'); is functionally equivalent to $old_name = ini_set('session.name','newname'); The current value of session.name is not attached to a session until session_start() is called. Once session_start() has used session.name to lookup the session_id() in the cookie data the name becomes irrelevant as all further operations on the session data are keyed by the session_id(). Note that changing session.name while a session is currently active will not update the name in any session cookie. The new name does not take effect until the next call to session_start(), and this requires that the current session, which was created with the previous value for session.name, be closed. up down -4 tony at marston-home dot demon dot co dot uk ¶ 7 years ago The description has recently been modified to contain the statement "When new session name is supplied, session_name() modifies HTTP cookie". This is not correct as session_name() has never modified any cookie data. A change in session.name does not become effective until session_start() is called, and it is session_start() that creates the cookie if it does not already exist. See the following bug report for details: https://bugs.php.net/bug.php?id=76413 up down -3 descartavel1+php at gmail dot com ¶ 2 years ago Always try to set the prefix for your session name attribute to either `__Host-` or `__Secure-` to benefit from Browsers improved security. See https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie#attributes Also, if you have auto_session enabled, you must set this name in session.name in your config (php.ini, htaccess, etc) ＋ adicionar nota Funções para Sessão session_​abort session_​cache_​expire session_​cache_​limiter session_​commit session_​create_​id session_​decode session_​destroy session_​encode session_​gc session_​get_​cookie_​params session_​id session_​module_​name session_​name session_​regenerate_​id session_​register_​shutdown session_​reset session_​save_​path session_​set_​cookie_​params session_​set_​save_​handler session_​start session_​status session_​unset session_​write_​close Copyright © 2001-2026 The PHP Documentation Group My PHP.net Contact Other PHP.net sites Privacy policy ↑ and ↓ to navigate • Enter to select • Esc to close • / to open Press Enter without selection to search using Google | 2026-01-13T09:30:34 |
https://llvmweekly.org/issue/596 | LLVM Weekly - #596, June 2nd 2025 LLVM Weekly - #596, June 2nd 2025 Welcome to the five hundred and ninety-sixth issue of LLVM Weekly, a weekly newsletter (published every Monday) covering developments in LLVM, Clang, and related projects. LLVM Weekly is brought to you by Alex Bradbury . Subscribe to future issues at https://llvmweekly.org and pass it on to anyone else you think may be interested. Please send any tips or feedback via email: asb@asbradbury.org , or Mastodon: @llvmweekly@fosstodon.org / @asb@fosstodon.org , or Bluesky: @llvmweekly.org / @asbradbury.org . News and articles from around the web and events Alex Denisov has authored the missing guide to dataflow analysis in MLIR . If you’re interested in how RISC-V vector code generation has been developing in LLVM over the past couple of releases, I’ve written the talk I gave recently at RISC-V Summit Europe as a blog post . According to the LLVM Calendar in the coming week there will be the following: Office hours with the following hosts: Johannes Doerfert, Renato Golin. Online sync-ups on the following topics: ClangIR upstreaming, pointer authentication, GSoC office hours, OpenMP, C/C++ language working group, Flang, RISC-V, libc, HLSL, MLGO. For more details see the LLVM calendar , getting involved documentation on online sync ups and office hours . On the forums There was quite a bit more discussion on the RFC on potentially changing LLVM’s release process . Aaron Ballman proposed removing support for delayed typo correction in Clang as the feature has no maintainer and a number of bugs with no path to being fixed. Slava Zakharin proposed adding llvm.loop.vectorize.reassociation.enable metadata which would allow unsafe reassociations during loop vectorisation. Elvis Wang would like to introduce a new VPlan transform that conditionally executes vector basic blocks based on mask activity . LLVM 20.1.6 was released . Abhikrant Sharma posted an MLIR RFC on supporting requantisation in the quant dialect . John Harrison discussed adding typing annotations to LLDB’s python code . If you have a workshop proposal for just before the next US LLVM Developers Meeting you have until June 6th to submit it . Alexis Engelke shared results from ‘TPDE’ which aims to provide baseline compilation much faster than FastISel . See the paper and GitHub repo for more information. LLVM commits The PTRADD SelectionDAG node was introduced. 8adcc8a . llvm.vector.[de]interleave{4,6,8} intrinsics were added. 3033f20 . The automated message for good-first-issue labeled issue was updated not to suggest requesting assignment. 50937eb . Support for the MemProf summary section was added. cc6f446 . llvm-remarkutil now has a tool to print a histogram of instruction frequencies, optionally filtered by function name via a regex. cb647ec . A flag was added to control call folding in the ConstantFolding pass. 1f7885c . --max-retries-per-test was added to lit , which will retry running failed tests up to the given number of times. 84fd907 . Clang commits Clang’s ThreadSafetyAnalysis now supports reentrant capabilities. c7ccfc6 . SpirvType and SpirvOpaqueType were added to HLSL. 5a45711 . Clang’s debuginfo was updated to emit a symbol for the debugger that points for the vtable address for the given class. This allows a debugger to associate classes with the physical location of their vtables using only the DWARF information. d1b0cbf . The clang-doc tool was updated with a command line option to enable the Mustache template backend. 79023db . Other project commits A device-side malloc implementation was implemented in LLVM’s libc for GPU. b4bc8c6 . Flang started added noalias to function arguments but was backed out for now as it leads to a performance regression due to function specialisation no longer kicking in. d16ecad . The new --pointer-match-depth option for LLDB’s type summary add command can be used to specify how many layers of pointers can be dereferenced at most when matching a summary formatter of type T . 02916a4 . Subscribe at LLVMWeekly.org . | 2026-01-13T09:30:34 |
https://docs.aws.amazon.com/de_de/AmazonCloudFront/latest/DeveloperGuide/lambda-edge-testing-debugging.html | Testen und Debuggen von Lambda@Edge-Funktionen - Amazon CloudFront Testen und Debuggen von Lambda@Edge-Funktionen - Amazon CloudFront Dokumentation Amazon CloudFront Entwicklerhandbuch Testen der Lambda@Edge-Funktionen Identifizieren Sie Lambda @Edge -Funktionsfehler in CloudFront Fehlerbehebung bei ungültigen Lambda@Edge-Funktionsantworten (Validierungsfehler) Fehlerbehebung bei Lambda@Edge-Funktionsausführungsfehlern Bestimmen der Lambda@Edge-Region Ermitteln Sie, ob Ihr Konto Logs an weiterleitet CloudWatch Die vorliegende Übersetzung wurde maschinell erstellt. Im Falle eines Konflikts oder eines Widerspruchs zwischen dieser übersetzten Fassung und der englischen Fassung (einschließlich infolge von Verzögerungen bei der Übersetzung) ist die englische Fassung maßgeblich. Testen und Debuggen von Lambda@Edge-Funktionen Es ist wichtig, dass Sie Ihren Lambda @Edge -Funktionscode eigenständig testen, um sicherzustellen, dass er die beabsichtigte Aufgabe erfüllt, und Integrationstests durchzuführen, um sicherzustellen, dass die Funktion korrekt funktioniert. CloudFront Während des Integrationstests oder nach der Bereitstellung Ihrer Funktion müssen Sie möglicherweise Fehler wie HTTP CloudFront 5xx-Fehler debuggen. Fehler können eine ungültige Antwort der Lambda-Funktion, Ausführungsfehler beim Auslösen der Funktion oder Fehler aufgrund einer Ablehnung der Ausführung durch den Lambda-Service sein. Die Abschnitte in diesem Thema enthalten Strategien, um festzustellen, welche Art von Fehler das Problem verursacht. Dazu finden Sie Schritte, die Sie unternehmen können, um das Problem zu beheben. Anmerkung Achten Sie bei der Überprüfung von CloudWatch Protokolldateien oder Metriken bei der Behebung von Fehlern darauf, dass diese an dem Ort angezeigt oder gespeichert werden, der dem Ort, an dem die Funktion ausgeführt wurde, AWS-Region am nächsten ist. Wenn Sie also eine Website oder Webanwendung mit Benutzern im Vereinigtes Königreich haben und Ihrer Distribution beispielsweise eine Lambda-Funktion zugeordnet ist, müssen Sie die Region ändern, um die CloudWatch Metriken oder Protokolldateien für London AWS-Region anzuzeigen. Weitere Informationen finden Sie unter Bestimmen der Lambda@Edge-Region . Themen Testen der Lambda@Edge-Funktionen Identifizieren Sie Lambda @Edge -Funktionsfehler in CloudFront Fehlerbehebung bei ungültigen Lambda@Edge-Funktionsantworten (Validierungsfehler) Fehlerbehebung bei Lambda@Edge-Funktionsausführungsfehlern Bestimmen der Lambda@Edge-Region Ermitteln Sie, ob Ihr Konto Logs an weiterleitet CloudWatch Testen der Lambda@Edge-Funktionen Der Test Ihrer Lambda-Funktion besteht aus zwei Schritten: eigenständiger Test und Integrationstest. Eigenständiger Test der Funktionalität Bevor Sie Ihre Lambda-Funktion hinzufügen CloudFront, stellen Sie sicher, dass Sie die Funktionalität zuerst testen, indem Sie die Testfunktionen in der Lambda-Konsole oder andere Methoden verwenden. Weitere Informationen zu den Tests in der Lambda-Konsole finden Sie unter Aufrufen einer Lambda-Funktion mit der Konsole im Entwicklerhandbuch für AWS Lambda . Testen Sie den Betrieb Ihrer Funktion in CloudFront Es ist wichtig, Integrationstests abzuschließen, bei denen Ihre Funktion einer Distribution zugeordnet ist und auf der Grundlage eines CloudFront Ereignisses ausgeführt wird. Stellen Sie sicher, dass die Funktion für das richtige Ereignis ausgelöst wird und eine für CloudFront gültige und korrekte Antwort zurückgibt. Achten Sie beispielsweise darauf, dass die Ereignisstruktur korrekt ist, dass nur gültige Header enthalten sind usw. Wenn Sie die Integrationstests mit Ihrer Funktion in der Lambda-Konsole wiederholen, folgen Sie den Schritten im Lambda @Edge -Tutorial, wenn Sie Ihren Code oder den CloudFront Trigger ändern, der Ihre Funktion aufruft. Stellen Sie beispielsweise sicher, dass Sie mit einer nummerierten Version Ihrer Funktion arbeiten, wie in diesem Schritt des Tutorials beschrieben: Schritt 4: Fügen Sie einen CloudFront Trigger hinzu, um die Funktion auszuführen . Beachten Sie beim Vornehmen von Änderungen und deren Bereitstellung, dass es mehrere Minuten dauern kann, bis Ihre aktualisierte Funktion und CloudFront Trigger in allen Regionen repliziert sind. Dies dauert in der Regel wenige Minuten, kann jedoch auch bis zu 15 Minuten dauern. Sie können überprüfen, ob die Replikation abgeschlossen ist, indem Sie zur CloudFront Konsole gehen und sich Ihre Distribution ansehen. So überprüfen Sie, ob die Bereitstellung Ihrer Replikation abgeschlossen ist Öffnen Sie die CloudFront Konsole unter https://console.aws.amazon.com/cloudfront/v4/home . Wählen Sie den Distributionsnamen aus. Überprüfen Sie, ob sich der Status der Verteilung von InProgress (Läuft) zurück auf Deployed (Bereitgestellt) geändert hat, d.h. Ihre Funktion wurde repliziert. Anschließend befolgen Sie die Schritte im nächsten Abschnitt, um zu überprüfen, ob die Funktion funktioniert. Beachten Sie, dass das Testen in der Konsole nur die Logik Ihrer Funktion validiert und keine Servicekontingente (früher als Limits bezeichnet) anwendet, die spezifisch für Lambda@Edge sind. Identifizieren Sie Lambda @Edge -Funktionsfehler in CloudFront Nachdem Sie überprüft haben, ob Ihre Funktionslogik korrekt funktioniert, werden möglicherweise immer noch HTTP 5xx-Fehler angezeigt, wenn Ihre Funktion ausgeführt wird. CloudFront HTTP 5xx-Fehler können aus einer Vielzahl von Gründen zurückgegeben werden, darunter Lambda-Funktionsfehler oder andere Probleme in. CloudFront Wenn Sie Lambda @Edge -Funktionen verwenden, können Sie Diagramme in der CloudFront Konsole verwenden, um herauszufinden, was den Fehler verursacht, und dann daran arbeiten, ihn zu beheben. Sie können beispielsweise sehen, ob HTTP 5xx-Fehler durch CloudFront oder durch Lambda-Funktionen verursacht werden, und dann können Sie für bestimmte Funktionen zugehörige Protokolldateien einsehen, um das Problem zu untersuchen. Informationen zur allgemeinen Behebung von HTTP-Fehlern finden Sie in CloudFront den Schritten zur Fehlerbehebung im folgenden Thema:. Behebung von Statuscodes für die Fehlerantwort in CloudFront Was verursacht Lambda @Edge -Funktionsfehler in CloudFront Es gibt mehrere Gründe, aus denen eine Lambda-Funktion einen HTTP 5xx-Fehler verursachen kann. Die Schritte zur Fehlerbehebung hängen von der Art des Fehlers ab. Fehler können wie folgt kategorisiert werden: Ein Lambda-Funktionsausführungsfehler. Ein Ausführungsfehler tritt auf, wenn Sie CloudFront keine Antwort von Lambda erhalten, weil die Funktion unbehandelte Ausnahmen enthält oder ein Fehler im Code vorliegt. Zum Beispiel, wenn der Code "callback(Error)" beinhaltet. Eine ungültige Lambda-Funktionsantwort wird zurückgegeben an CloudFront CloudFront Erhält nach der Ausführung der Funktion eine Antwort von Lambda. Ein Fehler wird zurückgegeben, wenn die Objektstruktur der Antwort nicht der Lambda@Edge-Ereignisstruktur entspricht oder die Antwort ungültige Header oder andere ungültige Felder enthält. Die Ausführung in CloudFront wird aufgrund von Lambda-Servicequotas (früher als Limits bezeichnet) gedrosselt Der Lambda-Service drosselt die Ausführung in jeder Region und gibt einen Fehler zurück, wenn Sie das Kontingent überschreiten. Weitere Informationen finden Sie unter Kontingente für Lambda@Edge . So bestimmten Sie den Typ des Fehlers Um Ihnen bei der Entscheidung zu helfen, worauf Sie sich beim Debuggen und bei der Behebung von Fehlern konzentrieren sollten, ist es hilfreich CloudFront, herauszufinden, warum CloudFront ein HTTP-Fehler zurückgegeben wird. Zu Beginn können Sie die Grafiken verwenden, die im Abschnitt Überwachung der CloudFront Konsole auf dem AWS-Managementkonsole bereitgestellt werden. Weitere Informationen zum Anzeigen von Diagrammen im Bereich Überwachung der CloudFront Konsole finden Sie unter Überwachen von CloudFront-Metriken mit Amazon CloudWatch . Die folgenden Diagramme sind besonders hilfreich, wenn Sie nachverfolgen möchten, ob Fehler von Ursprungs-Servern oder einer Lambda-Funktion zurückgegeben werden, und wenn Sie die Art des Problems eingrenzen möchten, wenn der Fehler aus einer Lambda-Funktion resultiert. Fehlerratendiagramm Eines der Diagramme, das Sie auf der Registerkarte Overview (Überblick) für Ihre Verteilungen anzeigen können, ist das Diagramm Error rates (Fehlerraten) . Dieses Diagramm zeigt die Rate der Fehler als Prozentsatz aller Anforderungen an, die bei Ihren Verteilungen eingehen. Das Diagramm zeigt die Gesamtfehlerrate, die gesamten 4xx-Fehler, die gesamten 5xx-Fehler und die gesamten 5xx-Fehler an, die aus Lambda-Funktionen resultieren. Basierend auf Fehlertyp und Anzahl können Sie Schritte unternehmen, um diese Probleme zu untersuchen und zu beheben. Wenn Lambda-Fehler auftreten, können Sie eine genauere Untersuchung durchführen, indem Sie sich die spezifischen Arten von Fehlern ansehen, die von der Funktion zurückgegeben werden. Die Registerkarte Lambda@Edge errors (Lambda@Edge-Fehler) enthält Diagramme, die Funktionsfehler nach Typ kategorisieren, damit Sie das Problem für eine bestimmte Funktion herausfinden können. Wenn Sie CloudFront Fehler sehen, können Sie Fehler beheben und daran arbeiten, die ursprünglichen Fehler zu beheben oder Ihre CloudFront Konfiguration zu ändern. Weitere Informationen finden Sie unter Behebung von Statuscodes für die Fehlerantwort in CloudFront . Diagramme für Ausführungsfehler und ungültige Funktionsanworten Die Registerkarte Lambda@Edge errors (Lambda@Edge-Fehler) enthält Diagramme, die Lambda@Edge-Fehler für eine bestimmte Verteilung nach Typ kategorisieren. So zeigt beispielsweise ein Diagramm alle Ausführungsfehler unterteilt nach AWS-Region an. Damit Fehler einfacher erkannt und behoben werden können, können Sie nach bestimmten Problemen suchen, indem Sie die Protokolldateien für spezifische Funktionen regionsweise öffnen und prüfen. So zeigen Sie Protokolldateien für eine bestimmte Funktion nach Region an Wählen Sie auf der Registerkarte Lambda@Edge-Fehler unter Zugeordnete Lambda@Edge-Funktionen den Funktionsnamen und dann Metriken anzeigen aus. Klicken Sie anschließend auf der Seite mit dem Namen der Funktion rechts oben auf Funktionsprotokolle anzeigen und wählen Sie dann eine Region aus. Wenn Sie beispielsweise Probleme im Diagramm Fehler für die Region USA West (Oregon) sehen, wählen Sie diese Region aus der Dropdown-Liste aus. Dadurch wird die CloudWatch Amazon-Konsole geöffnet. Wählen Sie in der CloudWatch Konsole für diese Region unter Protokollstreams einen Protokollstream aus, um die Ereignisse für die Funktion anzuzeigen. Lesen Sie darüber hinaus die folgenden Abschnitte in diesem Kapitel, um weitere Empfehlungen für die Behebung von Fehlern zu erhalten. Drosselungsdiagramm Die Registerkarte Lambda@Edge errors (Lambda@Edge-Fehler) enthält auch ein Diagramm zu Drosselungen . In einigen Situationen drosselt der Lambda-Service Ihre Funktionsaufrufe auf Regionsbasis, wenn Sie sich dem regionalen Kontingent (früher als Limit bezeichnet) für die Gleichzeitigkeit nähern. Wenn Sie einen limit exceeded (Grenzwert überschritten) -Fehler sehen, hat Ihre Funktion ein Kontingent erreicht, das der Lambda-Service für Ausführungen in einer Region nutzt. Weitere Informationen, u. a. auch zur Erhöhung des Kontingents, finden Sie unter Kontingente für Lambda@Edge . Ein Beispiel zur Verwendung dieser Informationen beim Beheben von HTTP-Fehlern finden Sie unter Vier Schritte zum Debuggen der Bereitstelllung von Inhalten in AWS . Fehlerbehebung bei ungültigen Lambda@Edge-Funktionsantworten (Validierungsfehler) Wenn Sie feststellen, dass es sich bei Ihrem Problem um einen Lambda-Validierungsfehler handelt, bedeutet dies, dass Ihre Lambda-Funktion eine ungültige Antwort auf zurückgibt. CloudFront Folgen Sie den Anweisungen in diesem Abschnitt, um Maßnahmen zur Überprüfung Ihrer Funktion zu ergreifen und sicherzustellen, dass Ihre Antwort den Anforderungen entspricht. CloudFront CloudFront validiert die Antwort einer Lambda-Funktion auf zwei Arten: Die Lambda-Antwort muss der gewünschten Objektstruktur entsprechen. Beispiele für eine fehlerhafte Objektstruktur sind: nicht interpretierbarer JSON-Code, fehlende Pflichtfelder und ein ungültiges Objekt in der Antwort. Weitere Informationen hierzu finden Sie unter Lambda@Edge-Ereignisstruktur . Die Antwort darf nur gültige Objektwerte beinhalten. Ein Fehler tritt auf, wenn die Antwort ein gültiges Objekt aber nicht unterstützte Werte enthält. Beispiele sind das Hinzufügen oder Aktualisieren von ungültigen Headern oder schreibgeschützten Headern (siehe Einschränkungen für Edge-Funktionen ), das Überschreiten der maximalen Body-Größe (siehe Beschränkungen für die Größe der generierten Antwort im Thema Lambda@Edge Fehler ) und ungültige Zeichen oder Werte (siehe Lambda@Edge-Ereignisstruktur ). Wenn Lambda eine ungültige Antwort auf zurückgibt CloudFront, werden Fehlermeldungen in Protokolldateien geschrieben, die in die Region CloudFront übertragen werden, CloudWatch in der die Lambda-Funktion ausgeführt wurde. Dies ist das Standardverhalten, an das die Protokolldateien gesendet werden, CloudWatch wenn eine ungültige Antwort eingeht. Wenn Sie jedoch eine Lambda-Funktion mit verknüpft haben, CloudFront bevor die Funktionalität veröffentlicht wurde, ist sie möglicherweise nicht für Ihre Funktion aktiviert. Weitere Informationen finden Sie unter Feststellen, ob Ihr Konto Protokolle an CloudWatch überträgt weiter unten im Thema. CloudFront überträgt Protokolldateien in die Region, die der Region entspricht, in der Ihre Funktion ausgeführt wurde, in der Protokollgruppe, die Ihrer Distribution zugeordnet ist. Protokollgruppen haben das folgende Format: /aws/cloudfront/LambdaEdge/ DistributionId , wo DistributionId ist die ID Ihrer Distribution. Informationen zur Bestimmung der Region, in der Sie die CloudWatch Protokolldateien finden, finden Sie unter Bestimmung der Lambda @Edge -Region weiter unten in diesem Thema. Wenn der Fehler reproduzierbar ist, können Sie eine neue Anfrage erstellen, die zu dem Fehler führt, und dann die Anforderungs-ID in einer fehlgeschlagenen CloudFront Antwort ( X-Amz-Cf-Id Header) suchen, um einen einzelnen Fehler in den Protokolldateien zu lokalisieren. Der Eintrag in der Protokolldatei enthält Informationen, die Ihnen bei der Identifizierung Ursache für den Fehler helfen können. Er zeigt außerdem die entsprechende Lambda-Anforderungs-ID an, mit der Sie die Ursache im Kontext einer einzelnen Anforderung analysieren können. Wenn ein Fehler nur sporadisch auftritt, können Sie mithilfe von CloudFront Zugriffsprotokollen die Anforderungs-ID für eine fehlgeschlagene Anfrage ermitteln und anschließend die CloudWatch Protokolle nach den entsprechenden Fehlermeldungen durchsuchen. Weitere Informationen finden Sie im vorherigen Abschnitt Bestimmung der Fehlerart . Fehlerbehebung bei Lambda@Edge-Funktionsausführungsfehlern Wenn es sich bei dem Problem um einen Lambda-Ausführungsfehler handelt, kann es hilfreich sein, Protokollierungsanweisungen für Lambda-Funktionen zu erstellen, Meldungen in CloudWatch Protokolldateien zu schreiben, die die Ausführung Ihrer Funktion überwachen CloudFront und feststellen, ob sie wie erwartet funktioniert. Anschließend können Sie in den CloudWatch Protokolldateien nach diesen Anweisungen suchen, um zu überprüfen, ob Ihre Funktion funktioniert. Anmerkung Auch wenn Sie Ihre Lambda@Edge-Funktion nicht geändert haben, kann diese durch Aktualisierungen der Lambda-Funktionsausführungsumgebung beeinträchtigt werden und einen Ausführungsfehler ausgeben. Informationen zum Testen und Migrieren auf eine neuere Version finden Sie unter Kommende Updates für die AWS Lambda- und AWS Lambda @Edge -Ausführungsumgebung. Bestimmen der Lambda@Edge-Region Um die Regionen zu sehen, in denen Ihre Lambda @Edge -Funktion Traffic empfängt, sehen Sie sich die Metriken für die Funktion auf der CloudFront Konsole auf der AWS-Managementkonsole an. Metriken werden für jede AWS Region angezeigt. Auf derselben Seite können Sie eine Region auswählen und Protokolldateien für diese anzeigen, um Probleme näher zu untersuchen. Sie müssen die CloudWatch Protokolldateien in der richtigen AWS Region überprüfen, um die Protokolldateien zu sehen, die bei der CloudFront Ausführung Ihrer Lambda-Funktion erstellt wurden. Weitere Informationen zum Anzeigen von Diagrammen im Bereich Überwachung der CloudFront Konsole finden Sie unter Überwachen von CloudFront-Metriken mit Amazon CloudWatch . Ermitteln Sie, ob Ihr Konto Logs an weiterleitet CloudWatch CloudFront Aktiviert standardmäßig die Protokollierung ungültiger Lambda-Funktionsantworten und überträgt die Protokolldateien CloudWatch mithilfe einer der Serviceverknüpfte Rollen für Lambda@Edge Wenn Sie Lambda @Edge -Funktionen haben, die Sie hinzugefügt haben, CloudFront bevor die Funktion für das Protokoll der ungültigen Lambda-Funktionsantwort veröffentlicht wurde, wird die Protokollierung aktiviert, wenn Sie Ihre Lambda @Edge -Konfiguration das nächste Mal aktualisieren, z. B. indem Sie einen Trigger hinzufügen. CloudFront Gehen Sie wie folgt vor, um zu überprüfen, ob die Übertragung der Protokolldateien an für Ihr Konto aktiviert CloudWatch ist: Prüfen Sie, ob die Protokolle in erscheinen CloudWatch — Achten Sie darauf, dass Sie in der Region suchen, in der die Lambda @Edge -Funktion ausgeführt wurde. Weitere Informationen finden Sie unter Bestimmen der Lambda@Edge-Region . Stellen Sie fest, ob die zugehörige serviceverknüpfte Rolle in Ihrem Konto in IAM vorhanden ist. Die IAM-Rolle AWSServiceRoleForCloudFrontLogger muss in Ihrem Konto vorhanden sein. Weitere Informationen über diese Rolle finden Sie unter Serviceverknüpfte Rollen für Lambda@Edge . JavaScript ist in Ihrem Browser nicht verfügbar oder deaktiviert. Zur Nutzung der AWS-Dokumentation muss JavaScript aktiviert sein. Weitere Informationen finden auf den Hilfe-Seiten Ihres Browsers. Dokumentkonventionen Hinzufügen von Auslösern zu einer Lambda@Edge-Funktion Löschen von Funktionen und Replikaten Hat Ihnen diese Seite geholfen? – Ja Vielen Dank, dass Sie uns mitgeteilt haben, dass wir gute Arbeit geleistet haben! Würden Sie sich einen Moment Zeit nehmen, um uns mitzuteilen, was wir richtig gemacht haben, damit wir noch besser werden? Hat Ihnen diese Seite geholfen? – Nein Vielen Dank, dass Sie uns mitgeteilt haben, dass diese Seite überarbeitet werden muss. Es tut uns Leid, dass wir Ihnen nicht weiterhelfen konnten. Würden Sie sich einen Moment Zeit nehmen, um uns mitzuteilen, wie wir die Dokumentation verbessern können? | 2026-01-13T09:30:34 |
https://llvmweekly.org/issue/591 | LLVM Weekly - #591, April 28th 2025 LLVM Weekly - #591, April 28th 2025 Welcome to the five hundred and ninety-first issue of LLVM Weekly, a weekly newsletter (published every Monday) covering developments in LLVM, Clang, and related projects. LLVM Weekly is brought to you by Alex Bradbury . Subscribe to future issues at https://llvmweekly.org and pass it on to anyone else you think may be interested. Please send any tips or feedback via email: asb@asbradbury.org , or Mastodon: @llvmweekly@fosstodon.org / @asb@fosstodon.org , or Bluesky: @llvmweekly.org / @asbradbury.org . News and articles from around the web and events The agenda for 2025 AsiaLLVM has now been posted . The next LLVM Berlin meetup will take place on June 5th . Romain Thomas blogged about using libFuzzer to fuzz a Windows Arm64 closed-source binary . GCC 15 was released . Also see Red Hat’s blog post on new C++ features in GCC 15 . According to the LLVM calendar in the coming week there will be the following: Office hours with the following hosts: Johannes Doerfert, Renato Golin. Online sync-ups on the following topics: Flang, MLIR Tensor compiler, modules, SPIR-V, OpenMP for flang, HLSL working group, memory safety working group, MLGO. For more details see the LLVM calendar , getting involved documentation on online sync ups and office hours . On the forums Kevin Sala Penades proposed a flexible and customisable new code instrumentation framework for LLVM. This would allow JSON to be used to describe the types of instructions thta should be instrumented and how. Peter Collingbourne would like to improve the reproducibility of linker benchmarking with a new reproducible Nix-based suite . Tom Tromey queried support for dynamic sizes and field offsets in DWARF , motivated by an LLVM-based Ada compiler. This generated responses from a number of other language frontend developers. “byrnesj1” started a discussion about the computeKnownBits recursion depth limit and case where the current limit can lead to missed optimisations. Andrzej Warzynski shared a summary of the MLIR vector dialect roundtable discussion at EuroLLVM . David Spickett suggested making it clearer what the different release package types are and their purpose . Alex Zinenko shared the latest MLIR area team meeting minutes . Nikita Popov reported back on investigations into removing type mutability in LLVM IR , noting some challenges. LLVM commits CodeGenPrepare learned to unfold popcount when used in power-of-two tests. 5080a02 . llvm-extract now supports unnamed basic blocks. 8a57df6 . A large TargetTransformInfo refactoring was landed, replacing “concept based polymorphism” with the PImpl (pointer to implementation) idiom. bb17651 . Details of the LLVM CoC appeal process were clarified. a5a6ae1 . Additional types of stores are now supported in DebugInfo assignment tracking. 928c333 . The LLVM_ABI_FRIEND macro was introduced for friend function declarations. c049583 . The AMDGPU backend gained support for block load/store of callee saved registers. 5bad5d8 . The ForwardHandleAccesses pass was added to the DirectX backend. a83b4a2 . computeKnownBits was taught to use range metadata for atomic_load . f261f14 . The AssertNoFPClass SelectionDAG node was introduced, which can be used to mark a value we are sure isn’t some fp class type. f0c61d2 . Clang commits As usual, further work on ClangIR upstreaming. e.g. StackSave and StackRestoreOp as part of support for variable length arrays. Also support for accessing structure members. 80872d7 , 21bc23e . Clang now supports copying records with fields using pointer authentication. 5b16941 . Various enhancements were made to alpha.webkit.RetainPtrCtorAdoptChecker. 16e5c3d . Other project commits MLIR’s generate-test-checks.py was updated to preserve original SSA names when generating LIT variable names for function arguments. 7ff3d3b . The OpenMP API features supported by Flang were documented. 2c2ba7e . The Fortran standards supported in Flang were documented. 45a3056 . The Wasm linker can now be safely invoked multiple times within the same process 9cbbb74 . Subscribe at LLVMWeekly.org . | 2026-01-13T09:30:34 |
https://llvmweekly.org/issue/588 | LLVM Weekly - #588, April 7th 2025 LLVM Weekly - #588, April 7th 2025 Welcome to the five hundred and eighty-eighth issue of LLVM Weekly, a weekly newsletter (published every Monday) covering developments in LLVM, Clang, and related projects. LLVM Weekly is brought to you by Alex Bradbury . Subscribe to future issues at https://llvmweekly.org and pass it on to anyone else you think may be interested. Please send any tips or feedback via email: asb@asbradbury.org , or Mastodon: @llvmweekly@fosstodon.org / @asb@fosstodon.org , or Bluesky: @llvmweekly.org / @asbradbury.org . News and articles from around the web and events Final call for registration for the EuroLLVM Developers' Meeting . Registration is now open for the 2025 AsiaLLVM conference , taking place on June 10th in Tokyo. Alex Denisov blogged about building LLVM plugins with Bazel . Ubuntu benchmarked compiling more packages with -O3 and found it didn’t seem to be worth it. According to the LLVM calendar in the coming week there will be the following: Office hours with the following hosts: Alina Sbirlea, Kristof Beyls, Johannes Doerfert. Online sync-ups on the following topics: MLIR C/C++ frontend, ClangIR, pointer authentication, libc++, OpenMP, Flang, BOLT, RISC-V, LLVM libc. For more details see the LLVM calendar , getting involved documentation on online sync ups and office hours . On the forums LLVM 20.1.2 was released . Adam Siemieniuk started an MLIR RFC discussion on simplifying x86 intrinsic generation . Sergei Barannikov posted a migration guide for using the new support for TableGen-erating SDNode descriptions . Timo Nicolai asked about interfacing between xDSL and MLIR . As part of the discussions on global function merging, Zhaoxuan Jiang shared a plan for improving the performance of loading the stable function map for non-LTO setups . Meeting notes have been posted from the tensor compiler design group meeting . Aaron Ballman has posted to Discourse meeting notes from past Clang language working group meetings (and more - look in the Clang Frontend cateogry on Discourse). LLVM commits LLVM’s GitHub documentation page now covers stacked pull requests. 7dce16a . Debug info support for fixed-point types was added, motivated by Ada. 6894734 . The Xtensa windowed register call ABI was implemented. 89c25c5 . llvm-reduce learned to reduce the target-features attribute. f60eed9 . Options were added to control the cost heuristics applied for loop interchange. 528e408 . The spirv.VulkanBuffer type was added to the SPIR-V backend. a77d807 . llvm-dwarfdump’s --verify option is now multithreaded. 4f902d2 . MCAsmLexer and AsmLexer were merged. c9f6d26e . An initial CFG simplification transform was added to VPlan. 5fbd065 . SelectionDAGTargetInfo and SDNodeInfo classes were introduced for accessing generated SDNode descriptions. 0a17427 . Clang commits The ClangIR upstreaming effort added support for while and do..while loops, as well as break and continue statements. 9f3d8e8 , b0d0636 . clang-sycl linker now uses the SPIR-V backend to do LLVM to SPIR-V translation internally. 4a4d41e . Other project commits BOLT’s gadget scanner can now detect non-protected indirect calls. c818ae7 . Driver options for array repacking were added for Flang. 3f6ae3f . ranges::iota was implemented in libcxx. 475cbf0 . std::flat_multiset was implemented in libcxx. 7013b51 . LLDB can now parallelise the loading of many shared libraries when symbol preloading is enabled. a8d2d16 . New OpenMP memory management interfaces were implemented. 8100bd5 . Subscribe at LLVMWeekly.org . | 2026-01-13T09:30:34 |
https://llvmweekly.org/issue/567 | LLVM Weekly - #567, November 11th 2024 LLVM Weekly - #567, November 11th 2024 Welcome to the five hundred and sixty-seventh issue of LLVM Weekly, a weekly newsletter (published every Monday) covering developments in LLVM, Clang, and related projects. LLVM Weekly is brought to you by Alex Bradbury . Subscribe to future issues at http://llvmweekly.org and pass it on to anyone else you think may be interested. Please send any tips or feedback to asb@asbradbury.org , @llvmweekly or @asbradbury on Twitter, or @llvmweekly@fosstodon.org or @asb@fosstodon.org . News and articles from around the web and events A survey is now up to better understand how MLIR develoeprs and users connect to the upstream infrastructure . Answers to this survey will help inform discussions on MLIR project governance and charter, so please do fill it in or pass on to others who use MLIR. The call for papers for the Compilers for Machine Learning (C4ML) workshop at CGO is now out . The next LLVM Bay Area meetup will take place on Monday November 18th . According to the LLVM calendar in the coming week there will be the following: Office hours with the following hosts: Aaron Ballman, Alexey Bader, Alina Sbirlea, Johannes Doerfert. Online sync-ups on the following topics: Flang, alias analysis, new contributors, LLVM/Offload, classic Flang, BOLT, MLIR open meeting. For more details see the LLVM calendar , getting involved documentation on online sync ups and office hours . On the forums Nikita Popov proposed adding support for modelling errno memory effects , noting that right now LLVM has no way to model that a function can only write to errno in particular (as opposed to other memory locations). Joshua Cranmer proposed allowing fast-math flags to be attached to more instructions (such as fpext, fptrunc, uitofp, sitofp). Takumi Nakamura posted an RFC on extending ObjectYAML to handle coverage map sections . In response to a question, Nikita Popov gave some illustrative examples for the difference between getelementptr nuw/nsw/nusw . In the RFC thread on introducing a bytecode for LLDB data fomatters, Adrian Prantl suggests a path forwards . Joshua Cranmer initiated an RFC discussion on changing the supported formats for floating-point literals in LLVM IR . Simone Campanoni posted an RFC on allowing ThinLTO to rename local functions with sections . Ivan Butygin kicked off an MLIR RFC thread on removing the offset from the memref type (there’s some detailed follow-up posts e.g this that give more background). LLVM commits A new analysis pass was introduced to avoid re-running transform passes in cases there has been no change. cacbe71 . Expectations about the handling of additional review comments after a ‘LGTM’ were documented. 41248b5 . Recursive types are now disallowed in LLVM IR. 4831e0a . Tuning flags for targets with fast segmented loads and stores were added to the RISC-V backend. beb12f9 . GlobalISel now canonicalizes (sub x, C) to (add, x, -C) . 999dfb2 . XRay instrumentation was implemented for SystemZ. 4a37799 . LLVM learned to emit function epilogue call frame information for RISC-V. 97982a8 . BranchRelaxation support was implemented in the Xtensa backend. 3b1b127 . RuntimeDyld now supports LoongArch. 4e668d5 . The implicit SDag node was removed. 501a583 . Clang commits As part of upstreaming ClangIR into mainline Clang, trivial codegen ( cir.fun @foo ) is now possible. c695a32 . APINotes gained preliminary lifetimebound support. 7ac78f1 . The __grid_constant__ attribute was implemented for CUDA. 7c3fdcc . A new alpha.webkit.UncheckedCallArgsChecker was added. ef353b0 . __builtin_counted_by_ref was added, a builtin that returns a pointer to the count field from the counted_by attribute. 7475156 . A build of libLLVMSupport was added to the lit suite that’s used for generating Clang profile data. 7382509 . Other project commits BOLT gained a --compact-code-model option for AArch64. 49ee606 . XRay is now supported on shared libraries for AArch64. 1adca7a . libcxx testing can now be run for GPU targets. 95a2eb7 . libcxx benchmarks are now built alongside the tests. e236a52 . Bounded iterators for std::array are now supported in libcxx. 427a5cf . The MLIR arith-int-range-narrowing pass was introduced. 9f0f6df . Subscribe at LLVMWeekly.org . | 2026-01-13T09:30:34 |
https://llvmweekly.org/issue/571 | LLVM Weekly - #571, December 9th 2024 LLVM Weekly - #571, December 9th 2024 Welcome to the five hundred and seventy-first issue of LLVM Weekly, a weekly newsletter (published every Monday) covering developments in LLVM, Clang, and related projects. LLVM Weekly is brought to you by Alex Bradbury . Subscribe to future issues at http://llvmweekly.org and pass it on to anyone else you think may be interested. Please send any tips or feedback via email: asb@asbradbury.org , or Mastodon: @llvmweekly@fosstodon.org / @asb@fosstodon.org , or Bluesky: @llvmweekly.org / @asbradbury.org . News and articles from around the web and events Recordings from the 2024 LLVM Developers' Meeting are now available . LLVM 19.1.5 was released . The next LLVM Bay Area meetup will take place on December 16th . According to the LLVM calendar in the coming week there will be the following: Office hours with the following hosts: Aaron Ballman, Alexey Bader, Alina Sbirlea, Kristof Beyls, Johannes Doerfert. Online sync-ups on the following topics: Flang, SYCL, new contributors, LLVM/Offload, classic flang, BOLT, OpenMP for Flang, MLIR. For more details see the LLVM calendar , getting involved documentation on online sync ups and office hours . On the forums Chris Bieneman posted an RFC on identifying contact information for voter registration , as part of implementing LLVM’s governance proposal. Renato Golin started to share results from the MLIR project charter and restructuring survey . Tanya Lattner is seeking volunteers for the 2025 EuroLLVM program committee . Keith Smiley reported that Vim filetype support for LLVM can now be taken from a separate llvm.vim repo (this mirrors the relevant files from the monorepo). In response to a question, Manuel Brito provided a summary of issues with GVN vs NewGVN . After an expression of interest, Vasileios Porpodas has posted a rebased version of the initial spill2reg patch up for review again . Jacques Pienaar is seeking feedback on a PR to move MLIR Python to nanobind from pybind11 , noting that this led to meaningful performance improvements for MLIR lowering time of a Google-internal LLM model in JAX. Igor Kudrin proposed extended llvm-objcopy to support editing notes in ELF binaries . Rahul Reddy Chamala proposed adding a Python callback in LLDB for source file resolution . The idea is this would provide a flexible way of providing mechanisms for retrieving arbitrary source files from servers. LLVM commits A ‘Lime1’ (named after ‘linear memory’) target CPU was added for WebAssembly. 35cce40 . fptrunc and fpext IR instructions can now take fast math flags. ecbe4d1 . Experimental MC layer support was added for the Qualcomm RISC-V ‘Xqcia’ extension. 6881c6d . SCEVExpansionBudget was added to UnrollingPreferences to allow backends to control the maximum budget for SCEV expansions. 4226e0a . WebAssembly target features were defined for “call-indirect-overlong” (a subset of “reference-types”, just enabling the overlong encoding for call_indirect immediate) and “bulk-memory-opt” (subset of “bulk-memory” just enabling memory.copy and memory.fill). c3536b2 . Skeleton versions of new AMDGPU register bank select passes were committed. fef54d0 . Clang commits -fpointer-tbaa was enabled by default, allowing more precise TBAA metadata. The commit message reports +2% more NoAlias results for memory accesses, +3% more stores removed by dead store elimination, +4% more loops vectorised. 7954a05 . Frame pointers are disabled by default for bare metal ARM targets, matching GCC behaviour. 2f4eac6 . A new webkit static analyzer checker was added for memory unsafe casts. 51a5b77b . For C++26, a deprecation warning will be emitted when a variadic parameter declaration isn’t preceded by a comma. 54fcf3e . __has_extension(c_fixed_enum) can be used to determine if support for fixed underlying enum types is present (as prior to C23, this is a language extension). 9791f25 . The initial ClangIR types were upstreamed from the ClangIR incubator project. a43b2e1 . Clang config file options can now be prefixed with $ if they are linker arguments that should be added after all the options specified on the commandline (rather than before). 755519f . Other project commits The old hdrgen in LLVM’s libc was deleted, removing the dependency on TableGen (and thus LLVM) in order to start bootstrapping a full build. newhdrgen was renamed to hdrgen . e0ae779 , 06c831d . The documentation of LLVM’s libc was reorganised. a9aff44 . Libunwind’s support for the Haiku operating system was improved. 3b904ae . Basic support for ARM64X dynamic relocations was added to the COFF LLD linker. 71bbafb . A proof of concept LLDB data formatter bytecode was committed (documentation and an example interpreter). 0ee364d . LLVM/Offload gained an offload-tblgen tool and an initial new API implementation. fd3907c . Subscribe at LLVMWeekly.org . | 2026-01-13T09:30:34 |
https://llvmweekly.org/issue/569 | LLVM Weekly - #569, November 25th 2024 LLVM Weekly - #569, November 25th 2024 Welcome to the five hundred and sixty-ninth issue of LLVM Weekly, a weekly newsletter (published every Monday) covering developments in LLVM, Clang, and related projects. LLVM Weekly is brought to you by Alex Bradbury . Subscribe to future issues at http://llvmweekly.org and pass it on to anyone else you think may be interested. Please send any tips or feedback via email: asb@asbradbury.org , or Mastodon: @llvmweekly@fosstodon.org / @asb@fosstodon.org , or Bluesky: @llvmweekly.org / @asbradbury.org . News and articles from around the web and events I mentioned last week that LLVM Weekly is now on Bluesky (as well as Mastodon). I’ve put together a “starter pack” of LLVM contributors/developers on Bluesky that may be of interest. If you’re not listed and want to be, just respond here or message me. This is a reminder that the FOSDEM LLVM dev-room CfP closes on December 1st . Herb Sutter published a trip report from the recent ISO C++ meeting in Wrocław . LLVM 19.1.4 was released . The 16th Open Source Development Tools Conference (formerly HelloGCC Workshop) will take place on December 7th and is accepting submissions until November 30th . According to the LLVM calendar in the coming week there will be the following: Office hours with the following hosts: Kristof Beyls, Johannes Doerfert., Amera Emerson. Online sync-ups on the following topics: Flang, libc++, new contributuros, LLVM/Offload, classic flang, OpenMP for flang, MLIR. (though do double-check especially the meetings later in the week, as I’d expect cancellations due to thanksgiving in the US). For more details see the LLVM calendar , getting involved documentation on online sync ups and office hours . On the forums John Regehr kicked off a discussion on improving constraint elimination in LLVM . Matthias Springer followed up on the MLIR thread on low precision FP types with a proposal . Pavel Labath raised the issue of discontinuous functions in LLDB. Noting that tools like Propeller may split functions into smaller pieces, and although this is representable in DWARF, LLDB’s internal representation doesn’t allow for it. J Ryan Stinnett and Stephen Kell posted a v2 RFC on contributing a new debug info coverage extension to llvm-dwarfdump . ChuanqiXu proposed a ClangIR-based safe C++ . There’s plenty of interest in the details of the proposal, but also questions about its limitations and whether the timing is right for an RFC given that ClangIR is not yet mature. Jon Chesterfield initiated an RFC thread on representing function pointers as integer indices into a table for targets other than Wasm . Kristof Beyls shared an update on the previous BOLT-based binary security analysis tool RFC to note that an initial PR is now up for review . LLVM commits ORC’s new LazyObjectLinkingLayer allows object files to be added to an executor that will not be linked into it unless some function they define is called at runtime. 224290d . The RISC-V backend gained support for even-odd GPR pairs in inline assembly using the ‘R’ constraint. 4615cc3 . Commit access requests can now be made via GitHub issues. 6fe94c3 . The basic definition for “LLVM” as the environment part of a triple (as in x86_64-pc-linux-llvm was added, intended for use to indicate LLVM’s libc. 7672216 . In order to allow for better vectorisation, the SLP vectoriser now matches scalar instructions + poison values as it poisons are instructions with the same opcode. b870336 . Hexagon gained a load widening pass (building on the previously committed store widening pass). 028d41d . Clang commits Clang’s internals manual was updated to discourage people from using contractions in diagnostics. f710e4c . Clang learned to handled __builtin_cpu_is for RISC-V. 875b10f . -m{arch,tune}=diamondrapids is now supported. 97836be . Scoped atomic thread fence is now supported. 1ced565 . Other project commits The formatting for LLDB’s editline completion was improved. dd78d7c . A new pass was added to Flang to lower omp.workshare to other OpenMP constructs that can be lowered to LLVM. e7e5541 . malloc in LLVM’s libc now uses a best-fit binary trie. 385961d . Subscribe at LLVMWeekly.org . | 2026-01-13T09:30:34 |
https://llvmweekly.org/issue/585 | LLVM Weekly - #585, March 17th 2025 LLVM Weekly - #585, March 17th 2025 Welcome to the five hundred and eighty-fifth issue of LLVM Weekly, a weekly newsletter (published every Monday) covering developments in LLVM, Clang, and related projects. LLVM Weekly is brought to you by Alex Bradbury . Subscribe to future issues at https://llvmweekly.org and pass it on to anyone else you think may be interested. Please send any tips or feedback via email: asb@asbradbury.org , or Mastodon: @llvmweekly@fosstodon.org / @asb@fosstodon.org , or Bluesky: @llvmweekly.org / @asbradbury.org . News and articles from around the web and events LLVM 20.1.0 was released . An in-depth LLVM project blog post from David Spickett goes into depth on the history of Flang, technical implementation details, and the switch from flang-new to flang . The agenda for the MLIR workshop at EuroLLVM is now available . The next LLVM Bay Area meetup will take place on 31st March . The next HelloLLVM online meetup will take place on March 22nd . According to the LLVM calendar in the coming week there will be the following: Office hours with the following hosts: Phoebe Wang, Johannes Doerfert, Aaron Ballman. Online sync-ups on the following topics: Flang, vectorizer, modules, libc++, security response group, LLVM/offload, C/C++ language working group, LLVM area team, classic flang, SPIR-V, OpenMP, infrastructure area team, LLVM memory safety. For more details see the LLVM calendar , getting involved documentation on online sync ups and office hours . On the forums Alex Zinenko, on on behalf of the MLIR area team announced the roles of team members and introduced the group , and Renato Golin share dminutes from the first meeting . Renato Golin shared notes from the tensor compiler design group . Yuta Mukai proposed a new pass for write-allocate evasion . Pater Waller shared a graph of the speedup of clang build with PGO and BOLT . Krzysztof Parzyszek proposes updating Flang to follow LLVM’s recommendation of using early exits . LLVM commits A new !match operator was added to TableGen to do regex matching. 376e3b6 . A new hook was added to scale the register spill weight by a target-specific factor, and used for RISC-V. The reasoning is that different register classes have different spill costs (as noted in the commit, for RISC-V vector registers with LMUL > 1 are more expensive than when LMUL=1 ). 08a3c53 . Assembler/disassembler support was implemented for Xtensa MAC16. 69527b0 . The SLP vectorizer learned a new “SplitVectorize” mode where it will split vectorised operations by opcode, reducing register pressure (see the commit message for an example). 1008539 . A new -cost-kind=all flag can now be used to print output of all cost model kinds. cdf1833 . The cost model for early exit loops in the loop vectorizer was improved. 26ecf97 . LLVM’s code review documentation now covers upstreaming changes to LLVM from a downstream project. 77b55c7 . A new AdvisoryLock interface was added to Support. d8dfdaf . Optimisations were implemented for SystemZ vector comparison, widening and high-word vector multiply, and zero/sign extension. 7af3d39 , cdc7864 , 4a4987b . The instructions on cross-compiling LLVM were totally rewritten, and have been tested when targeting 32-bit Arm, AArch64, or 64-bit RISC-V from an x86_64 host. ba11e1e . Clang commits By default Clang now uses the in-tree LLVM SPIR-V backend to generated SPIR-V binaries, rather than invoking the external llvm-spirv tool. 919d293 . alpha.webkit.UnretainedLambdaCapturesChecker, alpha.webkit.NoUnretainedMemberChecker, alpha.webkit.UnretainedCallArgsChecker, alpha.webkit.RetainPtrCtorAdoptChecker, and alpha.webkit.ForwardDeclChecker were added. 5c3b059 , c8ec807 , caf3018 , be9ca85 . 4dcba5e . ClangIR flattening support was committed (a pass that ensures the ClangIR CFG is flat). 701148f . __builtin_elementwise_exp10 was added. 7decd04 . The process for proposing an extension to Clang was documented. 1d89d7d . Other project commits Flang’s FrontendActions.cpp was split in order to decrease the maximum compilation time and memory usage of a single translation unit (it was one of the biggest compilation units). Additionally, precompiled headers are now used to further reduce memory usage and compilation time. 0c7e895 , 0c5eb4d . Documentation was added for the LLVM libc UEFI target. 4e841d7 . As part of porting LLDB to AIX, support for NativeProcess was implemented. ec95ce3 . Module flags support was added to MLIR’s LLVMIR dialect. 29a0000 . Subscribe at LLVMWeekly.org . | 2026-01-13T09:30:34 |
https://llvmweekly.org/issue/598 | LLVM Weekly - #598, June 16th 2025 LLVM Weekly - #598, June 16th 2025 Welcome to the five hundred and ninety-eighth issue of LLVM Weekly, a weekly newsletter (published every Monday) covering developments in LLVM, Clang, and related projects. LLVM Weekly is brought to you by Alex Bradbury . Subscribe to future issues at https://llvmweekly.org and pass it on to anyone else you think may be interested. Please send any tips or feedback via email: asb@asbradbury.org , or Mastodon: @llvmweekly@fosstodon.org / @asb@fosstodon.org , or Bluesky: @llvmweekly.org / @asbradbury.org . News and articles from around the web and events The first Bristol UK LLVM/MLIR meetup will take place on 2nd July . An MLIR Compiler School and Workshop will take place in Cambridge UK, September 8th-12th . Applications are open for the US LLVM Developers' Meeting student travel grants. According to the LLVM Calendar in the coming week there will be the following: Office hours with the following hosts: Phoebe Wang, Johannes Doerfert, Aaron Ballman. Online sync-ups on the following topics: MLIR C/C++ frontend, ClangIR, pointer authentication, vectorisation, security response, OpenMP, C/C++ language working group, Flang, RISC-V, LLVM embedded toolchains. For more details see the LLVM calendar , getting involved documentation on online sync ups and office hours . On the forums Uzair Nawaz and “sribee8” wrote a proposal on adding widechar support to LLVM libc . Aaron Ballman proposed removing the PSTL top-level project as development appears to have ceased. Félix Cloutier started a discussion about correctness issues if a bool has a value assigned to it other than 0 or 1 (e.g. via memcpy). Antonio Frighetto proposed adding a dead_on_return attribute which indicates the memory point to by the argument is dead upon function return. Caroline Concatto posted a proposal for improving handling of the AArch64 FPMR state register used by FP8 intrinsics . LLVM 20.1.7 was released . This is expected to be the last 20.1.x released Martin Storsjö started a thread about PGO for cross compilation . Jonas Devlieghere proposed adding Model Context Protocol (MCP) support to LLDB . Roy Margalit proposes the robustness sanitizer , aiming to complement TSan. Sjoerd Meijer notes that loop interchange is ready to be enabled . Paschalis Mpeis posts about adding a new AArch64 BOLT buildbot and improving testing . LLVM commits PatLeaf can now be imported in GISel. f3ffee6 . The IR autoupgrader can now convert old debug-info. 3d7aa961 . LLVM’s MC layer now prefers foo = bar rather than .set foo bar , unless overridden by the target.. 28bda77 . The RISC-V backend now supports memcmp expansion for vectors. 4903c11 . Clang commits LoongArch now supports __bf16 . 0ed5d9a . Clang documented its behaviour for underspecified object declarations. b896d26 . After an RFC discussion, delayed typo correction was removed from Clang. 9eef4d1 . Clang’s build system no longer passes -fno-strict-aliasing when building with GCC. 4ed10db . A JSON generator was added for clang-doc. 1c3320c . Other project commits Flang’s CLI now accepts -W[no-]feature flags. bf60aa1 . wmemmove and ioctl were implemented in LLVM’s libc. b184672 , 4039fdb . libcxx’s ABI guarantees were documented. f2fede6 . -z dynamic-undefined-weak was implemented in the LLD ELF linker. 07dad4e . Subscribe at LLVMWeekly.org . | 2026-01-13T09:30:34 |
https://llvmweekly.org/issue/562 | LLVM Weekly - #562, October 7th 2024 LLVM Weekly - #562, October 7th 2024 Welcome to the five hundred and sixty-second issue of LLVM Weekly, a weekly newsletter (published every Monday) covering developments in LLVM, Clang, and related projects. LLVM Weekly is brought to you by Alex Bradbury . Subscribe to future issues at http://llvmweekly.org and pass it on to anyone else you think may be interested. Please send any tips or feedback to asb@asbradbury.org , @llvmweekly or @asbradbury on Twitter, or @llvmweekly@fosstodon.org or @asb@fosstodon.org . News and articles from around the web and events Registration for the 2024 LLVM Developers' Meeting will close on October 11th . Also, volunteer session moderators are being sought. Min-Yih Hsu write a blog explaining RVVBitsPerBlock in the RISC-V LLVM backend (which of course by necessity explains a lot more about how codegen for the RISC-V vector extension works!). Tomas Vondra blogged about applying BOLT to Postgres , exploring the performance gains achieved on pgbench . Vinicius Espindola wrote on the LLVM blog about their GSoC project: ABI lowering in ClangIR . Arm engineers blogged about their contributions to LLVM in the 19 release . LLVM 19.1.1 was released . Slides I presented at the RISC-V Summit Europe on supporting custom RISC-V extension in LLVM are now online (apologies, it wasn’t recorded so no video to link to). The next LLVM meetup in Berlin will take place on October 23rd and will feature Valentin Haenel discussing Numba and llvmlite. A Sydney LLVM meetup will take place on October 10th . The next LLVM meetup in Munich will take place on October 30th . Thanks to work from Fraser Cormack, a lexer for LLVM’s TableGen is now merged into Python’s pygments syntax highlighting library and should be in the next release. According to the LLVM calendar in the coming week there will be the following: Office hours with the following hosts: Alina Sbirlea, Kristof Beyls, Johannes Doerfert. Online sync-ups on the following topics: MLIR C/C++ frontend, pointer authentication, MemorySSA, new contributors, OpenMP, Flang, SPIR-V, BOLT, RISC-V, MLIR, LLVM embedded toolchains. For more details see the LLVM calendar , getting involved documentation on online sync ups and office hours . On the forums Tom Stellard sought ideas for how best to remove test binaries from the git repo , motivated by a desire to avoid attacks where someone modifies the build system in a subtle way that executes one of the binaries rather than reading them as test input. Stella Laurenzo started a discussion on rethinking MLIR’s approach to low precision FP types . Farzon Lotfi proposed allowing the Scalarizer pass to scalarize vectors returned in structs . Tom Stellard is intending to archive some old repositories in the LLVM organisation on GitHub . As noted in the replies, this is an easily reversible operation. Chaitanya Shahare shared that the development version of the in-progress LLVM website redesign is now live at www-new.llvm.org . Slides and a recording of the recent MLIR meeting on XLA indexing maps are now available . Todd Snider started an RFC discussion on a .symtab_meta , a new representation for metadata associated with a symbol . Jason Molenda has a proposal to revise the LLDB private ReadMemory APIs . LLVM commits A new (off by default) size-aware machine block placement strategy was introduced, which aims to reorder blocks to the number of fall-through jumps is maximised. 9016f27 . The WebAssembly type checker was further improved, with support added for blocks with input parameters and checking for br_if . a268bda . X86InstComments printing logic was made smarter, gaining the ability to print simplified expressions for vpternlog semantics. aa02b76 . A comma-separated list of mangled vtable names can now be given to the IndirectCallPromotion pass, and it will skip vtable-based comparisons for these. 34f0edd . APFloat support was added for “E8M0” from the Open Compute Project microscaling formats specification. 99f527d . LLVMFrontendAtomic was added as a helper to emit libcalls for atomicrmw instructions that can’t be emitted (e.g. for complx types). aec87a2 . Basic definitions were added for Armv9.6-A. d0756ca . CODE_OWNERS.TXT was moved over to Maintainers.md . bf488ed . Clang commits The RealtimeSanitizer documentation was updated to cover the supported runtime flags. 9d4ddf3 . clang-tidy gained a bugprone-tagged-union-member-count checker. 7b8f7be . A new static analyzer check was added to warn when the denominator in a division operation is a potentially attacker controlled (“tainted”) value. In such cases, an attacker may be able to cause a divide by zero. 09b8dbfa . Implementation of P0522 “relaxed template template argument matching rules” was completed. 6afe567 . CMake cache files were added for building a toolchain targeting Hexagon. ea62db0 . Other project commits The libcxx modulemap was rewritten to have fewer top-level modules, leading to a drastic improvement in compile time in some cases. 41145fe . Branch Target Identification (BTI) aware long branch thunks are now supported for AArch64 in the ELF LLD. c4d9cd8 . The documentation for contributing to lldb-dap was improved. 6c137b7 . The f8E8M0FNU type proposed in the Open Compute MX Specification was added to MLIR. 3f9caba . Subscribe at LLVMWeekly.org . | 2026-01-13T09:30:34 |
https://llvmweekly.org/issue/580 | LLVM Weekly - #580, February 10th 2025 LLVM Weekly - #580, February 10th 2025 Welcome to the five hundred and eightieth issue of LLVM Weekly, a weekly newsletter (published every Monday) covering developments in LLVM, Clang, and related projects. LLVM Weekly is brought to you by Alex Bradbury . Subscribe to future issues at http://llvmweekly.org and pass it on to anyone else you think may be interested. Please send any tips or feedback via email: asb@asbradbury.org , or Mastodon: @llvmweekly@fosstodon.org / @asb@fosstodon.org , or Bluesky: @llvmweekly.org / @asbradbury.org . News and articles from around the web and events As a reminder, today is the last full day to vote in the LLVM Area Team Elections . GNU Binutils 2.44 was released, notably deprecated the gold linker . Andres Salamanca blogged about LLVM’s SimplifyCFG pass . Antonin Décimo writes on the Tarides blog about using clang-cl with OCaml 5 . The next LLVM Bay Area meetup will take place on 24th February . The next Cambridge (UK) compiler social will take place this Wednesday 12th February . Be sure to register if you would like ot attend. Many thanks to the organisers - hopefully I’ll see some of you there! The next Portland LLVM social will take place on February 13th . There’s a poll for choosing the exact location. According to the LLVM calendar in the coming week there will be the following: Office hours with the following hosts: Aaron Ballman, Alexey Bader, Alina Sbirlea, Kristof Beyls, Johannes Doerfert, Online sync-ups on the following topics: alias analysis, pointer authentication, OpenMP, Flang, BOLT, RISC-V, LLVM libc. For more details see the LLVM calendar , getting involved documentation on online sync ups and office hours . On the forums Ilya Biryukov proposed an LLVM working group on memory safety . Ideas for Google Summer of Code projects have started to be posted. See the GSoC 2025 tag on Discourse for project ideas such a Bfloat16 in LLVM libc, improving Clang documentation parsing, and rust-enzyme improvements. Nikita Popov proposed an ABI lowering library for LLVM which can be used by frontends to produce LLVM IR for a specific target with appropriate call ABI lowering. Rahul Joshi is checking there are no downstream users for TargetIntrinsicInfo and shared a PSA on API breaking changes for named operands in MachineIR . LLVM Foundation board minutes from December and from January have now been posted. River Riddle explains the purpose of a dialect attribute in MLIR . “bubblepipe” kicked off a discussion about the tuple type in MLIR . Joshua Cranmer posted a new fast-math flags RFC, this time focusing on the semantics of contract . Stella Laurenzo is taking a break from the MLIR project and shared some thoughts and advice for future facilitation of the project. Thank you Stella for all of your contributions! Samuel Tebbs started an RFC discussing on modeling register pressure on a per-VPlan basis in the LoopVectorizer . Timm Bäder is looking for help with the bytecode interpreter in Clang and has a series of starting points for how you can do so. LLVM commits Xtensa windowed registers are now supported. f6578c3 . A CMake flag can now be used to avoid building LLVM’s telemetry framework (note that the telemetry code is inert by default anyway). bac62ee . MachineCopyPropagation, PostRAScheduler, RenameIndependentSubregs, and a handful of other passes were ported to the new pass manager. 4313345 , 44f638f , f77f777 . Vector predicated loads/stores are now supported in the InterleavedAccessPass. 005b23b . The guidance on testing buildbot configurations locally was enhanced with advice on working around compatibility issues with Python 3.13 and dealing with builder workflows that rely on scripts from llvm-zorg (where you may want to test not-yet-upstreamed modifications). 96d46c6 . llvm.vector.(de)interleave{3,5,7} intrinsics were introduced. 5a1e16f . A series of patches related to the loop interchange RFC have landed in recent weeks, with the goal of addressing the compile-time increase caused by enabling loop interchange. d15f3e8 , 5d281a4 , 1eaa179 . Clang commits An initial ClangIR to LLVM IR lowering pass was added. It is a very minimal starting point, supporting lowering global integer and floating point variables only. 622ee03 , 2b5cc89 . The new -Wunique-object-duplication warning will warn about objects which should only exist once per program but which may get duplicated when built into a shared library. dfc2873 . Initial support for the OpenACC ‘atomic’ construct was added. 99a9133 . Clang builtins were switched to using string tables. cd269fe , 1cb979f , 64ea3f5 . -ftime-trace can now break down analysis time of the static analyzer. c1d5be8 . A BreakBeforeTemplateCloser and a BinPackLongBracedList option was added for clang-format. d2b45ce , e0a21e2 . -fprofile-continuous enables a profiling mode where profile counter updates are continuously synced to a file. 8e61aae . Other project commits MLIR’s ViewOpGraph GraphViz output was made much prettier ( screenshot ). 1f67070 . libFortranRuntime.a was renamed to libflang_rt.runtime.a. 5c8c2b3 . An alternative algorithm for printf binary to decimal floating point conversion was added to LLVM’s libc. It is intended to be used in environments that can’t afford the space cost of the table lookup required by the default Ryū algorithm. b53da77 . libc++ gained new benchmarks for associative containers. 1d319df . The LLD ELF linker gained new options for optimising section layout (for instance, based on profile data). 6ab034b . LLDB’s documentation on remote testing was updated. 5d738b2 . A lexer was committed to LLDB for the “Data Inspection Language” (DIL), intended to be used for variable inspection (see the RFC ). d9a7498 . MLIR’s LLVM dialect now supports global aliases. 4fb96f2 . Subscribe at LLVMWeekly.org . | 2026-01-13T09:30:34 |
https://llvmweekly.org/issue/570 | LLVM Weekly - #570, December 2nd 2024 LLVM Weekly - #570, December 2nd 2024 Welcome to the five hundred and seventieth issue of LLVM Weekly, a weekly newsletter (published every Monday) covering developments in LLVM, Clang, and related projects. LLVM Weekly is brought to you by Alex Bradbury . Subscribe to future issues at http://llvmweekly.org and pass it on to anyone else you think may be interested. Please send any tips or feedback via email: asb@asbradbury.org , or Mastodon: @llvmweekly@fosstodon.org / @asb@fosstodon.org , or Bluesky: @llvmweekly.org / @asbradbury.org . News and articles from around the web and events The deadline for submissions to the LLVM dev room at FOSDEM has been extended to December 8th . The next Cambridge (UK) Compiler Social will take place on 4th December featuring talks “Formal Semantics for MLIR Dialects” by Mathieu Fehr and “Arcilator: fast and cycle-accurate hardware simulation in CIRCT” by Martin Erhart. The next Zurich LLVM social will take place on 10th December and feature a talk on “embedding domain-specific languages in C or C++ with Polygeist”. A Winter School on the MLIR compilation infrastructure is being organised in Paris in the last week of January . Antmicro blogged about optimising LLVM for machine-generated C++ code as produced by Verilator. According to the LLVM calendar in the coming week there will be the following: Office hours with the following hosts: Anastasia Stulova, Quentin Colombet, Johannes Doerfert, Renato Golin. Online sync-ups on the following topics: MLIR C/C++ frontend, pointer authentication, MemorySSA, new contributors, OpenMP, C/C++ language working group, Flang, SPIR-V, RISC-V, MLIR open meeting, embedded toolchains, HLSL, MLGO. For more details see the LLVM calendar , getting involved documentation on online sync ups and office hours . On the forums Renato Golin provided an update on the MLIR project charter and restructuring survey noting that the survey is now closed as it has been flagged as violating Google’s terms of service, with no functional route to ask for manual review. Some respondents are concerned that people may have been hoping to respond after the thanksgiving break and now won’t be able to. Nuno Lopes started a follow-up thread on removing undef from tests , including statistics on the use of undef over time. The thread discussues how to remove more cases where undef is used when it shouldn’t be, and to flag new additions. Tim Gymnich proposed adding floating point type information to LLT in order to allow GlobalISel to diffrentiate between different floating point formats with the same bit-width (e.g. bf16 vs half). David Spickett shared an RFC for supporting AArch64 guarded control stack in LLDB . Djordje Todorovic updated the thread on the autocheck source code analysis tool so share that at this time they don’t see a path to open sourcing it due to restrictions related to the relevant standards, but invited anyone with experience with such issues who would like to help to reach out. Stella Laurenzo issued a PSA on upcoming changes to MLIR Python binding dependencies (as noted in the thread, this shouldn’t affect you unless you maintain an out of tree project that uses the bindings as prt of a larger super-project). Djordje Todorovic posted an RFC on adding support for the MIPS P8700 RISC-V CPU and its extensions. Aleksei Vetrov is seeking feedback on a proposal to introduce a callsite_wrapper attribute to Clang , which would be used in the Linux kernel to collect information about memory allocations and attribute it to the place where it originated. Peter Collingbourne would like to introduce a new feature to LLD to help control code-size dependent measurement bias , specifically to counteract measurement issues as flagged in papers such as this one (where link order strongly affected results). LLVM commits llvm-profdata merge was made substantially faster. ff7b42c . SimplifyCFG learned to hoist load/store with conditional faulting for X86. 2568e52 . The SLEEF vector library is now supported for the RISC-V target. 93caee1 . Tail call optimisation in the machine outliner is now support for RISC-V. 2906232 . The process for the requesting admin access to the CI/CD infrastructure on GitHub was documented. 5bdcaf1 . A YAML-based deserialisation of MemProf profiles was added. e98396f . The merge-json.py helper will merge the compile_commands.json from the runtimes build with the one from the main build. 4148aa6 . SPIR-V type inference was improved. b5132b7 . Clang commits The new [[clang::no_specializations]] attribute can be used to warn users that a specific template shouldn’t be specialised. 0604d13 . The unix.cstring.NotNullTerminated and unix.chroot checkers are no longer marked as alpha. 4dfa021 , e034c4e . Other project commits libc++ coding guidelines were documented. 5971647 . Runtimes can now again be built against an installed LLVM tree. 3cb2852 . Flang gained a new pass to rewrite omp.loop to semantically equivalent operations. 81f544d . -mlir-disable-diagnostic can be used to make mlir-opt stop emitting diagnostic information. 1f422dc . The ConvertMeshToMPIPass was added to MLIR. 79eb406 . Subscribe at LLVMWeekly.org . | 2026-01-13T09:30:34 |
https://llvmweekly.org/issue/583 | LLVM Weekly - #583, March 3rd 2025 LLVM Weekly - #583, March 3rd 2025 Welcome to the five hundred and eighty-third issue of LLVM Weekly, a weekly newsletter (published every Monday) covering developments in LLVM, Clang, and related projects. LLVM Weekly is brought to you by Alex Bradbury . Subscribe to future issues at https://llvmweekly.org and pass it on to anyone else you think may be interested. Please send any tips or feedback via email: asb@asbradbury.org , or Mastodon: @llvmweekly@fosstodon.org / @asb@fosstodon.org , or Bluesky: @llvmweekly.org / @asbradbury.org . News and articles from around the web and events The CFP for the MLIR workshop at the EuroLLVM developer meeting is open , with a deadline of 9th March for submissions. Alex Bradbury wrote a short post on configuring ccache for use with multiple Clang/LLVM builds in different directories . Shafik Yaghmour blogged about what you need to know when optimisations change the behaviour of your C++ . I’ll preface the normal rundown of LLVM events / office hours with a PSA that the USA enters daylight savings time this coming Sunday 9th March, while UK/Europe and potentially other areas don’t follow suit until March 30th. According to the LLVM calendar in the coming week there will be the following: Office hours with the following hosts: Quentin Colombet, Johannes Doerfert, Renato Golin. Online sync-ups on the following topics: Flang, MLIR C/C++ frontend, C++ modules, LLVM area team, LLVM/Offload, classic flang, Clang C/C++ language working group, SPIR-V, infrastructure area team, LLVM memory safety working group, HLSL, MLGO. For more details see the LLVM calendar , getting involved documentation on online sync ups and office hours . On the forums Javed Absar shared an MLIR PSA on deprecating linalg named elementwise ops . Owen Rodley proposed keeping GlobalValue GUIDs stable . LLVM 20.1.0-rc3 was released Sam Elliott started a thread to try to clarify the policy on updates to code imported into the llvm-test-suite repo . Cristian Assaiante shared some performance regressions in SPEC 2017 benchmarks observed on x86_64 . The February 2025 LLVM Foundation board meeting minutes have been posted . Joseph Huber posted an RFC thread on handling math libcalls with LTO . MLIR News #74 is now available Luca Haaks is a PhD student in management science at LMU Munich and is looking for LLVM contributors to interview as part of research into coordination dynamics in open source software communities. LLVM commits Initial RISC-V vector support was added to llvm-exegesis. c253e5c . Telemetry is no longer disabled by disabling building of the library (which led to awkwardness like #ifdef s), but by modifying LLVM_ENABLE_TELEMETRY . If this is set to false, telemetry cannot be enabled and no data can be collected. 159b872 . The LangRef now clarifies that the pointer after an object must be valid. 47822c8 . LLVM’s coding standards document coverage on anonymous namespaces was reworked to cover visibility more broadly. 5bddadf . Assembler support was added for the Qualcomm RISC-V Xqcilia (large immediate arithmetic) and Xqccmp (16-bit push/pop and double moves) vendor extensions. Also for the Rivos XRivoxVisni (vector integer small new instructions) vendor extension. 538b898 , 8039f8e , 5066d7b . DISubrangeType was added, motivated by Ada. e298fc2 . MergeFuncs no longer introduces calls to linkonce_odr or weak_odr functions as they may introduce an infinite call cycle. f10e0f7 . The LangRef definition of llvm.minnum and llvm.maxnum was clarified. 363b059 . -print-inst-addrs and -print-inst-debug-locs and be used to print addresses and debug locations of instructions when dumping. 0ebf7b4 . Clang commits __attribute__((format_matches)) is now implemented, allowing the compiler to check that a format string matches its arguments. c710118 . A minimal cir-opt tool was added in order to allow tests to be written for CIR dialect parsing. 607a1f2 . alpha.webkit.UnretainedLocalVarsChecker was added. cec3507 . creduce-clang-crash.py was renamed to reduce-clang-crash.py and now supports cvise alongside creduce. 59cee03 . [[clang:atomic]] attributes are now supported for controlling atomic code generation. 240f226 . Other project commits BOLT gained support for two new profile quality statistics. 7e33beb . The clang-opt-bisect analyzer tool was removed from Dexter. 1ed359e . Initial UEFI headers were added to LLVM’s libc. 9b6d0d7 . NaN propagation lowering was implemented in MLIR’s tosa-to-linalg. cf3b036 . Subscribe at LLVMWeekly.org . | 2026-01-13T09:30:34 |
https://llvmweekly.org/issue/533 | LLVM Weekly - #533, March 18th 2024 LLVM Weekly - #533, March 18th 2024 Welcome to the five hundred and thirty-third issue of LLVM Weekly, a weekly newsletter (published every Monday) covering developments in LLVM, Clang, and related projects. LLVM Weekly is brought to you by Alex Bradbury . Subscribe to future issues at http://llvmweekly.org and pass it on to anyone else you think may be interested. Please send any tips or feedback to asb@asbradbury.org , @llvmweekly or @asbradbury on Twitter, or @llvmweekly@fosstodon.org or @asb@fosstodon.org . News and articles from around the web and events Anton Korobeynikov wrote on the LLVM blog about LLVM in Google Summer of Code 2023 and 2024 . The Unreal Engine blog covers their addition of transactional memory semantics to C++ , using a Clang/LLVM based toolchain. A new LLVM meetup is starting in the Seattle-Belevue area, with the first scheduled for 26th March . Include What You Use 0.22 was released . According to the LLVM calendar in the coming week there will be the following (note: US is still ahead of most countries in entering daylight savings time so meeting times may be different to usual): Office hours with the following hosts: Phoebe Wang, Johannes Doerfert. Online sync-ups on the following topics: Flang, pointer authentication, SYCL, SPIR-V, libc++, security group, new contributors, LLVM/offload, C/C++ language working group, loop optimisations, classic flang, floating point, OpenMP in Flang, MLIR, PowerPC. For more details see the LLVM calendar , getting involved documentation on online sync ups and office hours . On the forums Tom Stellard is seeking input from users of personal access tokens for LLVM GitHub interactions . Mehdi Amini posted a new RFC for adding a warning when bypassing premerge testing . Michael Jones proposed “project hand in hand” , aiming to increase code sharing between LLVM’s libc and libcxx subprojects. Justin Stitt kicked off an RFC discussion on adding a ‘wraps’ attribute to Clang for granular integer overflow handling , noting limitations with the current __attribute__((no_sanitizer("signed-integer-overflow"))) approach. Fangrui Song posted an RFC on RELLEB, a compact relocation format for ELF and supporting compressed SHT_SYMTAB / SHT_STRTAB for ELF . Vitaly Buka proposed adding an llvm.experimental.hot() intrinsic . Krzysztof Drewniak shared an RFC on adding new microscaling float scalars to APFloat and FloatType . There was another discussion about custom float types in MLIR this week too. Wentao Zhang outlined some issues with TableGen HWMode and made a proposal to address them . Amrit Bhogal suggested making __builtin_dump_struct expand typeof declarations . Mishal Shah notes that the “Green Dragon” Jenkins infrastructure is migrating to a new cloud services provider . Michael Buch shared a proposal for handling [[no_unique_address]] in LLDB . LLVM commits The necessary LLVM-side support was added for the BPF ‘arena’ feature, allowing access to a memory region shared by both the BPF program and user space. 2aacb56 . llvm-debuginfo-analyzer now supports WebAssembly’s binary format. b19cfb9 . The new LLVM_PARALLEL_TABLEGEN_JOBS CMake option allows the number of tablegen jobs that can run in parallel to be restricted. 9228859 . InstSimplify was updated to make use of range attributes to simplify comparisons. a3b5250 . The llvm.coro.await.suspend intrinsic was implemented. f786881 . llvm::{min,max}_element was added to LLVM’s STLExtras.h. fab2bb8 . The option for running lit testsuites in parallel was reverted. 8846b91 . IRBuilder learned to fold some binary intrinsics. 1411452 . MacroFusion gained support for commutable instructions. b890a48 . LLVM_ENABLE_FATLTO can now be used to build LLVM with -ffat-lto-objects . 43fc921 . Clang commits A basic set of AArch64 pointer authentication Clang builtins and intrinsics are now supported (and detailed documentation on ptrauth added!). 0481f04 . The rsqrt, isinf, and clamp intrinsics were implemented for HLSL. 8f9ee39 , d192b643 , 8386a38 . The -Wreturn-mismatch warning was added. 8467457 . __builtin_arm_trap was defined for AArch64, allowing a compile-time constant payload. 4299c72 . -m[no-]unaligned-access was removed for RISC-V and LoongArch, -m[no-]strict-align should be used instead. cd07125 . Work on InstallAPI with the ability added to collect C++ declarations. 2c93bec . Other project commits A new generic Alarm class was added to LLDB to aid coalescing progress reports. f01a32f . MLIR’s LLVM dialect gained support for recursive DITypes. 1e8dad3 . Fortran::common::optional and Fortran::common::reference_wrapper implementation was added to the Flang runtime. 71e0261 , d8f97c0 . LLVM’s libc documentation for GPU testing was updated. 6818c7b . LLD gained the --compress-sections option to compressed matching non-SHF_ALLOC sections. f1ca2a0 . Subscribe at LLVMWeekly.org . | 2026-01-13T09:30:34 |
https://llvmweekly.org/issue/581 | LLVM Weekly - #581, February 17th 2025 LLVM Weekly - #581, February 17th 2025 Welcome to the five hundred and eighty-first issue of LLVM Weekly, a weekly newsletter (published every Monday) covering developments in LLVM, Clang, and related projects. LLVM Weekly is brought to you by Alex Bradbury . Subscribe to future issues at http://llvmweekly.org and pass it on to anyone else you think may be interested. Please send any tips or feedback via email: asb@asbradbury.org , or Mastodon: @llvmweekly@fosstodon.org / @asb@fosstodon.org , or Bluesky: @llvmweekly.org / @asbradbury.org . News and articles from around the web and events The /r/cpp moderator’s Hagenberg ISO C++ committee trip report is up . See especially the update on C++ profiles. The next Portland LLVM meetup was pushed out a week to February 20th . According to the LLVM calendar in the coming week there will be the following: Office hours with the following hosts: Phoebe Wang, Aaron Ballman, Johannes Doerfert. Online sync-ups on the following topics: flang, vectoriser, libc++, security working group, LLVM area team, LLVM/Offload, classic flang, C/C++ language working gropu, SPIR-V, floating point, OpenMP for flang, instructure area team. For more details see the LLVM calendar , getting involved documentation on online sync ups and office hours . On the forums The results of the LLVM Area Team Elections are now up . Thank you to everyone who stood, and congratulations to those elected. Arthur Eubanks posted an RFC on the new pass manager pipeline construction design . “The new pass manager for the codegen pipeline has some implementation in-tree, but it’s been pretty organic growth so far and I’d like to properly design it out with feedback from the community (especially those more familiar with the codegen pipeline) before we get into a state where it’s too hard to change design. This focuses on how we’ll create the codegen pipeline programmatically in code, which is the main challenge so far.” LLVM 20.1.0-rc2 was released . Ron Dahan proposed expanding the experimental histogram intrinsic . Andrzej Warzynski gives a heads-up that MLIR’s tensor.pack and tensor.unpack ops are moving to linalg this week . As the commit access criteria thread seems to have reached consensus , Tom Stellard has moved it to PR. Balazs Benics took a moment to recognise the progress that the clang static analyzer contributor community has made . Congratulations and thank you everyone! Rahul Joshi started a conversation on clarifying LLVM’s style guide for using static when possible . More GSoC ideas are appearing. See the GSoC category and gsoc2025 tag . LLVM commits Guidance on handling large formatting changes within PRs was clarified. f845497 . The LoongArchMergeBaseOffset pass learned to merge base and offsets for tle-le code sequences. 0b5c318 . Guidance on backporting fixes to the release branch was clarified. 308d286 . The unused TargetIntrinsicInfo class was removed. 0f674cc . The llvm.sincospi intrinsic was introduced. 701223a . The long-deprecated OperandMatchResultTy enum was removed. d222488 . An errno memory location kind was introduced to IR. ff585fe . Discord invite links are now placed alongside links to Discord channels (as the channel links aren’t usable unless you joined the server via invite at some point). db2953d . A FatLTOCleanup pass was added. 63c1be7 . The mul constant expression was removed. d8b2e43 . A generic OoO RISC-V scheduling model was added. 7eadc19 . Clang commits __builtin_assume_dereferenceable was introduced, allowing you to provide the optimiser with knowledge that the pointer argument is dereferenceable up to at least the specified number of bytes. 50d10b5 . Combinations of -f(no-)strict-overflow , -f(no-)wrapv , f(no-)wrapv-pointer are now handled in the same way that GCC does (process left-to-right and pick whatever is active at the end). 783275e . Declaration attributes on void parameters is no longer allowed. aeeeeab . Documentation was written on using perf and uftrace to debug performance issues in Clang. 1337b0f . The clang static analyzer gained a new assume-at-least-one-iteration option. edbc1fb . HLSL initialisation list support was implemented. 761d422 . Other project commits LLDB’s breakpoint handling behaviour has been changed. It now only sets a thread’s stop reason to breakpoint-hit when the instruction has actually been executed / the breakpoint has been triggered. b666ac3 . MLIR’s deprecated buffer-deallocation pass was removed. 213917b . Flang now generates proper ABI flags for RISC-V in the emitted ELF. 8da8ff8 . It should now be possible to build flang against an installed MLIR. c30a7f4 . strftime was implemented in LLVM’s libc. 398f865 . Additional linker relaxations were implemented in LLD for LoongArch. 6c54ab5 . Subscribe at LLVMWeekly.org . | 2026-01-13T09:30:34 |
https://llvmweekly.org/issue/572 | LLVM Weekly - #572, December 16th 2024 LLVM Weekly - #572, December 16th 2024 Welcome to the five hundred and seventy-second issue of LLVM Weekly, a weekly newsletter (published every Monday) covering developments in LLVM, Clang, and related projects. LLVM Weekly is brought to you by Alex Bradbury . Subscribe to future issues at http://llvmweekly.org and pass it on to anyone else you think may be interested. Please send any tips or feedback via email: asb@asbradbury.org , or Mastodon: @llvmweekly@fosstodon.org / @asb@fosstodon.org , or Bluesky: @llvmweekly.org / @asbradbury.org . News and articles from around the web and events Thomas Fransham blogged about their GSoC project to add LLVM and Clang plugin support for Windows . Alex Denisov and Amir Rajan blogged about Lightstorm, a minimalistic Ruby compiler using MLIR . According to the LLVM calendar in the coming week there will be the following: Office hours with the following hosts: Phoebe Wang, Johannes Doerfert. Online sync-ups on the following topics: pointer authentication, vectoriser improvements, security group, new contributors, OpenMP, C/C++ lanugage working group, Flang, floating point, RISC-V, LLVM libc, MLIR. For more details see the LLVM calendar , getting involved documentation on online sync ups and office hours . On the forums Chris Bieneman announced that election test emails have gone out (and later that a second test went out ). Reid Kleckner posted a timelinine for the planned elections . Michal Paszkowski proposed promoting SPIR-V to an official target . Renato Golin mooted a new version scheme for LLVM , moving towards yearly releases. Most respondents so far stated a preference for at least two releases per year. Stella Laurenzo proposes blackout period for controversial MLIR design decisions until the new year , warning that it’s been particularly active lately and some people are nearing burnout. Ramkumar Ramachandra shares the good news that Alive2 now supports X86 vector intrinsics . Carlos Galvez started a discussion on deprecation warnings for clang-tidy . Hendrik Hübner started a discussion on potentially adding a PDP11 target to LLVM. Peter Smith shared further thoughts on the printf code size optimisation thread following a discussion at the LLVM embedded rountable. Oren Benita Ben Simhon advertised a new LLVM meetup group in Israel . Wang Pengcheng wondered about changing the default RISC-V configuration to rva23u64 . Sergei Barannikov would like to add support for TableGen'erating SDNode descriptions and has had nothing but positive feedback so far. Rolf Morel posted a detailed MLIR RFC on introducing a linalg.contract op . Andrzej Warzynski kicked off an MLIR RFC discussion on restrucing the usage of 0-D vectors in the vector dialect . Elizaveta Noskova wrote up a description of a series of patches to support splitting save and restore points during shrink-wrapping . Mikhail Gudim linked to an alternative approach . LLVM commits LLVM now has a guide on undefined behaviour. 0100c63 , 03661fb . The number of dynamic relocations in a clang binary was reduced by ~7000 due to reworking of the Option library. dd647e3 . Apple Silicon specific runtime loop unrolling preferences were implemented in the AArch64 backend. 0bb7bd4 . The AMDGPU backend gained a new “max-memory-clause” scheduling strategy. b33c807 . The RISC-V backend now supports stack clash protection and XRay. 708a478 , ea76b2d . SystemZ now supports __builtin_{setjmp,longjmp} . dc04d41 . Critical edge splitting code was moved to the dominator tree updater. 79047fa . A pre-commit check was introduced to warn about uses of undef. 19bc282 . Vararg support was implemented in the Xtensa backend. be4a183 . A wrapper for a merged string table was added to LLVM’s ADT library. ef28e96 . Tests in various backends were updated to use -mtriple rather than -march . f1987c7 , 7284902 , and more. Clang commits Clang’s driver now prioritises command line arguments over DEFAULT_SYSROOT . 737d78a . -Wdangling-capture was enabled by default. f229ea2 . Other project commits LLDB gained a formatter bytecode interpreter implemented in C++. 9a9c1d4 . The initial scaffolding for a binary analysis tool based on BOLT was committed. ceb7214 . LLVM’s libc can now be used baremetal on AArch64. 2e8ce30 . LLD now supports --randomize-section-padding , which is intended to be used in A/B experiments to control for effects such as false sharing in the cache. 64da33a . LLVM libc docs now link to LLVM dev meeting talks related to it. e5ab6e9 . LLDB learned to handle LoongArch64 hardware break/watchpoints. 6c4e70f . Subscribe at LLVMWeekly.org . | 2026-01-13T09:30:34 |
https://llvmweekly.org/issue/546 | LLVM Weekly - #546, June 17th 2024 LLVM Weekly - #546, June 17th 2024 Welcome to the five hundred and forty-sixth issue of LLVM Weekly, a weekly newsletter (published every Monday) covering developments in LLVM, Clang, and related projects. LLVM Weekly is brought to you by Alex Bradbury . Subscribe to future issues at http://llvmweekly.org and pass it on to anyone else you think may be interested. Please send any tips or feedback to asb@asbradbury.org , @llvmweekly or @asbradbury on Twitter, or @llvmweekly@fosstodon.org or @asb@fosstodon.org . News and articles from around the web and events The next Cambridge compiler social will take place on June 19th and will fature a talk “Hyperblock Scheduling for Verified High-Level Synthesis” by Yann Herklotz. The forms to volunteer for the LLVM US Dev meeting program committee, travel grant committee, or to propose a co-located workshop will close on June 21st . According to the LLVM calendar in the coming week there will be the following: Office hours with the following hosts: Phoebe Wang, Johannes Doerfert, Aaron Ballman. Online sync-ups on the following topics: pointer authentication, SPIR-V, vectorizer, security group, new contributors, OpenMP, Flang, floating point, RISC-V, MLIR, embedded toolchains. For more details see the LLVM calendar , getting involved documentation on online sync ups and office hours . On the forums Stephen Tozer provided a PSA on LLVM IR output changing from debug intrinsics to debug records . Apologies for missing this before, but Aaron Ballman provided an excellent summary of his perception of the consensus in the long-running -Ofast deprecation RFC thread . Galina Kistanova reported that the upgrade to buildbot v3.9 was successfully completed . Aaron Ballman kicked off an RFC thread on requiring that discussion of new Clang extensions to explicitly consider impact to monorepo stakeholders , using the example of __restrict on member functions impacting libcxx’s std::function . Hongjia Cao has attempted to reignite discussion on non-8-bit byte support in LLVM. Sander de Smalen proposes avoiding inlining alwaysinline functions when they cannot leagally be inlined . Alexis Engelke started an RFC discussion on the use of string view literals in the LLVM code base , noting that when Twine is used with string literal strlen may still be called. Andrew Wock proposes support for thread-local profile counters , providing benchmarks for the various options. Younan Zhang suggests adding a new GitHub issue label for fuzzer-generated issues . Tom Stellard reports that LLVM now meets all criteria to pass OpenSSF’s baseline best practices. Alexander Shaposhnikov would like to revive the numerical sanitiser . “YunFly” proposed a new pass for fusion in MLIR . Andreas Jonson would like to allow noundef metadata only on loads (enforcing this with the verifier). “Menooker” proposes adding an easy builder interface for constructing MLIR IR from C++ . Balazs Benics posted static analyzer RFCs on taming Z3 query times and making isTainted() and complex symbols friends . LLVM commits LLVM has switched to using debug records internally by default, the migration doc on the removal of debug intrinsics was updated, and IR is printed with debug records by default. dc726c3 , e19199b , 0945727 . DynamicAPInt was introduced (moved from mlir’s MPInt), providing an arbitrary precision integer library that unlike APInt doesn’t require a fixed maximum size. 76030dc . APFloat support for FP6 and FP4 data types was added. b1fe03f , 880d370 . BranchWeightMetadata was extended to track the provenance of weights. 294f3ce . All LLVM docs were updated to use debug records rather than debug intrinsics. 400d4fd . Modulo variable expansion was implemented, with support initially present for AArch64. 0c5319e . Support was added for the RISC-V indirect CSR access extensions. 2fe7238 . Basic definitions were added for the Cortex-A725 and Cortex-X925. e80c595 . The move from Chromium’s security tracker to GitHub for security issue reporting was documented. a6c1152 . A window scheduling algorithm for the machinepipeliner was implemented. b6bf402 . llvm-profgen gained support for Linux kernel perf files. 2fa6eaf . Clang commits The emitted IR for array initialisation was simplified. 12d24e0 . sizeof(pointer) handling in bugprone-sizeof-expression was improved. 546c816 . Other project commits As part of work on a freelist allocator, a Block class abstraction and freelist class was added to LLVM’s libc. 85c78d4 , 1737814 , 3bcd80a . pthread_rwlock and fdopen were implemented in LLVM’s libc. 41fecca , 0b24b47 . LLD’s build-id now defaults to a 20-byte SHA1 digest. 1d96e4b . Basic TLSDESC support for LoongArch was implemented in LLD. c4a1440 . MLIR’s arith dialect integer range optimisations pass was improved. 4722911 . MLIR no longer merges blocks during canonicalisation by default. a506279 . Subscribe at LLVMWeekly.org . | 2026-01-13T09:30:34 |
https://penneo.com/da/real-estate/ | Ejendomsbranchen - Penneo Produkter Penneo Sign Validator Hvorfor Penneo Integrationer Løsninger Anvendelsesscenarier Digital signering Dokumenthåndtering Udfyld og underskriv PDF-formularer Automatisering af underskriftsprocesser Overholdelse af eIDAS Brancher Revision og regnskab Finans og bank Advokatydelser Ejendom Administration og HR Priser Ressourcer Vidensunivers Trust Center Produktopdateringer SIGN Hjælpecenter KYC Hjælpecenter Systemstatus LOG PÅ Penneo Sign Log ind på Penneo Sign. LOG PÅ Penneo KYC Log ind på Penneo KYC. LOG PÅ BOOK ET MØDE GRATIS PRØVEPERIODE DA EN NO FR NL Produkter Penneo Sign Validator Hvorfor Penneo Integrationer Løsninger Revision og regnskab Finans og bank Advokatydelser Ejendom Administration og HR Anvendelsesscenarier Digital signering Dokumenthåndtering Udfyld og underskriv PDF-formularer Automatisering af underskriftsprocesser Overholdelse af eIDAS Priser Ressourcer Vidensunivers Trust Center Produktopdateringer SIGN Hjælpecenter KYC Hjælpecenter Systemstatus BOOK ET MØDE GRATIS PRØVEPERIODE LOG PÅ DA EN NO FR NL Penneo Sign Log ind på Penneo Sign. LOG PÅ Penneo KYC Log ind på Penneo KYC. LOG PÅ Mindre papirarbejde, mere tid til fremragende kundeservice Penneo hjælper ejendomsmæglere og ejendomsadministrationsselskaber med at optimere dokumentunderskrift , så de kan fokusere på at levere en bedre oplevelse for lejere, købere og sælgere. UDFORSK PENNEO Forældede processer kan føre til ineffektivitet og mindre tid til kunderne Forældede dokumentunderskriftsprocesser skaber betydelig ineffektivitet. Manuelt arbejde, langsomme godkendelsesforløb og gentagne administrative opgaver mindsker produktiviteten og stjæler tid fra værdifulde kunderelationer. Ud over driftsmæssig ineffektivitet kan forældede processer også påvirke kundeoplevelsen negativt. Lejere, købere og sælgere forventer hurtige og problemfri transaktioner – men langsom dokumenthåndtering kan føre til frustration. Se, hvordan Penneo kan hjælpe dig Øg produktiviteten ved at integrere Penneo med dine værktøjer Ved at integrere Penneo med dine eksisterende værktøjer kan du eliminere besværet ved at skifte mellem platforme og spare værdifuld tid. Penneo tilbyder forudbyggede integrationer med ejendoms- og ejendomsadministrationssoftware som Unik Bolig, WebBolig, EG Bolig og EG Strato . Derudover kan du oprette integrationer, der er skræddersyet til dine behov, ved hjælp af Penneos åbne API. Se alle vores integrationer Automatiser dokumentunderskrivningen og forbedr medarbejderoplevelsen Penneo minimerer arbejdsbyrden i forbindelse med dokumentunderskrift bidrager til en bedre kundeoplevelse ved at: Automatisere underskrift af lejekontrakter, købsaftaler og andre nødvendige dokumenter. Give sikre og juridisk bindende digitale signaturer med eID’er eller pas. Giver medarbejdere og kunder mulighed for at underskrive dokumenter hvor som helst og på hvilken som helst enhed. Se alle funktioner Eliminer manuelt arbejde og luk aftaler hurtigere Med integrationer til nøgleværktøjer og automatiserede signeringsflows kan du minimere administrative flaskehalse, forbedre nøjagtigheden og forbedre kundeoplevelsen – så du kan afslutte aftaler hurtigt og effektivt. Penneo overholder GDPR, har ISO 27001- og 27701-certificeringer og bruger kryptering til at beskytte dine data og dokumenter på alle trin. Med Penneo kan du oprette kvalificerede elektroniske signaturer (QES) ved hjælp af pas, norsk BankID, itsme® eller .beID, samt avancerede elektroniske signaturer (AdES) med MitID, MitID Erhverv eller svensk BankID. Få fuldt overblik over hele underskriftsprocessen med detaljerede aktivitetslogs – og giv dit team de bedste forudsætninger for at minimere fejl og arbejde effektivt . Gør det nemt for dine kunder at underskrive dokumenter digitalt – når som helst og hvor som helst. Modernisering af jeres processer fremmer innovation, øger produktiviteten og gør jeres organisation til en attraktiv og fremsynet arbejdsplads. Se, hvordan Penneo fungerer Over 3000 companies trust Penneo Se hvordan Penneo kan hjælpe dig BOOK ET UFORPLIGTENDE MØDE Produkter Penneo Sign Priser Integrationer Åben API Validator Hvorfor Penneo Løsninger Revision og regnskab Finans og bank Advokatydelser Ejendom Administration og HR Anvendelsesscenarier Digital signering Dokumenthåndtering Udfyld og underskriv PDF-formularer Automatisering af underskriftsprocesser Overholdelse af eIDAS Ressourcer Vidensunivers Trust Center Produktopdateringer SUPPORT SIGN Hjælpecenter KYC Hjælpecenter Systemstatus Virksomhed Om os Karriere Privatlivspolitik Vilkår Brug af cookies Accessibility Statement Whistleblower Policy Kontakt os PENNEO A/S - Gærtorvet 1-5, DK-1799 København V - CVR: 35633766 | 2026-01-13T09:30:34 |
https://llvmweekly.org/issue/579 | LLVM Weekly - #579, February 3rd 2025 LLVM Weekly - #579, February 3rd 2025 Welcome to the five hundred and seventy-ninth issue of LLVM Weekly, a weekly newsletter (published every Monday) covering developments in LLVM, Clang, and related projects. LLVM Weekly is brought to you by Alex Bradbury . Subscribe to future issues at http://llvmweekly.org and pass it on to anyone else you think may be interested. Please send any tips or feedback via email: asb@asbradbury.org , or Mastodon: @llvmweekly@fosstodon.org / @asb@fosstodon.org , or Bluesky: @llvmweekly.org / @asbradbury.org . News and articles from around the web and events The next Cambridge (UK) compiler social will take place on 12th February including talks by George Constantinides and Alex Zinenko. Be sure to register if you plan to attend. The delayed, but comprehensive and well worth the wait /r/cpp Wroclaw C++ committee meeting trip report is now up. If you fancy hearing me discuss RISC-V and a little bit of LLVM, I’m featured in the most recent episode of Igalia’s podcast . According to the LLVM calendar in the coming week there will be the following: Office hours with the following hosts: Quentin Colombet, Johannes Doerfert, Renato Golin. Online sync-ups on the following topics: Flang, MLIR C/C++ frontend, MemorySSA, LLVM/Offload, classic flang, Clang C/C++ language working group, SPIR-V, OpenMP for flang, HLSL, MLGO. For more details see the LLVM calendar , getting involved documentation on online sync ups and office hours . On the forums Tanya Lattner shared more information on EuroLLVM ticket prices and hotel . The LLVM 20.x branch happened and LLVM 20.1.0-rc1 was released . As a reminder, voting is open for the area team elections until February 10th. Renato Golin followed up on the MLIR organisation and charter thread to propose starting to form the high-level maintainer groups and then posted a thread on an MLIR Tensor Compiler Design Group . MLIR News #73 is out . Oskar Wirga is seeking feedback on a potential ability for Clang to collect coverage information of compiler-provided exploit mitigations . Pavel Labath started an RFC discussing about addressing incompatibilities between LLDB and GDB in their handling of the ‘x’ packet . Arseniy Zaostrovnykh posted an RFC on -ftime-trace for the static analyzer . Justin Stitt suggests adding wrapping and non-wrapping arithmetic types to Clang , providing finer grained control than options such as -fwrapv operating across a whole translation unit. Ted Woodward discussed adding RISC-V CSRs to LLDB core dumps and enabling disassembly of Qualcomm’s Xqci RISC-V extension . There was further back and forth discussion on the commit access criteria RFC . LLVM commits The new KernelInfo pass reports various statistics intended to advise users attempting to compile code for GPUs of common bad code patterns. 18f8106 . Building compiler-rt and libc by specifying them within LLVM_ENABLE_PROJECTS is now deprecated. LLVM_ENABLE_RUNTIMES should be used instead. b593110 . A scheduler model was added for the SiFive P550. ea9993a . As part of the work to remove debug instructions, various methods were transitioned to use iterators rather than Instruction* . 81d18ad8 , 34b1395 , 285009f , 65f81df . The RuntimeUnrollMultiExit knob can be used by targets to control whether to allow multi-exit unrolling. ad9da92 . GlobalISel disabled bf16 TableGen patterns for the time being due to issues with them matching for fp16 and vice versa. 5a81a55 . The Xmipscmove and Xmipslsp vendor extensions were implemented for RISC-V. 0cb7636 . LLVM intrinsics were switched to use StringTable . f4de28a . ReachingDefAnalysis was extended to stack objects. 3c3c850 . The nocapture attribute was replaced with captures(none) . 29441e4 . A new VectorizerEnd extension point was added after vectorizer passes in the PassBuilder. d3161de . New GitHub Actions automation was added to aid users requesting commit access. f8ef269 . Clang commits -fwrapv now only controls the well-definedness of signed integer overflow (i.e. no longer impacts pointer overflow). The new -fwrapv-pointer flag can be used to make pointer overflow well-defined. This matches GCC’s flags and behaviour. 1295aa2 . __nullptr was added as a keyword to C. 7fd5833 . A new PenaltyBreakBeforeMemberAccess style option was added to clang-format. d50ebd4 . diagnose_if was extended to accept more detailed warning information. 0865ecc . The new -fextend-variable-liveness flag can be used to improve debugging of optimised code by causing Clang to try to preserve the liveness of source variables through optimisations, so they are more likely to be visible in debuggers. 71ab44a , 4424c44 . TypeSanitizer now has documentation. 822954b . Documentation was added for HIPSTDPAR. 964565c . Implicit promotions of integer types was disabled for vector math builtins. 1ac3665 . Skeleton framework code was added for ClangIR to LLVM IR lowering. 38ddcb7 . Clang no longer emits pointer-tbaa for void pointers. Detailed reasoning is given in the commit message and associated documentation update. 77d3f8a . Other project commits Flang now supports the UNROLL directive to control how many times a loop should be unrolled. e811cb0 . libcxx dropped support for Clang 17. 7f845cb . LLDB expression evaluation with AArch64 Guarded Control Stacks enabled now works. b31e974 , 6d0dd3d . The MLIR MPI dialect was extended with additional types and ops. 48f8865 . Subscribe at LLVMWeekly.org . | 2026-01-13T09:30:34 |
https://llvmweekly.org/issue/561 | LLVM Weekly - #561, September 30th 2024 LLVM Weekly - #561, September 30th 2024 Welcome to the five hundred and sixty-first issue of LLVM Weekly, a weekly newsletter (published every Monday) covering developments in LLVM, Clang, and related projects. LLVM Weekly is brought to you by Alex Bradbury . Subscribe to future issues at http://llvmweekly.org and pass it on to anyone else you think may be interested. Please send any tips or feedback to asb@asbradbury.org , @llvmweekly or @asbradbury on Twitter, or @llvmweekly@fosstodon.org or @asb@fosstodon.org . News and articles from around the web and events Joseph Huber has a rather neat port of Doom that runs on AMDGPU with ROCm and LLVM’s libc . James Hamilton provided a high level introduction to LLVM . According to the LLVM calendar in the coming week there will be the following: Office hours with the following hosts: Renato Golin, Anastasia Stulova, Quentin Colombet, Johannes Doerfert. Online sync-ups on the following topics: Flang, libc++, LLVM/Offload, Clang C/C++ language working group, OpenMP for Flang, MLIR, HLSL, MLGO. For more details see the LLVM calendar , getting involved documentation on online sync ups and office hours . On the forums Chris Bieneman provided an update on efforts to establish a new LLVM project governance model , noting the hope to conduct the first elections in January 2025 if the proposal is adopted. Erich Keane posted an RFC on updating the supported host compiler versions for LLVM 20 . A large chunk of the ensuing discussion was about the expectations for whether builds should be -Werror -clean on all supported toolchains or not (they’re not today), though it was agreed this discussion belongs in a separate RFC. Nikita Popov suggested improvements to capture tracking in LLVM . Anton Korobeynikov provided a detailed update on pointer authentication support as of the LLVM 19 release as well as listing work that is still in progress. David Blaikie proposed a tweak to LLVM’s header including policy . Some respondents were keen to ensure the policy isn’t interpreted in a way that suggests running include-what-you-use is required. Rahul Joshi proposed support for auto in TableGen and also shared recent improvements to formatting/printing helpers in LLVM . Kadir Çetinkaya provided a revised RFC proposal for adding support for controlling Clang diagnostic severities at the file level . Nikita Popov started an RFC thread on introducing a samesign flag for icmp for use in cases where the two compared values are known to have the same sign and so ult will have the same result as slt . Andrew Savonichev shared a draft implementation plan for a DWARF reduction tool . Donald Chen shared a PSA about the semantics of program points in MLIR dataflow analysis changing . Neil Henning kicked off a discussion around adding the ability to make asserts runtime togglable . LLVM commits LLVM’s release notes are now in Markdown rather than RST. b9f09a4 . WebAssembly’s AsmTypeCheck can now detect multiple errors in a single function. b62075e . A new update_mc_test_checks.py utility was added, to update test files using llvm-mc. 2b892b0 . The computed properties IsSSA, NoPHIs, and NoVRegs can now be overridden in MIR input. 8ba334b . An llvm.atan2.* intrinsic was added. 26029d7 . The Zacas RISC-V extension is no longer marked as experimental. 614aeda . ConstantFPRange was added in order to in the future enable range-based optimisations for floating point values. fa824dc . The SLP vectorizer learned to do “clustered” vectorization for instructions other than loads. 3469db8 . The DirectX target gained a pass to scalarize vectors in global scope into arrays. 324bdd6 . Clang commits clang-tidy’s documentation gained a section to list examples of external projects using the tool. ce9a2c6 . The static analyzer taint propagation checker is no longer marked as alpha. f82fb06 . SPIRV memory scopes support was reworked and expanded. 3cfd0c0 . The -basic-block-sections=labels option was deprecated. 7b7747d . Command-line options were introduced for RISC-V CFI. 9f33eb8 . TestLanguage.def can now be used to specify all tested language versions. 7dfdca1 . Other project commits An ABI option was added to libcxx to harden operator[] for unique_ptr<T[]> when the size of the allocation is known. 45a09d1 . MLIR gained support for LLVM operand bundles. fde3c16 . Documentation on adding support for a new language was added back to LLDB. a3cf01d . Errors from LLDB’s inline expression evaluator are now much prettier. d33fa70 . Subscribe at LLVMWeekly.org . | 2026-01-13T09:30:34 |
https://logging.apache.org/log4j/2.x/manual/index.html | Manual :: Apache Log4j a subproject of Apache Logging Services Home Download Release notes Support Versioning and maintenance policy Security Manual Getting started Installation API Loggers Event Logger Simple Logger Status Logger Fluent API Fish tagging Levels Markers Thread Context Messages Flow Tracing Implementation Architecture Configuration Configuration file Configuration properties Programmatic configuration Appenders File appenders Rolling file appenders Database appenders Network Appenders Message queue appenders Delegating Appenders Layouts JSON Template Layout Pattern Layout Lookups Filters Scripts JMX Extending Plugins Performance Asynchronous loggers Garbage-free logging References Plugin reference Java API reference Resources F.A.Q. Migrating from Log4j 1 Migrating from Logback Migrating from SLF4J Building GraalVM native images Integrating with Hibernate Integrating with Jakarta EE Integrating with service-oriented architectures Development Components Log4j IOStreams Log4j Spring Boot Support Log4j Spring Cloud Configuration JUL-to-Log4j bridge Log4j-to-JUL bridge Related projects Log4j Jakarta EE Log4j JMX GUI Log4j Kotlin Log4j Scala Log4j Tools Log4j Transformation Tools Home Manual Edit this Page Manual Apache Log4j is a versatile, industrial-grade Java logging framework composed of an API, its implementation, and components to assist the deployment for various use cases. The project is actively maintained by a team of volunteers and support ed by a big community. Logging is an essential part of the software development process. It provides a way to track the flow of execution in a program, allowing developers to understand the application’s behavior without needing a debugger. This is particularly useful when tracking bugs or understanding why a particular code runs slowly. The original concept for Log4j was conceived in early 1996 when the E.U. SEMPER project decided to develop its own tracing API. In 2003, the project was donated to the Apache Software Foundation, which became Apache Log4j. Since then, Log4j has seen numerous releases and has become a widely adopted solution. When should you use Log4j? Log4j is an excellent choice for any Java application that needs logging capabilities. It is user-friendly, fast, and flexible. You can use it to log messages at different levels of severity, from debug to fatal, and you can configure it to log messages to various destinations, such as files, databases, or the console. See Getting started for an introduction. When not to use Log4j? While Log4j is a highly suitable choice for many applications, it may be challenging to locate the information you require when logging a high volume of messages. Additionally, logging can impact your application’s performance. Log4j offers solutions to address these concerns. However, if you are in a unique situation where you are concerned about logging overhead or volume, you may wish to consider not using logging at all. What does Log4j offer? Log4j offers numerous features, including: Batteries included Log4j bundles a rich set of components to assist various use cases. Appenders targeting files, network sockets, databases, SMTP servers, etc. Layouts that can render CSV, HTML, JSON, Syslog, etc. formatted outputs Filters based on log event rates, regular expressions, scripts, time, etc. Lookups for accessing system properties, environment variables, log event fields, etc. Reliability Log4j is built with solid reliability in mind. It can automatically reload its configuration upon modification and will do so without losing log events while reconfiguration occurs. Performance When configured correctly, Log4j can deliver excelling performance without almost any burden on the Java garbage collector, and it will do so without sacrificing reliability. Check out the Performance page for details. Extensibility Log4j contains a fully-fledged plugin support that users can leverage to extend functionality. You can easily add your components (layouts, appenders, filters, etc.) or customize existing ones (e.g., adding new directives to Pattern Layout or JSON Template Layout ). Check out the Extending Log4j page. Powerful API Log4j is a logging system where the API (called Log4j API) and its implementation (called Log4j Core) is distinctly separate from each other. Log4j API provides the most feature-rich logging facade in the market; support for various Message types (such as Object or Map ) besides plain String , lambda expressions, parameterized logging, markers, levels, diagnostic contexts (aka. MDC/NDC), etc. Log4j team takes backward compatibility very seriously and makes sure people relying on Log4j API gets a logging facade that is straightforward to use in a correct and future-proof way. Check out the Java API , Kotlin API and Scala API pages for further information. No vendor lock-in Log4j API is a generic logging facade for various logging frameworks. While Log4j Core implements it at its fullest, you can easily switch to other implementations such as Logback or JUL ( java.util.logging ). How to learn more? How can I get started with Log4j? How can I install Log4j? How can I configure Log4j? How can I use Log4j API? How can I tune my Log4j setup for performance? How can I migrate from Log4j 1 to Log4j 2 ? What are Log4j plugins and how can I use them to extend Log4j? Copyright © 1999-2025 The Apache Software Foundation . Licensed under the Apache Software License, Version 2.0 . Please read our privacy policy . Apache, Log4j, and the Apache feather logo are trademarks or registered trademarks of The Apache Software Foundation. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. | 2026-01-13T09:30:34 |
https://llvmweekly.org/issue/590 | LLVM Weekly - #590, April 21st 2025 LLVM Weekly - #590, April 21st 2025 If you prefer, you can read a HTML version of this email at https://llvmweekly.org/issue/590 . Welcome to the five hundred and ninetieth issue of LLVM Weekly, a weekly newsletter (published every Monday) covering developments in LLVM, Clang, and related projects. LLVM Weekly is brought to you by Alex Bradbury . Subscribe to future issues at https://llvmweekly.org and pass it on to anyone else you think may be interested. Please send any tips or feedback via email: asb@asbradbury.org , or Mastodon: @llvmweekly@fosstodon.org / @asb@fosstodon.org , or Bluesky: @llvmweekly.org / @asbradbury.org . EuroLLVM was a lot of fun last week. Thank you, as always, to everyone involved in organising. News and articles from around the web and events Cor3ntin wrote a fantastic run-down of recent improvements to Clang . The next Toronto LLVM meetup will take place on April 30th . The next Bay Area LLVM meetup will take place on April 28th . According to the LLVM calendar in the coming week there will be the following: Office hours with the following hosts: Kristof Beyls, Amara Emerson, Johannes Doerfert. Online sync-ups on the following topics: ClangIR upstreaming, OpenMP, Flang, RISC-V, embedded toolchains. For more details see the LLVM calendar , getting involved documentation on online sync ups and office hours . On the forums Reid Kleckner started an RFC proposal on changing LLVM_LINK_DYLIB to default ON on Posix platforms . Gábor Horváth shared notes from the static analysis roundtable at EuroLLVM 2025 . cirt-os asked about increased file size with BOLT and ability to remove .botl sections . Fraser Cormack proposed introducing elementwise clz/ctz builtins . LLVM 20.1.3 was released . “isuckatcs” wrote up a plan for prototyping ‘summary based analysis’ for the Clang static analyzer . David Blaikie queried how people are doing post-commit review . LLVM commits The LLVM intrinsic string table was moved from character to string literal mission on non-MSVC platforms. 0a27c4e . BranchRelaxation was ported to the new pass manager, completing the PreEmitPasses. b283ff7 . RegAlloc now uses whether a register is callee-saved or not as a tiebreaker before falling back to register ID. 74e8f29 . LLVM public interface annotations such as LLVM_ABI were documented. 3b91030 . +nosimd now works for AArch32 targets. 06da00a . 16-bit floating point is now supported in the SystemZ backend. 6d03f51 . Range attributes can now be specified in Intrinsics.td. c3c0b27 . The LangRef now has a description of the semantics of call signatures. 7113010 . Incremental compile times when enabling/disabling a target should be much improved as the LLVM_HAS_*_TARGET macro definitions were moved to a separate header, Targets.h , outside of llvm-config.h (which is included by most code, so changes cause cascading rebuilds). 667209e . Address matching in SDag patterns is now supported for X86 GlobalISel. e8245d5 . Clang commits Clang bytecode disassembly printer can now print lines showing jump targets. 578ca5e . Elementwise minnum/maxnum builtin functions were added. 58b5df0 . ClangIR minimal support for structure types was upstreamed. cd7d2c3 . A -funique-source-file-names flag was introduced. a5aa0c4 , a1d52fc . Support was added for the __ptrauth type qualifier. a3283a9 . -fextend-lifetimes was enabled at -Og . a9dff35 . counted_by and counted_by_or_null are now allowed on pointers where the pointee type is incomplete bu potentially completable. 59eafd1 . Other project commits Initial Bolt instrumentation support was landed for 64-bit RISC-V. dbb79c3 . Flang now handles volatile types. c9ec1bc . std::stable_sort will now use radix sort for floats as well as integers. 51b8c66 . lldb-dap now supports cancelling of requests. 2d30a60 . C APIs were added for the MLIR SMT dialect. 9deb08a . The MLIR 1:N dialect conversion driver was deleted after its period of deprecation was completed. 23e3cbb . Subscribe at LLVMWeekly.org . | 2026-01-13T09:30:34 |
https://logging.apache.org/log4j/2.x/manual/config-intro.html | Configuration :: Apache Log4j a subproject of Apache Logging Services Home Download Release notes Support Versioning and maintenance policy Security Manual Getting started Installation API Loggers Event Logger Simple Logger Status Logger Fluent API Fish tagging Levels Markers Thread Context Messages Flow Tracing Implementation Architecture Configuration Configuration file Configuration properties Programmatic configuration Appenders File appenders Rolling file appenders Database appenders Network Appenders Message queue appenders Delegating Appenders Layouts JSON Template Layout Pattern Layout Lookups Filters Scripts JMX Extending Plugins Performance Asynchronous loggers Garbage-free logging References Plugin reference Java API reference Resources F.A.Q. Migrating from Log4j 1 Migrating from Logback Migrating from SLF4J Building GraalVM native images Integrating with Hibernate Integrating with Jakarta EE Integrating with service-oriented architectures Development Components Log4j IOStreams Log4j Spring Boot Support Log4j Spring Cloud Configuration JUL-to-Log4j bridge Log4j-to-JUL bridge Related projects Log4j Jakarta EE Log4j JMX GUI Log4j Kotlin Log4j Scala Log4j Tools Log4j Transformation Tools Home Manual Implementation Configuration Edit this Page Configuration Even moderately sized applications can contain thousands of logging statements. To decide which of these statements will be logged and where, users need to configure Log4j Core in one of following ways: Through a configuration file Through programmatic configuration Some meta-configuration options (e.g., the configuration file location) are only available through system properties . Copyright © 1999-2025 The Apache Software Foundation . Licensed under the Apache Software License, Version 2.0 . Please read our privacy policy . Apache, Log4j, and the Apache feather logo are trademarks or registered trademarks of The Apache Software Foundation. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. | 2026-01-13T09:30:34 |
http://docs.buildbot.net/current/manual/cmdline.html#buildbot-config-directory | 2.7. Command-line Tool — Buildbot 4.3.0 documentation Buildbot 1. Buildbot Tutorial 2. Buildbot Manual 2.1. Introduction 2.2. Installation 2.3. Concepts 2.4. Secret Management 2.5. Configuration 2.6. Customization 2.7. Command-line Tool 2.7.1. buildbot 2.7.1.1. Administrator Tools 2.7.1.2. Developer Tools 2.7.1.3. Other Tools 2.7.1.4. .buildbot config directory 2.7.2. buildbot-worker 2.7.2.1. create-worker 2.7.2.2. start 2.7.2.3. restart 2.7.2.4. stop 2.8. Resources 2.9. Optimization 2.10. Plugin Infrastructure in Buildbot 2.11. Deployment 2.12. Upgrading 3. Buildbot Development 4. Release Notes 5. Older Release Notes 6. API Indices Buildbot 2. Buildbot Manual 2.7. Command-line Tool View page source 2.7. Command-line Tool This section describes command-line tools available after buildbot installation. The two main command-line tools are buildbot and buildbot-worker . The former handles a Buildbot master and the former handles a Buildbot worker. Every command-line tool has a list of global options and a set of commands which have their own options. One can run these tools in the following way: buildbot [global options] command [command options] buildbot-worker [global options] command [command options] The buildbot command is used on the master, while buildbot-worker is used on the worker. Global options are the same for both tools which perform the following actions: --help Print general help about available commands and global options and exit. All subsequent arguments are ignored. --verbose Set verbose output. --version Print current buildbot version and exit. All subsequent arguments are ignored. You can get help on any command by specifying --help as a command option: buildbot command --help You can also use manual pages for buildbot and buildbot-worker for quick reference on command-line options. The remainder of this section describes each buildbot command. See Command Line Index for a full list. 2.7.1. buildbot The buildbot command-line tool can be used to start or stop a buildmaster or buildbot, and to interact with a running buildmaster. Some of its subcommands are intended for buildmaster admins, while some are for developers who are editing the code that the buildbot is monitoring. 2.7.1.1. Administrator Tools The following buildbot sub-commands are intended for buildmaster administrators: create-master buildbot create-master -r {BASEDIR} This creates a new directory and populates it with files that allow it to be used as a buildmaster’s base directory. You will usually want to use the option -r option to create a relocatable buildbot.tac . This allows you to move the master directory without editing this file. upgrade-master buildbot upgrade-master {BASEDIR} This upgrades a previously created buildmaster’s base directory for a new version of buildbot master source code. This will copy the web server static files, and potentially upgrade the db. start buildbot start [--nodaemon] {BASEDIR} This starts a buildmaster which was already created in the given base directory. The daemon is launched in the background, with events logged to a file named twistd.log . The option –nodaemon option instructs Buildbot to skip daemonizing. The process will start in the foreground. It will only return to the command-line when it is stopped. Additionally, the user can set the environment variable START_TIMEOUT to specify the amount of time the script waits for the master to start until it declares the operation as failure. restart buildbot restart [--nodaemon] {BASEDIR} Restart the buildmaster. This is equivalent to stop followed by start The option –nodaemon option has the same meaning as for start . stop buildbot stop {BASEDIR} This terminates the daemon (either buildmaster or worker) running in the given directory. The --clean option shuts down the buildmaster cleanly. With --no-wait option buildbot stop command will send buildmaster shutdown signal and will immediately exit, not waiting for complete buildmaster shutdown. sighup buildbot sighup {BASEDIR} This sends a SIGHUP to the buildmaster running in the given directory, which causes it to re-read its master.cfg file. checkconfig buildbot checkconfig {BASEDIR|CONFIG_FILE} This checks if the buildmaster configuration is well-formed and contains no deprecated or invalid elements. If no arguments are used or the base directory is passed as the argument the config file specified in buildbot.tac is checked. If the argument is the path to a config file then it will be checked without using the buildbot.tac file. cleanupdb buildbot cleanupdb {BASEDIR|CONFIG_FILE} [-q] This command is frontend for various database maintenance jobs: optimiselogs: This optimization groups logs into bigger chunks to apply higher level of compression. This script runs for as long as it takes to finish the job including the time needed to check master.cfg file. copy-db buildbot copy-db {DESTINATION_URL} {BASEDIR} [-q] This command copies all buildbot data from source database configured in the buildbot configuration file to the destination database. The URL of the destination database is specified on the command line. The destination database may have different type from the source database. The destination database must be empty. The script will initialize it in the same way as if a new Buildbot installation was created. Source database must be already upgraded to the current Buildbot version by the buildbot upgrade-master command. 2.7.1.2. Developer Tools These tools are provided for use by the developers who are working on the code that the buildbot is monitoring. try This lets a developer to ask the question What would happen if I committed this patch right now? . It runs the unit test suite (across multiple build platforms) on the developer’s current code, allowing them to make sure they will not break the tree when they finally commit their changes. The buildbot try command is meant to be run from within a developer’s local tree, and starts by figuring out the base revision of that tree (what revision was current the last time the tree was updated), and a patch that can be applied to that revision of the tree to make it match the developer’s copy. This (revision, patch) pair is then sent to the buildmaster, which runs a build with that SourceStamp . If you want, the tool will emit status messages as the builds run, and will not terminate until the first failure has been detected (or the last success). There is an alternate form which accepts a pre-made patch file (typically the output of a command like svn diff ). This --diff form does not require a local tree to run from. See try –diff concerning the --diff command option. For this command to work, several pieces must be in place: the Try_Jobdir or : Try_Userpass , as well as some client-side configuration. Locating the master The try command needs to be told how to connect to the try scheduler, and must know which of the authentication approaches described above is in use by the buildmaster. You specify the approach by using --connect=ssh or --connect=pb (or try_connect = 'ssh' or try_connect = 'pb' in .buildbot/options ). For the PB approach, the command must be given a option –master argument (in the form HOST : PORT ) that points to TCP port that you picked in the Try_Userpass scheduler. It also takes a option –username and option –passwd pair of arguments that match one of the entries in the buildmaster’s userpass list. These arguments can also be provided as try_master , try_username , and try_password entries in the .buildbot/options file. For the SSH approach, the command must be given option –host and option –username , to get to the buildmaster host. It must also be given option –jobdir , which points to the inlet directory configured above. The jobdir can be relative to the user’s home directory, but most of the time you will use an explicit path like ~buildbot/project/trydir . These arguments can be provided in .buildbot/options as try_host , try_username , try_password , and try_jobdir . If you need to use something different from the default ssh command for connecting to the remote system, you can use –ssh command line option or try_ssh in the configuration file. The SSH approach also provides a option –buildbotbin argument to allow specification of the buildbot binary to run on the buildmaster. This is useful in the case where buildbot is installed in a virtualenv on the buildmaster host, or in other circumstances where the buildbot command is not on the path of the user given by option –username . The option –buildbotbin argument can be provided in .buildbot/options as try_buildbotbin The following command line arguments are deprecated, but retained for backward compatibility: --tryhost is replaced by option –host --trydir is replaced by option –jobdir --master is replaced by option –masterstatus Likewise, the following .buildbot/options file entries are deprecated, but retained for backward compatibility: try_dir is replaced by try_jobdir masterstatus is replaced by try_masterstatus Waiting for results If you provide the option –wait option (or try_wait = True in .buildbot/options ), the buildbot try command will wait until your changes have either been proven good or bad before exiting. Unless you use the option –quiet option (or try_quiet=True ), it will emit a progress message every 60 seconds until the builds have completed. The SSH connection method does not support waiting for results. Choosing the Builders A trial build is performed on multiple Builders at the same time, and the developer gets to choose which Builders are used (limited to a set selected by the buildmaster admin with the TryScheduler ’s builderNames= argument). The set you choose will depend upon what your goals are: if you are concerned about cross-platform compatibility, you should use multiple Builders, one from each platform of interest. You might use just one builder if that platform has libraries or other facilities that allow better test coverage than what you can accomplish on your own machine, or faster test runs. The set of Builders to use can be specified with multiple option –builder arguments on the command line. It can also be specified with a single try_builders option in .buildbot/options that uses a list of strings to specify all the Builder names: try_builders = [ "full-OSX" , "full-win32" , "full-linux" ] If you are using the PB approach, you can get the names of the builders that are configured for the try scheduler using the get-builder-names argument: buildbot try --get-builder-names --connect = pb --master = ... --username = ... --passwd = ... Specifying the VC system The try command also needs to know how to take the developer’s current tree and extract the (revision, patch) source-stamp pair. Each VC system uses a different process, so you start by telling the try command which VC system you are using, with an argument like option –vc=cvs or option –vc=git . This can also be provided as try_vc in .buildbot/options . The following names are recognized: bzr cvs darcs hg git mtn p4 svn Finding the top of the tree Some VC systems (notably CVS and SVN) track each directory more-or-less independently, which means the try command needs to move up to the top of the project tree before it will be able to construct a proper full-tree patch. To accomplish this, the try command will crawl up through the parent directories until it finds a marker file. The default name for this marker file is .buildbot-top , so when you are using CVS or SVN you should touch .buildbot-top from the top of your tree before running buildbot try . Alternatively, you can use a filename like ChangeLog or README , since many projects put one of these files in their top-most directory (and nowhere else). To set this filename, use --topfile=ChangeLog , or set it in the options file with try_topfile = 'ChangeLog' . You can also manually set the top of the tree with --topdir=~/trees/mytree , or try_topdir = '~/trees/mytree' . If you use try_topdir , in a .buildbot/options file, you will need a separate options file for each tree you use, so it may be more convenient to use the try_topfile approach instead. Other VC systems which work on full projects instead of individual directories (Darcs, Mercurial, Git, Monotone) do not require try to know the top directory, so the option –try-topfile and option –try-topdir arguments will be ignored. If the try command cannot find the top directory, it will abort with an error message. The following command line arguments are deprecated, but retained for backward compatibility: --try-topdir is replaced by option –topdir --try-topfile is replaced by option –topfile Determining the branch name Some VC systems record the branch information in a way that try can locate it. For the others, if you are using something other than the default branch, you will have to tell the buildbot which branch your tree is using. You can do this with either the option –branch argument, or a try_branch entry in the .buildbot/options file. Determining the revision and patch Each VC system has a separate approach for determining the tree’s base revision and computing a patch. CVS try pretends that the tree is up to date. It converts the current time into a option -D time specification, uses it as the base revision, and computes the diff between the upstream tree as of that point in time versus the current contents. This works, more or less, but requires that the local clock be in reasonably good sync with the repository. SVN try does a svn status -u to find the latest repository revision number (emitted on the last line in the Status against revision: NN message). It then performs an svn diff -r NN to find out how your tree differs from the repository version, and sends the resulting patch to the buildmaster. If your tree is not up to date, this will result in the try tree being created with the latest revision, then backwards patches applied to bring it back to the version you actually checked out (plus your actual code changes), but this will still result in the correct tree being used for the build. bzr try does a bzr revision-info to find the base revision, then a bzr diff -r$base.. to obtain the patch. Mercurial hg parents --template '{node}\n' emits the full revision id (as opposed to the common 12-char truncated) which is a SHA1 hash of the current revision’s contents. This is used as the base revision. hg diff then provides the patch relative to that revision. For try to work, your working directory must only have patches that are available from the same remotely-available repository that the build process’ source.Mercurial will use. Perforce try does a p4 changes -m1 ... to determine the latest changelist and implicitly assumes that the local tree is synced to this revision. This is followed by a p4 diff -du to obtain the patch. A p4 patch differs slightly from a normal diff. It contains full depot paths and must be converted to paths relative to the branch top. To convert the following restriction is imposed. The p4base (see P4Source ) is assumed to be //depot Darcs try does a darcs changes --context to find the list of all patches back to and including the last tag that was made. This text file (plus the location of a repository that contains all these patches) is sufficient to re-create the tree. Therefore the contents of this context file are the revision stamp for a Darcs-controlled source tree. It then does a darcs diff -u to compute the patch relative to that revision. Git git branch -v lists all the branches available in the local repository along with the revision ID it points to and a short summary of the last commit. The line containing the currently checked out branch begins with “* “ (star and space) while all the others start with “ “ (two spaces). try scans for this line and extracts the branch name and revision from it. Then it generates a diff against the base revision. Todo I’m not sure if this actually works the way it’s intended since the extracted base revision might not actually exist in the upstream repository. Perhaps we need to add a –remote option to specify the remote tracking branch to generate a diff against. Monotone mtn automate get_base_revision_id emits the full revision id which is a SHA1 hash of the current revision’s contents. This is used as the base revision. mtn diff then provides the patch relative to that revision. For try to work, your working directory must only have patches that are available from the same remotely-available repository that the build process’ source.Monotone will use. patch information You can provide the option –who=dev to designate who is running the try build. This will add the dev to the Reason field on the try build’s status web page. You can also set try_who = dev in the .buildbot/options file. Note that option –who=dev will not work on version 0.8.3 or earlier masters. Similarly, option –comment=COMMENT will specify the comment for the patch, which is also displayed in the patch information. The corresponding config-file option is try_comment . Sending properties You can set properties to send with your change using either the option –property=key=value option, which sets a single property, or the option –properties=key1=value1,key2=value2… option, which sets multiple comma-separated properties. Either of these can be specified multiple times. Note that the option –properties option uses commas to split on properties, so if your property value itself contains a comma, you’ll need to use the option –property option to set it. try –diff Sometimes you might have a patch from someone else that you want to submit to the buildbot. For example, a user may have created a patch to fix some specific bug and sent it to you by email. You’ve inspected the patch and suspect that it might do the job (and have at least confirmed that it doesn’t do anything evil). Now you want to test it out. One approach would be to check out a new local tree, apply the patch, run your local tests, then use buildbot try to run the tests on other platforms. An alternate approach is to use the buildbot try --diff form to have the buildbot test the patch without using a local tree. This form takes a option –diff argument which points to a file that contains the patch you want to apply. By default this patch will be applied to the TRUNK revision, but if you give the optional option –baserev argument, a tree of the given revision will be used as a starting point instead of TRUNK. You can also use buildbot try --diff=- to read the patch from stdin . Each patch has a patchlevel associated with it. This indicates the number of slashes (and preceding pathnames) that should be stripped before applying the diff. This exactly corresponds to the option -p or option –strip argument to the patch utility. By default buildbot try --diff uses a patchlevel of 0, but you can override this with the option -p argument. When you use option –diff , you do not need to use any of the other options that relate to a local tree, specifically option –vc , option –try-topfile , or option –try-topdir . These options will be ignored. Of course you must still specify how to get to the buildmaster (with option –connect , option –tryhost , etc). 2.7.1.3. Other Tools These tools are generally used by buildmaster administrators. sendchange This command is used to tell the buildmaster about source changes. It is intended to be used from within a commit script, installed on the VC server. It requires that you have a PBChangeSource ( PBChangeSource ) running in the buildmaster (by being set in c['change_source'] ). buildbot sendchange --master {MASTERHOST}:{PORT} --auth {USER}:{PASS} --who {USER} {FILENAMES..} The option –auth option specifies the credentials to use to connect to the master, in the form user:pass . If the password is omitted, then sendchange will prompt for it. If both are omitted, the old default (username “change” and password “changepw”) will be used. Note that this password is well-known, and should not be used on an internet-accessible port. The option –master and option –username arguments can also be given in the options file (see .buildbot config directory ). There are other (optional) arguments which can influence the Change that gets submitted: --branch (or option branch ) This provides the (string) branch specifier. If omitted, it defaults to None , indicating the default branch . All files included in this Change must be on the same branch. --category (or option category ) This provides the (string) category specifier. If omitted, it defaults to None , indicating no category . The category property can be used by schedulers to filter what changes they listen to. --project (or option project ) This provides the (string) project to which this change applies, and defaults to ‘’. The project can be used by schedulers to decide which builders should respond to a particular change. --repository (or option repository ) This provides the repository from which this change came, and defaults to '' . --revision This provides a revision specifier, appropriate to the VC system in use. --revision_file This provides a filename which will be opened and the contents used as the revision specifier. This is specifically for Darcs, which uses the output of darcs changes --context as a revision specifier. This context file can be a couple of kilobytes long, spanning a couple lines per patch, and would be a hassle to pass as a command-line argument. --property This parameter is used to set a property on the Change generated by sendchange . Properties are specified as a name : value pair, separated by a colon. You may specify many properties by passing this parameter multiple times. --comments This provides the change comments as a single argument. You may want to use option –logfile instead. --logfile This instructs the tool to read the change comments from the given file. If you use - as the filename, the tool will read the change comments from stdin. --encoding Specifies the character encoding for all other parameters, defaulting to 'utf8' . --vc Specifies which VC system the Change is coming from, one of: cvs , svn , darcs , hg , bzr , git , mtn , or p4 . Defaults to None . user Note that in order to use this command, you need to configure a CommandlineUserManager instance in your master.cfg file, which is explained in Users Options . This command allows you to manage users in buildbot’s database. No extra requirements are needed to use this command, aside from the Buildmaster running. For details on how Buildbot manages users, see Users . --master The user command can be run virtually anywhere provided a location of the running buildmaster. The option –master argument is of the form MASTERHOST : PORT . --username PB connection authentication that should match the arguments to CommandlineUserManager . --passwd PB connection authentication that should match the arguments to CommandlineUserManager . --op There are four supported values for the option –op argument: add , update , remove , and get . Each are described in full in the following sections. --bb_username Used with the option –op=update option, this sets the user’s username for web authentication in the database. It requires option –bb_password to be set along with it. --bb_password Also used with the option –op=update option, this sets the password portion of a user’s web authentication credentials into the database. The password is first encrypted prior to storage for security reasons. --ids When working with users, you need to be able to refer to them by unique identifiers to find particular users in the database. The option –ids option lets you specify a comma separated list of these identifiers for use with the user command. The option –ids option is used only when using option –op=remove or option –op=get . --info Users are known in buildbot as a collection of attributes tied together by some unique identifier (see Users ). These attributes are specified in the form {TYPE}={VALUE} when using the option –info option. These {TYPE}={VALUE} pairs are specified in a comma separated list, so for example: --info=svn=jdoe,git='John Doe <joe@example.com>' The option –info option can be specified multiple times in the user command, as each specified option will be interpreted as a new user. Note that option –info is only used with option –op=add or with option –op=update , and whenever you use option –op=update you need to specify the identifier of the user you want to update. This is done by prepending the option –info arguments with {ID:} . If we were to update 'jschmo' from the previous example, it would look like this: --info=jdoe:git='Joe Doe <joe@example.com>' Note that option –master , option –username , option –passwd , and option –op are always required to issue the user command. The option –master , option –username , and option –passwd options can be specified in the option file with keywords user_master , user_username , and user_passwd , respectively. If user_master is not specified, then option –master from the options file will be used instead. Below are examples of how each command should look. Whenever a user command is successful, results will be shown to whoever issued the command. For option –op=add : buildbot user --master={MASTERHOST} --op=add \ --username={USER} --passwd={USERPW} \ --info={TYPE}={VALUE},... For option –op=update : buildbot user --master={MASTERHOST} --op=update \ --username={USER} --passwd={USERPW} \ --info={ID}:{TYPE}={VALUE},... For option –op=remove : buildbot user --master={MASTERHOST} --op=remove \ --username={USER} --passwd={USERPW} \ --ids={ID1},{ID2},... For option –op=get : buildbot user --master={MASTERHOST} --op=get \ --username={USER} --passwd={USERPW} \ --ids={ID1},{ID2},... A note on option –op=update : when updating the option –bb_username and option –bb_password , the option –info doesn’t need to have additional {TYPE}={VALUE} pairs to update and can just take the {ID} portion. 2.7.1.4. .buildbot config directory Many of the buildbot tools must be told how to contact the buildmaster that they interact with. This specification can be provided as a command-line argument, but most of the time it will be easier to set them in an options file. The buildbot command will look for a special directory named .buildbot , starting from the current directory (where the command was run) and crawling upwards, eventually looking in the user’s home directory. It will look for a file named options in this directory, and will evaluate it as a Python script, looking for certain names to be set. You can just put simple name = 'value' pairs in this file to set the options. For a description of the names used in this file, please see the documentation for the individual buildbot sub-commands. The following is a brief sample of what this file’s contents could be. # for status-reading tools masterstatus = 'buildbot.example.org:12345' # for 'sendchange' or the debug port master = 'buildbot.example.org:18990' Note carefully that the names in the options file usually do not match the command-line option name. master Equivalent to option –master for sendchange . It is the location of the pb.PBChangeSource for `sendchange . username Equivalent to option –username for the sendchange command. branch Equivalent to option –branch for the sendchange command. category Equivalent to option –category for the sendchange command. try_connect Equivalent to option –connect , this specifies how the try command should deliver its request to the buildmaster. The currently accepted values are ssh and pb . try_builders Equivalent to option –builders , specifies which builders should be used for the try build. try_vc Equivalent to option –vc for try , this specifies the version control system being used. try_branch Equivalent to option –branch , this indicates that the current tree is on a non-trunk branch. try_topdir try_topfile Use try_topdir , equivalent to option –try-topdir , to explicitly indicate the top of your working tree, or try_topfile , equivalent to option –try-topfile to name a file that will only be found in that top-most directory. try_host try_username try_dir When try_connect is ssh , the command will use try_host for option –tryhost , try_username for option –username , and try_dir for option –trydir . Apologies for the confusing presence and absence of ‘try’. try_username try_password try_master Similarly, when try_connect is pb , the command will pay attention to try_username for option –username , try_password for option –passwd , and try_master for option –master . try_wait masterstatus try_wait and masterstatus (equivalent to option –wait and master , respectively) are used to ask the try command to wait for the requested build to complete. 2.7.2. buildbot-worker buildbot-worker command-line tool is used for worker management only and does not provide any additional functionality. One can create, start, stop and restart the worker. 2.7.2.1. create-worker This creates a new directory and populates it with files that let it be used as a worker’s base directory. You must provide several arguments, which are used to create the initial buildbot.tac file. The option -r option is advisable here, just like for create-master . buildbot-worker create-worker -r {BASEDIR} {MASTERHOST}:{PORT} {WORKERNAME} {PASSWORD} The create-worker options are described in Worker Options . 2.7.2.2. start This starts a worker which was already created in the given base directory. The daemon is launched in the background, with events logged to a file named twistd.log . buildbot-worker start [--nodaemon] BASEDIR The option –nodaemon option instructs Buildbot to skip daemonizing. The process will start in the foreground. It will only return to the command-line when it is stopped. 2.7.2.3. restart buildbot-worker restart [--nodaemon] BASEDIR This restarts a worker which is already running. It is equivalent to a stop followed by a start . The option –nodaemon option has the same meaning as for start . 2.7.2.4. stop This terminates the daemon worker running in the given directory. buildbot stop BASEDIR Previous Next © Copyright Buildbot Team Members. Built with Sphinx using a theme provided by Read the Docs . | 2026-01-13T09:30:34 |
https://logging.apache.org/log4j/2.x/log4j-to-jul.html | Log4j-to-JUL bridge :: Apache Log4j a subproject of Apache Logging Services Home Download Release notes Support Versioning and maintenance policy Security Manual Getting started Installation API Loggers Event Logger Simple Logger Status Logger Fluent API Fish tagging Levels Markers Thread Context Messages Flow Tracing Implementation Architecture Configuration Configuration file Configuration properties Programmatic configuration Appenders File appenders Rolling file appenders Database appenders Network Appenders Message queue appenders Delegating Appenders Layouts JSON Template Layout Pattern Layout Lookups Filters Scripts JMX Extending Plugins Performance Asynchronous loggers Garbage-free logging References Plugin reference Java API reference Resources F.A.Q. Migrating from Log4j 1 Migrating from Logback Migrating from SLF4J Building GraalVM native images Integrating with Hibernate Integrating with Jakarta EE Integrating with service-oriented architectures Development Components Log4j IOStreams Log4j Spring Boot Support Log4j Spring Cloud Configuration JUL-to-Log4j bridge Log4j-to-JUL bridge Related projects Log4j Jakarta EE Log4j JMX GUI Log4j Kotlin Log4j Scala Log4j Tools Log4j Transformation Tools Home Components Log4j-to-JUL bridge Edit this Page Log4j-to-JUL bridge The Log4j-to-JUL bridge provides components that allow application and library that use the Log4j API to log to java.util.logging.Logger (JUL) instead. This chapter covers the implementation details of the Log4j-to-JUL bridge. For the installation procedure and basic usage see Installing JUL section of our Installation guide . Level conversion The current Log4j-to-JUL implementation does not use custom JUL levels and converts Log4j levels to JUL according to the following table: Table 1. Log4j to Java level conversion Log4j level priority Log4j standard levels Java Level 0 ≤ priority < 300 FATAL, ERROR SEVERE 300 ≤ priority < 400 WARN WARNING 400 ≤ priority < 500 INFO INFO 500 ≤ priority < 600 DEBUG FINE 600 ≤ priority TRACE FINER Copyright © 1999-2025 The Apache Software Foundation . Licensed under the Apache Software License, Version 2.0 . Please read our privacy policy . Apache, Log4j, and the Apache feather logo are trademarks or registered trademarks of The Apache Software Foundation. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. | 2026-01-13T09:30:34 |
https://logging.apache.org/download.html#sbom | Download :: Apache Logging Services Logging Services a project of Apache Software Foundation Home About Guidelines Charter Team Processes Wiki What is logging? Download Support Security XML Schema Blog The ASF License Donate Thanks Home Download Edit this Page Download You can use one of the following channels to download the Logging Services release distributions. All Logging Services projects distribute convenience binaries that are easy to install for the programming language platform they target. You are strongly advised to check the installation instructions in the website of the project ( Log4cxx , Log4j , Log4net , etc.) you are trying to install. Official distribution channels In accordance with the Apache Software Foundation’s release distribution policy and creation process , all Logging Services release distributions are officially accessible from the following channels: ASF Distribution directory (contains the most recent releases ) ASF Distribution directory archive (contains all published releases) Java distribution channels ASF Release and snapshot Nexus repositories (mirrored to the Maven Central Repository ) .NET distribution channels asf organization in NuGet Verification All Logging Services release distributions are digitally signed by the release manager and provided with checksum files. You can verify a distribution by following instructions: Linux/macOS Windows # Download and import the release manager public keys wget -O - https://downloads.apache.org/logging/KEYS | gpg --import # Verify signatures for sigFile in *.asc; do gpg --verify $sigFile ${sigFile%.asc}; done # Verify checksums shasum --check *.sha512 Download the release manager public keys Use gpg --import to import the keys Verify signature files: gpg --verify some.file.asc some.file Verify checksums: certUtil -hashfile some.file SHA512 Software Bill of Materials (SBOM) Many Logging Services projects distribute CycloneDX Software Bill of Materials (SBOM) along with each deployed artifact. This is streamlined by Logging Parent for Maven-based projects. Produced SBOMs contain BOM-links referring to a CycloneDX Vulnerability Disclosure Report (VDR) that Apache Logging Services uses for all projects it maintains. This VDR is accessible through the following URL: https://logging.apache.org/cyclonedx/vdr.xml Copyright © 1999-2026 The Apache Software Foundation . Licensed under the Apache Software License, Version 2.0 . Please read our privacy policy . Apache, Log4j, and the Apache feather logo are trademarks or registered trademarks of The Apache Software Foundation. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. | 2026-01-13T09:30:34 |
https://www.iso.org/es/standard/87945.html | ISO/UNDP PAS 53002 - Directrices para contribuir a los Objetivos de Desarrollo Sostenible (ODS) de las Naciones Unidas Ir directamente al contenido principal Aplicaciones OBP español English français русский Menú Normas Sectores Salud Tecnologías de la información y afines Gestión y servicios Seguridad, protección y gestión de riesgos Transporte Energía Diversidad e inclusión Sostenibilidad ambiental Alimentos y agricultura Materiales Edificación y construcción Ingeniería Sobre nosotros Perspectivas y actualidad Perspectivas Todos los artículos Salud Inteligencia artificial Cambio climático Transporte Ciberseguridad Gestión de la calidad Energías renovables Seguridad y salud en el trabajo Actualidad Opinión de expertos El mundo de las normas Kit de prensa Resources ISO 22000 explained ISO 9001 explained ISO 14001 explained Participar Tienda Buscar Carrito Publicly Available Specification Vista previa ISO/UNDP PAS 53002:2024 87945 ISO/UNDP PAS 53002:2024 Directrices para contribuir a los Objetivos de Desarrollo Sostenible (ODS) de las Naciones Unidas Publicado (Edición 1, 2024) ISO/UNDP PAS 53002:2024 ISO/UNDP PAS 53002:2024 87945 Idioma Inglés Español Formato PDF + PDF en color + ePub PDF + ePub PDF + PDF en color + ePub PDF + ePub CHF 0 Añadir al carrito * Gastos de envío no incluidos ¿Qué es la ISO/UNDP PAS 53002? Las directrices ISO/PNUD para los ODS (ISO/UNDP PAS 53002) son un documento de orientación para ayudar a las organizaciones a contribuir a los Objetivos de Desarrollo Sostenible (OSD) de las Naciones Unidas . Han sido elaboradas en colaboración con el Programa de las Naciones Unidas para el Desarrollo (PNUD) con el fin de proporcionar a las organizaciones un enfoque unificado para gestionar y optimizar sistemáticamente su impacto en el desarrollo sostenible a través de diversos aspectos operativos. ¿Por qué son importantes las directrices ISO/PNUD para los ODS? Esas directrices son cruciales para promover un enfoque holístico del desarrollo sostenible , que permita a las organizaciones contribuir positivamente a los ODS . Proporcionan un marco estructurado para maximizar los impactos positivos y reducir los negativos, en particular para los grupos vulnerables. Mediante medidas proactivas e integrando el desarrollo sostenible en las operaciones empresariales y los procesos de toma de decisiones, garantizan un enfoque equilibrado de la sostenibilidad económica, social y medioambiental . ¿Para quién son? Las directrices son relevantes para las organizaciones de todos los sectores. Están dirigidas a los responsables de la toma de decisiones al más alto nivel, quienes pueden aplicarlas para determinar cómo lograr un impacto positivo tangible basado en su propio y único contexto. Beneficios Alinean las estrategias organizativas con los Objetivos de desarrollo sostenible Mejoran el compromiso de las partes interesadas y su contribución a la sociedad Mejoran los informes de sostenibilidad y la transparencia Apoyan la gestión de riesgos relacionados con cuestiones de sostenibilidad Preguntas frecuentes ¿Quién debería aplicar la ISO/UNDP 53002? Organizaciones de los sectores público y privado de todo el mundo -grandes o pequeñas, nuevas o bien establecidas- que buscan integrar estrategias relacionadas con los ODS en sus operaciones. ¿Cómo complementa la ISO/UNDP 53002 a otras normas de sostenibilidad? Las directrices complementan las normas de sostenibilidad existentes al proporcionar un enfoque sobre la alineación de las estrategias y operaciones organizativas con los ODS en su conjunto . Complementa normas como la ISO 14001 , que se centra en los sistemas de gestión ambiental, y la ISO 22000 , que aborda la gestión de la inocuidad de los alimentos), así como las normas ISO relativas a la economía circular, incluida la ISO 59020 . En conjunto, estas normas permiten a las organizaciones mejorar su rendimiento en materia de sostenibilidad en varias dimensiones. ¿Qué hace única a la ISO/UNDP 53002? Las directrices ISO/PNUD para los ODS tienen como objetivo ayudar a las organizaciones a pasar de la alineación con los ODS a colocar los ODS en el centro de sus actividades . ¿Quién elaboró la ISO/UNDP 53002? Las directrices fueron elaboradas por un grupo internacional de expertos de la ISO y el PNUD reunidos por Danish Standards, miembro de la ISO para Dinamarca . Danish Standards ostenta la Secretaría del comité técnico para las directrices, el ISO/PC 343, Sustainable development goals management . ¿Qué es una ISO/PAS? Una especificación disponible públicamente (PAS) se publica para responder a una necesidad urgente del mercado , representando bien el consenso de los expertos dentro de un grupo de trabajo, bien un consenso en una organización externa a ISO. Al igual que las especificaciones técnicas (TS), las especificaciones públicamente disponibles se publican para su uso inmediato y también sirven como medio para obtener comentarios para una eventual transformación en una Norma internacional. Obtenga un valor añadido en su buzón Regístrese para obtener actualizaciones y recursos adicionales. Website Suscribirse * ¡Ya casi está! Sólo le falta un paso para unirse a la lista de suscriptores de ISO. Confirme su suscripción haciendo clic en el correo electrónico que acabamos de enviarle. No estará registrado hasta que confirme su suscripción. Si no encuentra el correo electrónico, compruebe su carpeta de correo no deseado y/o la pestaña de promociones (si utiliza Gmail). * Boletín de noticias en inglés Para saber cómo se utilizarán sus datos, consulte nuestro aviso de privacidad . Este sitio está protegido por reCAPTCHA. Se aplican la Política de privacidad y las Condiciones del servicio de Google Cómo se utilizarán sus datos Consulte nuestro aviso de privacidad . Este sitio está protegido por reCAPTCHA. Se aplican la Política de privacidad y las Condiciones del servicio de Google Informaciones generales Estado : Publicado Fecha de publicación : 2024-09 Etapa : Norma Internacional para revisar [ 90.92 ] Edición : 1 Número de páginas : 39 Comité Técnico : ISO/PC 343 ICS : 13.020.20 RSS actualizaciones Descargar ISO pone a disposición del público estas directrices (ISO/UNDP PAS 53002) para contribuir a los Objetivos de Desarrollo Sostenible de las Naciones Unidas. Acceso a las Directrices 12 septiembre 2024 Directrices internacionales únicas en el mundo para empoderar a las empresas y organizaciones para acelerar el éxito de los ODS ISO y el Programa de las Naciones Unidas para el Desarrollo (PNUD) han dado a conocer como novedad mundial las primeras directrices internacionales para ayudar a las empresas y organizaciones a agilizar … Ciclo de vida Ahora Publicado ISO/UNDP PAS 53002:2024 Las normas se revisan cada 5 años Etapa: 90.92 (Para revisar) 00 Preliminar 10 Propuesta 10.99 2023-10-06 Nuevo proyecto aprobado 20 Preparación 20.20 2023-10-06 Estudio del borrador del trabajo (WD) iniciado 30 Comité 30.99 2023-11-23 CD aprobado para su registro como DIS 40 Consulta 50 Aprobación 50.00 2023-11-28 Texto final recibido o FDIS registrado para su aprobación formal 50.20 2023-12-18 Envío de la prueba a la secretaría o inicio de la votación del FDIS: 8 semanas 50.60 2024-02-13 Cierre de la votación. Prueba devuelta por la secretaría 60 Publicación 60.00 2024-02-13 Norma Internacional en proceso de publicación 60.60 2024-09-12 Norma Internacional publicada 90 Revisión 90.92 2025-08-13 Norma Internacional para revisar 90.93 Norma Internacional confirmada 90.99 Retirada de la Norma Internacional propuesta por TC o SC 95 Retirada 95.99 Retirada de la Norma Internacional Será reemplazada por En desarrollo ISO/UNDP DIS 53002 Esta norma contribuye a los siguientes Objetivos de Desarrollo Sostenible 1 No Poverty 2 Zero Hunger 3 Good Health and Well-being 4 Quality Education 5 Gender Equality 6 Clean Water and Sanitation 7 Affordable and Clean Energy 8 Decent Work and Economic Growth 9 Industry, Innovation and Infrastructure 10 Reduced Inequalities 11 Sustainable Cities and Communities 12 Responsible Consumption and Production 13 Climate Action 14 Life Below Water 15 Life on Land 16 Peace, Justice and Strong Institutions ¿Tiene alguna duda? Consulte nuestras Ayuda y asistencia Tienda Tienda ICS 13 13.020 13.020.20 ISO/UNDP PAS 53002:2024 Mapa del sitio Normas Beneficios Normas más comunes Evaluación de la conformidad ODS Sectores Salud Tecnologías de la información y afines Gestión y servicios Seguridad, protección y gestión de riesgos Transporte Energía Sostenibilidad ambiental Materiales Sobre nosotros Qué es lo que hacemos Estructura Miembros Events Estrategia Perspectivas y actualidad Perspectivas Todos los artículos Salud Inteligencia artificial Cambio climático Transporte Actualidad Opinión de expertos El mundo de las normas Kit de prensa Resources ISO 22000 explained ISO 9001 explained ISO 14001 explained Participar Who develops standards Deliverables Get involved Colaboración para acelerar una acción climática eficaz Resources Drafting standards Tienda Tienda Publications and products ISO name and logo Privacy Notice Copyright Cookie policy Media kit Jobs Help and support Seguimos haciendo que la vida sea mejor , más fácil y más segura . Inscríbase para recibir actualizaciones por correo electrónico © Reservados todos los derechos Todos los materiales y publicaciones de ISO están protegidos por derechos de autor y sujetos a la aceptación por parte del usuario de las condiciones de derechos de autor de ISO. Cualquier uso, incluida la reproducción, requiere nuestra autorización por escrito. Dirija todas las solicitudes relacionadas con los derechos de autor a copyright@iso.org . Nos comprometemos a garantizar que nuestro sitio web sea accesible para todo el mundo. Si tiene alguna pregunta o sugerencia relacionada con la accesibilidad de este sitio web, póngase en contacto con nosotros. Añadir al carrito | 2026-01-13T09:30:34 |
https://zh-cn.facebook.com/login/?next=https%3A%2F%2Fl.facebook.com%2Fl.php%3Fu%3Dhttps%253A%252F%252Fwww.instagram.com%252F%26amp%253Bh%3DAT0ODBxi9Ky_q5Zd-o4dYpnmHyfX6cU94o0TSebfXayTVSpJVZhsLNiaEOYJD4tF5NyHmlhcHvBZpujDEdp7WEIct_OsB2vtYxvgex9BobCz0QD-I7CT9qU5M2_9NMDpfEnKNwsIMtWszByH | Facebook Facebook 邮箱或手机号 密码 忘记账户了？ 创建新账户 你暂时被禁止使用此功能 你暂时被禁止使用此功能 似乎你过度使用了此功能，因此暂时被阻止，不能继续使用。 Back 中文(简体) 한국어 English (US) Tiếng Việt Bahasa Indonesia ภาษาไทย Español 日本語 Português (Brasil) Français (France) Deutsch 注册 登录 Messenger Facebook Lite 视频 Meta Pay Meta 商店 Meta Quest Ray-Ban Meta Meta AI Meta AI 更多内容 Instagram Threads 选民信息中心 隐私政策 隐私中心 关于 创建广告 创建公共主页 开发者 招聘信息 Cookie Ad Choices 条款 帮助 联系人上传和非用户 设置 动态记录 Meta © 2026 | 2026-01-13T09:30:34 |
https://logging.apache.org/download.html | Download :: Apache Logging Services Logging Services a project of Apache Software Foundation Home About Guidelines Charter Team Processes Wiki What is logging? Download Support Security XML Schema Blog The ASF License Donate Thanks Home Download Edit this Page Download You can use one of the following channels to download the Logging Services release distributions. All Logging Services projects distribute convenience binaries that are easy to install for the programming language platform they target. You are strongly advised to check the installation instructions in the website of the project ( Log4cxx , Log4j , Log4net , etc.) you are trying to install. Official distribution channels In accordance with the Apache Software Foundation’s release distribution policy and creation process , all Logging Services release distributions are officially accessible from the following channels: ASF Distribution directory (contains the most recent releases ) ASF Distribution directory archive (contains all published releases) Java distribution channels ASF Release and snapshot Nexus repositories (mirrored to the Maven Central Repository ) .NET distribution channels asf organization in NuGet Verification All Logging Services release distributions are digitally signed by the release manager and provided with checksum files. You can verify a distribution by following instructions: Linux/macOS Windows # Download and import the release manager public keys wget -O - https://downloads.apache.org/logging/KEYS | gpg --import # Verify signatures for sigFile in *.asc; do gpg --verify $sigFile ${sigFile%.asc}; done # Verify checksums shasum --check *.sha512 Download the release manager public keys Use gpg --import to import the keys Verify signature files: gpg --verify some.file.asc some.file Verify checksums: certUtil -hashfile some.file SHA512 Software Bill of Materials (SBOM) Many Logging Services projects distribute CycloneDX Software Bill of Materials (SBOM) along with each deployed artifact. This is streamlined by Logging Parent for Maven-based projects. Produced SBOMs contain BOM-links referring to a CycloneDX Vulnerability Disclosure Report (VDR) that Apache Logging Services uses for all projects it maintains. This VDR is accessible through the following URL: https://logging.apache.org/cyclonedx/vdr.xml Copyright © 1999-2026 The Apache Software Foundation . Licensed under the Apache Software License, Version 2.0 . Please read our privacy policy . Apache, Log4j, and the Apache feather logo are trademarks or registered trademarks of The Apache Software Foundation. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. | 2026-01-13T09:30:34 |
https://releases.llvm.org/18.1.8/tools/clang/docs/ReleaseNotes.html | Clang 18.1.8 Release Notes — Clang 18.1.8 documentation Clang 18.1.8 documentation Clang 18.1.8 Release Notes «   Using Clang as a Compiler   ::   Contents   ::   Clang Compiler User’s Manual   » Clang 18.1.8 Release Notes ¶ Introduction Potentially Breaking Changes C/C++ Language Potentially Breaking Changes C++ Specific Potentially Breaking Changes ABI Changes in This Version AST Dumping Potentially Breaking Changes Clang Frontend Potentially Breaking Changes What’s New in Clang 18.1.8? C++ Language Changes C Language Changes Non-comprehensive list of changes in this release New Compiler Flags Deprecated Compiler Flags Modified Compiler Flags Removed Compiler Flags Attribute Changes in Clang Improvements to Clang’s diagnostics Improvements to Clang’s time-trace Bug Fixes in This Version OpenACC Specific Changes Target Specific Changes DWARF Support in Clang Floating Point Support in Clang AST Matchers clang-format libclang Static Analyzer Sanitizers Python Binding Changes Additional Information Written by the LLVM Team Introduction ¶ This document contains the release notes for the Clang C/C++/Objective-C frontend, part of the LLVM Compiler Infrastructure, release 18.1.8. Here we describe the status of Clang in some detail, including major improvements from the previous release and new feature work. For the general LLVM release notes, see the LLVM documentation . For the libc++ release notes, see this page . All LLVM releases may be downloaded from the LLVM releases web site . For more information about Clang or LLVM, including information about the latest release, please see the Clang Web Site or the LLVM Web Site . Potentially Breaking Changes ¶ These changes are ones which we think may surprise users when upgrading to Clang 18.1.8 because of the opportunity they pose for disruption to existing code bases. Fix a bug in reversed argument for templated operators. This breaks code in C++20 which was previously accepted in C++17. Clang did not properly diagnose such casese in C++20 before this change. Eg: struct P {}; template < class S > bool operator == ( const P & , const S & ); struct A : public P {}; struct B : public P {}; // This equality is now ambiguous in C++20. bool ambiguous ( A a , B b ) { return a == b ; } template < class S > bool operator != ( const P & , const S & ); // Ok. Found a matching operator!=. bool fine ( A a , B b ) { return a == b ; } To reduce such widespread breakages, as an extension, Clang accepts this code with an existing warning -Wambiguous-reversed-operator warning. Fixes #53954 . The CMake variable GCC_INSTALL_PREFIX (which sets the default --gcc-toolchain= ) is deprecated and will be removed. Specify --gcc-install-dir= or --gcc-triple= in a configuration file as a replacement. ( #77537 ) C/C++ Language Potentially Breaking Changes ¶ The default extension name for PCH generation ( -c -xc-header and -c -xc++-header ) is now .pch instead of .gch . -include a.h probing a.h.gch will now ignore a.h.gch if it is not a clang pch file or a directory containing any clang pch file. Fixed a bug that caused __has_cpp_attribute and __has_c_attribute return incorrect values for some C++-11-style attributes. Below is a complete list of behavior changes. Test Old value New value __has_cpp_attribute(unused) 201603 0 __has_cpp_attribute(gnu::unused) 201603 1 __has_c_attribute(unused) 202106 0 __has_cpp_attribute(clang::fallthrough) 201603 1 __has_cpp_attribute(gnu::fallthrough) 201603 1 __has_c_attribute(gnu::fallthrough) 201910 1 __has_cpp_attribute(warn_unused_result) 201907 0 __has_cpp_attribute(clang::warn_unused_result) 201907 1 __has_cpp_attribute(gnu::warn_unused_result) 201907 1 __has_c_attribute(warn_unused_result) 202003 0 __has_c_attribute(gnu::warn_unused_result) 202003 1 Fixed a bug in finding matching operator!= while adding reversed operator== as outlined in “The Equality Operator You Are Looking For” ( P2468 ). Fixes ( #68901 ). C++ Specific Potentially Breaking Changes ¶ The name mangling rules for function templates has been changed to take into account the possibility that functions could be overloaded on their template parameter lists or requires-clauses. This causes mangled names to change for function templates in the following cases: When a template parameter in a function template depends on a previous template parameter, such as template<typename T, T V> void f() . When the function has any constraints, whether from constrained template parameters or requires-clauses. When the template parameter list includes a deduced type – either auto , decltype(auto) , or a deduced class template specialization type. When a template template parameter is given a template template argument that has a different template parameter list. This fixes a number of issues where valid programs would be rejected due to mangling collisions, or would in some cases be silently miscompiled. Clang will use the old manglings if -fclang-abi-compat=17 or lower is specified. ( #48216 ), ( #49884 ), and ( #61273 ) The ClassScopeFunctionSpecializationDecl AST node has been removed. Dependent class scope explicit function template specializations now use DependentFunctionTemplateSpecializationInfo to store candidate primary templates and explicit template arguments. This should not impact users of Clang as a compiler, but it may break assumptions in Clang-based tools iterating over the AST. The warning -Wenum-constexpr-conversion is now also enabled by default on system headers and macros. It will be turned into a hard (non-downgradable) error in the next Clang release. The flag -fdelayed-template-parsing won’t be enabled by default with C++20 when targetting MSVC to match the behavior of MSVC. ( MSVC Docs ) Remove the hardcoded path to the imported modules for C++20 named modules. Now we require all the dependent modules to specified from the command line. See ( #62707 ). Forbid import XXX; in C++ to find module XXX comes from explicit clang modules. See ( #64755 ). ABI Changes in This Version ¶ Following the SystemV ABI for x86-64, __int128 arguments will no longer be split between a register and a stack slot. Fixed Microsoft calling convention for returning certain classes with a templated constructor. If a class has a templated constructor, it should be returned indirectly even if it meets all the other requirements for returning a class in a register. This affects some uses of std::pair. (#GH86384). AST Dumping Potentially Breaking Changes ¶ When dumping a sugared type, Clang will no longer print the desugared type if its textual representation is the same as the sugared one. This applies to both text dumps of the form 'foo':'foo' which will now be dumped as just 'foo' , and JSON dumps of the form: "type" : { "qualType" : "foo" , "desugaredQualType" : "foo" } which will now be dumped as just: "type" : { "qualType" : "foo" } Clang Frontend Potentially Breaking Changes ¶ Target OS macros extension A new Clang extension (see here ) is enabled for Darwin (Apple platform) targets. Clang now defines TARGET_OS_* macros for these targets, which could break existing code bases with improper checks for the TARGET_OS_ macros. For example, existing checks might fail to include the TargetConditionals.h header from Apple SDKs and therefore leaving the macros undefined and guarded code unexercised. Affected code should be checked to see if it’s still intended for the specific target and fixed accordingly. The extension can be turned off by the option -fno-define-target-os-macros as a workaround. What’s New in Clang 18.1.8? ¶ Some of the major new features and improvements to Clang are listed here. Generic improvements to Clang as a whole or to its underlying infrastructure are described first, followed by language-specific sections with improvements to Clang’s support for those languages. C++ Language Changes ¶ C++20 Feature Support ¶ Implemented P1907R1 which extends allowed non-type template argument kinds with e.g. floating point values and pointers and references to subobjects. This feature is still experimental. Accordingly, __cpp_nontype_template_args was not updated. However, its support can be tested with __has_extension(cxx_generalized_nttp) . Clang won’t perform ODR checks for decls in the global module fragment any more to ease the implementation and improve the user’s using experience. This follows the MSVC’s behavior. Users interested in testing the more strict behavior can use the flag ‘-Xclang -fno-skip-odr-check-in-gmf’. ( #79240 ). C++23 Feature Support ¶ Implemented P0847R7: Deducing this . Some related core issues were also implemented ( CWG2553 , CWG2554 , CWG2653 , CWG2687 ). Because the support for this feature is still experimental, the feature test macro __cpp_explicit_this_parameter was not set in this version. However, its support can be tested with __has_extension(cxx_explicit_this_parameter) . Added a separate warning to warn the use of attributes on lambdas as a C++23 extension in previous language versions: -Wc++23-lambda-attributes . C++2c Feature Support ¶ Implemented P2169R4: A nice placeholder with no name . This allows using _ as a variable name multiple times in the same scope and is supported in all C++ language modes as an extension. An extension warning is produced when multiple variables are introduced by _ in the same scope. Unused warnings are no longer produced for variables named _ . Currently, inspecting placeholders variables in a debugger when more than one are declared in the same scope is not supported. struct S { int _ , _ ; // Was invalid, now OK }; void func () { int _ , _ ; // Was invalid, now OK } void other () { int _ ; // Previously diagnosed under -Wunused, no longer diagnosed } Attributes now expect unevaluated strings in attributes parameters that are string literals. This is applied to both C++ standard attributes, and other attributes supported by Clang. This completes the implementation of P2361R6 Unevaluated Strings Implemented P2864R2 Remove Deprecated Arithmetic Conversion on Enumerations From C++26 . Implemented P2361R6 Template parameter initialization . This change is applied as a DR in all language modes. Resolutions to C++ Defect Reports ¶ Implemented CWG2598 and CWG2096 , making unions (that have either no members or at least one literal member) literal types. ( #77924 ). C Language Changes ¶ structs , unions , and arrays that are const may now be used as constant expressions. This change is more consistent with the behavior of GCC. Enums will now be represented in TBAA metadata using their actual underlying integer type. Previously they were treated as chars, which meant they could alias with all other types. Clang now supports the C-only attribute counted_by . When applied to a struct’s flexible array member, it points to the struct field that holds the number of elements in the flexible array member. This information can improve the results of the array bound sanitizer and the __builtin_dynamic_object_size builtin. C23 Feature Support ¶ Clang now accepts -std=c23 and -std=gnu23 as language standard modes, and the __STDC_VERSION__ macro now expands to 202311L instead of its previous placeholder value. Clang continues to accept -std=c2x and -std=gnu2x as aliases for C23 and GNU C23, respectively. Clang now supports requires c23 for module maps. Clang now supports N3007 Type inference for object definitions . Clang now supports <stdckdint.h> which defines several macros for performing checked integer arithmetic. It is also exposed in pre-C23 modes. Completed the implementation of N2508 . We previously implemented allowing a label at the end of a compound statement, and now we’ve implemented allowing a label to be followed by a declaration instead of a statement. Implemented N2940 which removes support for trigraphs in C23 and later. In earlier language modes, trigraphs remain enabled by default in conforming modes (e.g. -std=c17 ) and disabled by default in GNU and Microsoft modes (e.g., -std=gnu17 or -fms-compatibility ). If needed, you can enable trigraphs by passing -ftrigraphs . Non-comprehensive list of changes in this release ¶ Clang now has a __builtin_vectorelements() function that determines the number of elements in a vector. For fixed-sized vectors, e.g., defined via __attribute__((vector_size(N))) or ARM NEON’s vector types (e.g., uint16x8_t ), this returns the constant number of elements at compile-time. For scalable vectors, e.g., SVE or RISC-V V, the number of elements is not known at compile-time and is determined at runtime. The __datasizeof keyword has been added. It is similar to sizeof except that it returns the size of a type ignoring tail padding. __builtin_classify_type() now classifies _BitInt values as the return value 18 and vector types as return value 19 , to match GCC 14’s behavior. The default value of _MSC_VER was raised from 1920 to 1933. Since MSVC 19.33 added undocumented attribute [[msvc::constexpr]] , this release adds the attribute as well. Added #pragma clang fp reciprocal . The version of Unicode used by Clang (primarily to parse identifiers) has been updated to 15.1. Clang now defines macro __LLVM_INSTR_PROFILE_GENERATE when compiling with PGO instrumentation profile generation, and __LLVM_INSTR_PROFILE_USE when compiling with PGO profile use. New Compiler Flags ¶ -fverify-intermediate-code and its complement -fno-verify-intermediate-code . Enables or disables verification of the generated LLVM IR. Users can pass this to turn on extra verification to catch certain types of compiler bugs at the cost of extra compile time. Since enabling the verifier adds a non-trivial cost of a few percent impact on build times, it’s disabled by default, unless your LLVM distribution itself is compiled with runtime checks enabled. -fkeep-system-includes modifies the behavior of the -E option, preserving #include directives for “system” headers instead of copying the preprocessed text to the output. This can greatly reduce the size of the preprocessed output, which can be helpful when trying to reduce a test case. -fassume-nothrow-exception-dtor is added to assume that the destructor of a thrown exception object will not throw. The generated code for catch handlers will be smaller. A throw expression of a type with a potentially-throwing destructor will lead to an error. -fopenacc was added as a part of the effort to support OpenACC in Clang. -fcx-limited-range enables the naive mathematical formulas for complex division and multiplication with no NaN checking of results. The default is -fno-cx-limited-range , but this option is enabled by -ffast-math . -fcx-fortran-rules enables the naive mathematical formulas for complex multiplication and enables application of Smith’s algorithm for complex division. See SMITH, R. L. Algorithm 116: Complex division. Commun. ACM 5, 8 (1962). The default is -fno-cx-fortran-rules . -fvisibility-global-new-delete=<value> gives more freedom to users to control how and if Clang forces a visibility for the replaceable new and delete declarations. The option takes 4 values: force-hidden , force-protected , force-default and source ; force-default is the default. Option values with prefix force- assign such declarations an implicit visibility attribute with the corresponding visibility. An option value of source implies that no implicit attribute is added. Without the attribute the replaceable global new and delete operators behave normally (like other functions) with respect to visibility attributes, pragmas and options (e.g --fvisibility= ). Full register names can be used when printing assembly via -mregnames . This option now matches the one used by GCC. -fdefine-target-os-macros and its complement -fno-define-target-os-macros . Enables or disables the Clang extension to provide built-in definitions of a list of TARGET_OS_* macros based on the target triple. The extension is enabled by default for Darwin (Apple platform) targets. Deprecated Compiler Flags ¶ Modified Compiler Flags ¶ -Woverriding-t-option is renamed to -Woverriding-option . -Winterrupt-service-routine is renamed to -Wexcessive-regsave as a generalization -frewrite-includes now guards the original #include directives with __CLANG_REWRITTEN_INCLUDES , and __CLANG_REWRITTEN_SYSTEM_INCLUDES as appropriate. Introducing a new default calling convention for -fdefault-calling-conv : rtdcall . This new default CC only works for M68k and will use the new m68k_rtdcc CC on every functions that are not variadic. The -mrtd driver/frontend flag has the same effect when targeting M68k. -fvisibility-global-new-delete-hidden is now a deprecated spelling of -fvisibility-global-new-delete=force-hidden ( -fvisibility-global-new-delete= is new in this release). -fprofile-update is enabled for -fprofile-generate . Removed Compiler Flags ¶ -enable-trivial-auto-var-init-zero-knowing-it-will-be-removed-from-clang has been removed. It has not been needed to enable -ftrivial-auto-var-init=zero since Clang 16. Attribute Changes in Clang ¶ On X86, a warning is now emitted if a function with __attribute__((no_caller_saved_registers)) calls a function without __attribute__((no_caller_saved_registers)) , and is not compiled with -mgeneral-regs-only On X86, a function with __attribute__((interrupt)) can now call a function without __attribute__((no_caller_saved_registers)) provided that it is compiled with -mgeneral-regs-only When a non-variadic function is decorated with the format attribute, Clang now checks that the format string would match the function’s parameters’ types after default argument promotion. As a result, it’s no longer an automatic diagnostic to use parameters of types that the format style supports but that are never the result of default argument promotion, such as float . ( #59824 ) Clang now supports [[clang::preferred_type(type-name)]] as an attribute which can be applied to a bit-field. This attribute helps to map a bit-field back to a particular type that may be better-suited to representing the bit- field but cannot be used for other reasons and will impact the debug information generated for the bit-field. This is most useful when mapping a bit-field of basic integer type back to a bool or an enumeration type, e.g., enum E { Apple , Orange , Pear }; struct S { [[ clang :: preferred_type ( E )]] unsigned FruitKind : 2 ; }; When viewing S::FruitKind in a debugger, it will behave as if the member was declared as type E rather than unsigned . Clang now warns you that the _Alignas attribute on declaration specifiers is ignored, changed from the former incorrect suggestion to move it past declaration specifiers. ( #58637 ) Clang now introduced [[clang::coro_only_destroy_when_complete]] attribute to reduce the size of the destroy functions for coroutines which are known to be destroyed after having reached the final suspend point. Clang now introduced [[clang::coro_return_type]] and [[clang::coro_wrapper]] attributes. A function returning a type marked with [[clang::coro_return_type]] should be a coroutine. A non-coroutine function marked with [[clang::coro_wrapper]] is still allowed to return the such a type. This is helpful for analyzers to recognize coroutines from the function signatures. Clang now supports [[clang::code_align(N)]] as an attribute which can be applied to a loop and specifies the byte alignment for a loop. This attribute accepts a positive integer constant initialization expression indicating the number of bytes for the minimum alignment boundary. Its value must be a power of 2, between 1 and 4096(inclusive). void Array ( int * array , size_t n ) { [[ clang :: code_align ( 64 )]] for ( int i = 0 ; i < n ; ++ i ) array [ i ] = 0 ; } template < int A > void func () { [[ clang :: code_align ( A )]] for (;;) { } } Clang now introduced [[clang::coro_lifetimebound]] attribute. All parameters of a function are considered to be lifetime bound if the function returns a type annotated with [[clang::coro_lifetimebound]] and [[clang::coro_return_type]] . This analysis can be disabled for a function by annotating the function with [[clang::coro_disable_lifetimebound]] . Improvements to Clang’s diagnostics ¶ Clang constexpr evaluator now prints template arguments when displaying template-specialization function calls. Clang contexpr evaluator now displays notes as well as an error when a constructor of a base class is not called in the constructor of its derived class. Clang no longer emits -Wmissing-variable-declarations for variables declared with the register storage class. Clang’s -Wswitch-default flag now diagnoses whenever a switch statement does not have a default label. Clang’s -Wtautological-negation-compare flag now diagnoses logical tautologies like x && !x and !x || x in expressions. This also makes -Winfinite-recursion diagnose more cases. ( #56035 ). Clang constexpr evaluator now diagnoses compound assignment operators against uninitialized variables as a read of uninitialized object. ( #51536 ) Clang’s -Wformat-truncation now diagnoses snprintf call that is known to result in string truncation. ( #64871 ). Existing warnings that similarly warn about the overflow in sprintf now falls under its own warning group `-Wformat-overflow so that it can be disabled separately from Wfortify-source . These two new warning groups have subgroups -Wformat-truncation-non-kprintf and -Wformat-overflow-non-kprintf , respectively. These subgroups are used when the format string contains %p format specifier. Because Linux kernel’s codebase has format extensions for %p , kernel developers are encouraged to disable these two subgroups by setting -Wno-format-truncation-non-kprintf and -Wno-format-overflow-non-kprintf in order to avoid false positives on the kernel codebase. Also clang no longer emits false positive warnings about the output length of %g format specifier and about %o, %x, %X with # flag. Clang now emits -Wcast-qual for functional-style cast expressions. Clang no longer emits irrelevant notes about unsatisfied constraint expressions on the left-hand side of || when the right-hand side constraint is satisfied. ( #54678 ). Clang now prints its ‘note’ diagnostic in cyan instead of black, to be more compatible with terminals with dark background colors. This is also more consistent with GCC. Clang now displays an improved diagnostic and a note when a defaulted special member is marked constexpr in a class with a virtual base class ( #64843 ). -Wfixed-enum-extension and -Wmicrosoft-fixed-enum diagnostics are no longer emitted when building as C23, since C23 standardizes support for enums with a fixed underlying type. When describing the failure of static assertion of == expression, clang prints the integer representation of the value as well as its character representation when the user-provided expression is of character type. If the character is non-printable, clang now shows the escpaed character. Clang also prints multi-byte characters if the user-provided expression is of multi-byte character type. Example Code : static_assert ( "A \n " [ 1 ] == U '🌍' ); BEFORE : source:1:15: error: static assertion failed due to requirement '"A\n"[1] == U'\U0001f30d'' 1 | static_assert("A\n"[1] == U'🌍'); | ^~~~~~~~~~~~~~~~~ source:1:24: note: expression evaluates to '' ' == 127757' 1 | static_assert("A\n"[1] == U'🌍'); | ~~~~~~~~~^~~~~~~~ AFTER : source:1:15: error: static assertion failed due to requirement '"A\n"[1] == U'\U0001f30d'' 1 | static_assert("A\n"[1] == U'🌍'); | ^~~~~~~~~~~~~~~~~ source:1:24: note: expression evaluates to ''\n' (0x0A, 10) == U'🌍' (0x1F30D, 127757)' 1 | static_assert("A\n"[1] == U'🌍'); | ~~~~~~~~~^~~~~~~~ Clang now always diagnoses when using non-standard layout types in offsetof . ( #64619 ) Clang now diagnoses redefined defaulted constructor when redefined defaulted constructor with different exception specs. ( #69094 ) Clang now diagnoses use of variable-length arrays in C++ by default (and under -Wall in GNU++ mode). This is an extension supported by Clang and GCC, but is very easy to accidentally use without realizing it’s a nonportable construct that has different semantics from a constant-sized array. ( #62836 ) Clang changed the order in which it displays candidate functions on overloading failures. Previously, Clang used definition of ordering from the C++ Standard. The order defined in the Standard is partial and is not suited for sorting. Instead, Clang now uses a strict order that still attempts to push more relevant functions to the top by comparing their corresponding conversions. In some cases, this results in better order. E.g., for the following code struct Foo { operator int (); operator const char * (); }; void test () { Foo () - Foo (); } Clang now produces a list with two most relevant builtin operators at the top, i.e. operator-(int, int) and operator-(const char*, const char*) . Previously operator-(const char*, const char*) was the first element, but operator-(int, int) was only the 13th element in the output. However, new implementation does not take into account some aspects of C++ semantics, e.g. which function template is more specialized. This can sometimes lead to worse ordering. When describing a warning/error in a function-style type conversion Clang underlines only until the end of the expression we convert from. Now Clang underlines until the closing parenthesis. Before: warning: cast from 'long (*)(const int &)' to 'decltype(fun_ptr)' (aka 'long (*)(int &)') converts to incompatible function type [-Wcast-function-type-strict] 24 | return decltype(fun_ptr)( f_ptr /*comment*/); | ^~~~~~~~~~~~~~~~~~~~~~~~ After: warning: cast from 'long (*)(const int &)' to 'decltype(fun_ptr)' (aka 'long (*)(int &)') converts to incompatible function type [-Wcast-function-type-strict] 24 | return decltype(fun_ptr)( f_ptr /*comment*/); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -Wzero-as-null-pointer-constant diagnostic is no longer emitted when using __null (or, more commonly, NULL when the platform defines it as __null ) to be more consistent with GCC. Clang will warn on deprecated specializations used in system headers when their instantiation is caused by user code. Clang will now print static_assert failure details for arithmetic binary operators. Example: static_assert ( 1 << 4 == 15 ); will now print: error: static assertion failed due to requirement '1 << 4 == 15' 48 | static_assert(1 << 4 == 15); | ^~~~~~~~~~~~ note: expression evaluates to '16 == 15' 48 | static_assert(1 << 4 == 15); | ~~~~~~~^~~~~ Clang now diagnoses definitions of friend function specializations, e.g. friend void f<>(int) {} . Clang now diagnoses narrowing conversions involving const references. ( #63151 ). Clang now diagnoses unexpanded packs within the template argument lists of function template specializations. The warning -Wnan-infinity-disabled is now emitted when INFINITY or NAN are used in arithmetic operations or function arguments in floating-point mode where INFINITY or NAN don’t have the expected values. Clang now diagnoses attempts to bind a bitfield to an NTTP of a reference type as erroneous converted constant expression and not as a reference to subobject. Clang now diagnoses auto and decltype(auto) in declarations of conversion function template ( CWG1878 ) Clang now diagnoses the requirement that non-template friend declarations with requires clauses and template friend declarations with a constraint that depends on a template parameter from an enclosing template must be a definition. Clang now diagnoses incorrect usage of const and pure attributes, so -Wignored-attributes diagnoses more cases. Clang now emits more descriptive diagnostics for ‘unusual’ expressions (e.g. incomplete index expressions on matrix types or builtin functions without an argument list) as placement-args to new-expressions. Before: error: no matching function for call to 'operator new' 13 | new (__builtin_memset) S {}; | ^ ~~~~~~~~~~~~~~~~~~ note: candidate function not viable: no known conversion from '<builtin fn type>' to 'int' for 2nd argument 5 | void* operator new(__SIZE_TYPE__, int); | ^ After: error: builtin functions must be directly called 13 | new (__builtin_memset) S {}; | ^ Clang now diagnoses import before module declarations but not in global module fragment. ( #67627 ). Clang now diagnoses include headers with angle in module purviews, which is not usually intended. ( #68615 ) Clang now won’t mention invisible namespace when diagnose invisible declarations inside namespace. The original diagnostic message is confusing. ( #73893 ) Improvements to Clang’s time-trace ¶ Two time-trace scope variables are added. A time trace scope variable of ParseDeclarationOrFunctionDefinition with the function’s source location is added to record the time spent parsing the function’s declaration or definition. Another time trace scope variable of ParseFunctionDefinition is also added to record the name of the defined function. Bug Fixes in This Version ¶ Fixed an issue where a class template specialization whose declaration is instantiated in one module and whose definition is instantiated in another module may end up with members associated with the wrong declaration of the class, which can result in miscompiles in some cases. Fix crash on use of a variadic overloaded operator. ( #42535 ) Fix a hang on valid C code passing a function type as an argument to typeof to form a function declaration. ( #64713 ) Clang now reports missing-field-initializers warning for missing designated initializers in C++. ( #56628 ) Clang now respects -fwrapv and -ftrapv for __builtin_abs and abs builtins. ( #45129 , #45794 ) Fixed an issue where accesses to the local variables of a coroutine during await_suspend could be misoptimized, including accesses to the awaiter object itself. ( #56301 ) The current solution may bring performance regressions if the awaiters have non-static data members. See #64945 for details. Clang now prints unnamed members in diagnostic messages instead of giving an empty ‘’. Fixes ( #63759 ) Fix crash in __builtin_strncmp and related builtins when the size value exceeded the maximum value representable by int64_t. Fixes ( #64876 ) Fixed an assertion if a function has cleanups and fatal erors. ( #48974 ) Clang now emits an error if it is not possible to deduce array size for a variable with incomplete array type. ( #37257 ) Clang’s -Wunused-private-field no longer warns on fields whose type is declared with [[maybe_unused]] . ( #61334 ) For function multi-versioning using the target , target_clones , or target_version attributes, remove comdat for internal linkage functions. ( #65114 ) Clang now reports -Wformat for bool value and char specifier confusion in scanf. Fixes ( #64987 ) Support MSVC predefined macro expressions in constant expressions and in local structs. Correctly parse non-ascii identifiers that appear immediately after a line splicing ( #65156 ) Clang no longer considers the loss of __unaligned qualifier from objects as an invalid conversion during method function overload resolution. Fix lack of comparison of declRefExpr in ASTStructuralEquivalence ( #66047 ) Fix parser crash when dealing with ill-formed objective C++ header code. Fixes ( #64836 ) Fix crash in implicit conversions from initialize list to arrays of unknown bound for C++20. Fixes ( #62945 ) Clang now allows an _Atomic qualified integer in a switch statement. Fixes ( #65557 ) Fixes crash when trying to obtain the common sugared type of decltype(instantiation-dependent-expr) . Fixes ( #67603 ) Fixes a crash caused by a multidimensional array being captured by a lambda ( #67722 ). Fixes a crash when instantiating a lambda with requires clause. ( #64462 ) Fixes a regression where the UserDefinedLiteral was not properly preserved while evaluating consteval functions. ( #63898 ). Fix a crash when evaluating value-dependent structured binding variables at compile time. Fixes ( #67690 ) Fixes a clang-17 regression where LLVM_UNREACHABLE_OPTIMIZE=OFF cannot be used with Release mode builds. ( #68237 ). Fix crash in evaluating constexpr value for invalid template function. Fixes ( #68542 ) Clang will correctly evaluate noexcept expression for template functions of template classes. Fixes ( #68543 , #42496 , #77071 , #77411 ) Fixed an issue when a shift count larger than __INT64_MAX__ , in a right shift operation, could result in missing warnings about shift count >= width of type or internal compiler error. Fixed an issue with computing the common type for the LHS and RHS of a ?: operator in C. No longer issuing a confusing diagnostic along the lines of “incompatible operand types (‘foo’ and ‘foo’)” with extensions such as matrix types. Fixes ( #69008 ) Clang no longer permits using the _BitInt types as an underlying type for an enumeration as specified in the C23 Standard. Fixes ( #69619 ) Fixed an issue when a shift count specified by a small constant _BitInt() , in a left shift operation, could result in a faulty warnings about shift count >= width of type . Clang now accepts anonymous members initialized with designated initializers inside templates. Fixes ( #65143 ) Fix crash in formatting the real/imaginary part of a complex lvalue. Fixes ( #69218 ) No longer use C++ thread_local semantics in C23 when using thread_local instead of _Thread_local . Fixes ( #70068 ) and ( #69167 ) Fix crash in evaluating invalid lambda expression which forget capture this. Fixes ( #67687 ) Fix crash from constexpr evaluator evaluating uninitialized arrays as rvalue. Fixes ( #67317 ) Clang now properly diagnoses use of stand-alone OpenMP directives after a label (including case or default labels). Fix compiler memory leak for enums with underlying type larger than 64 bits. Fixes ( #78311 ) Before: label : #pragma omp barrier // ok After: label : #pragma omp barrier // error: '#pragma omp barrier' cannot be an immediate substatement Fixed an issue that a benign assertion might hit when instantiating a pack expansion inside a lambda. ( #61460 ) Fix crash during instantiation of some class template specializations within class templates. Fixes ( #70375 ) Fix crash during code generation of C++ coroutine initial suspend when the return type of await_resume is not trivially destructible. Fixes ( #63803 ) __is_trivially_relocatable no longer returns true for non-object types such as references and functions. Fixes ( #67498 ) Fix crash when the object used as a static_assert message has size or data members which are not member functions. Support UDLs in static_assert message. Fixed false positive error emitted by clang when performing qualified name lookup and the current class instantiation has dependent bases. Fixes ( #13826 ) Fix a clang-17 regression where a templated friend with constraints is not properly applied when its parameters reference an enclosing non-template class. Fixes ( #71595 ) Fix the name of the ifunc symbol emitted for multiversion functions declared with the target_clones attribute. This addresses a linker error that would otherwise occur when these functions are referenced from other TUs. Fixes compile error that double colon operator cannot resolve macro with parentheses. Fixes ( #64467 ) Clang’s -Wchar-subscripts no longer warns on chars whose values are known non-negative constants. Fixes ( #18763 ) Fix crash due to incorrectly allowing conversion functions in copy elision. Fixes ( #39319 ) and ( #60182 ) and ( #62157 ) and ( #64885 ) and ( #65568 ) Fix an issue where clang doesn’t respect detault template arguments that are added in a later redeclaration for CTAD. Fixes ( #69987 ) Fix an issue where CTAD fails for explicit type conversion. Fixes ( #64347 ) Fix crash when using C++ only tokens like :: in C compiler clang. Fixes ( #73559 ) Clang now accepts recursive non-dependent calls to functions with deduced return type. Fixes ( #71015 ) Fix assertion failure when initializing union containing struct with flexible array member using empty initializer list. Fixes ( #77085 ) Fix assertion crash due to failed scope restoring caused by too-early VarDecl invalidation by invalid initializer Expr. Fixes ( #30908 ) Clang now emits correct source location for code-coverage regions in if constexpr and if consteval branches. Untaken branches are now skipped. Fixes ( #54419 ) Fix assertion failure when declaring a template friend function with a constrained parameter in a template class that declares a class method or lambda at different depth. Fixes ( #75426 ) Fix an issue where clang cannot find conversion function with template parameter when instantiation of template class. Fixes ( #77583 ) Fix an issue where CTAD fails for function-type/array-type arguments. Fixes ( #51710 ) Fix crashes when using the binding decl from an invalid structured binding. Fixes ( #67495 ) and ( #72198 ) Fix assertion failure when call noreturn-attribute function with musttail attribute. Fixes ( #76631 ) - The MS __noop builtin without an argument list is now accepted in the placement-args of new-expressions, matching MSVC’s behaviour. Fix an issue that caused MS __decspec(property) accesses as well as Objective-C++ property accesses to not be converted to a function call to the getter in the placement-args of new-expressions. Fixes ( #65053 ) Fix an issue with missing symbol definitions when the first coroutine statement appears in a discarded if constexpr branch. Fixes ( #78290 ) Fixed assertion failure with deleted overloaded unary operators. Fixes ( #78314 ) The XCOFF object file format does not support aliases to symbols having common linkage. Clang now diagnoses the use of an alias for a common symbol when compiling for AIX. Clang now doesn’t produce false-positive warning -Wconstant-logical-operand for logical operators in C23. Fixes ( #64356 ). Clang’s -Wshadow no longer warns when an init-capture is named the same as a class field unless the lambda can capture this. Fixes ( #71976 ) Bug Fixes to Compiler Builtins ¶ Bug Fixes to Attribute Support ¶ Bug Fixes to C++ Support ¶ Clang limits the size of arrays it will try to evaluate at compile time to avoid memory exhaustion. This limit can be modified by -fconstexpr-steps . ( #63562 ) Fix a crash caused by some named unicode escape sequences designating a Unicode character whose name contains a - . (Fixes #64161 ) Fix cases where we ignore ambiguous name lookup when looking up members. ( #22413 ), ( #29942 ), ( #35574 ) and ( #27224 ). Clang emits an error on substitution failure within lambda body inside a requires-expression. This fixes: ( #64138 ) and ( #71684 ). Update FunctionDeclBitfields.NumFunctionDeclBits . This fixes: ( #64171 ). Expressions producing nullptr are correctly evaluated by the constant interpreter when appearing as the operand of a binary comparison. ( #64923 ) Fix a crash when an immediate invocation is not a constant expression and appear in an implicit cast. ( #64949 ). Fix crash when parsing ill-formed lambda trailing return type. Fixes: ( #64962 ) and ( #28679 ). Fix a crash caused by substitution failure in expression requirements. ( #64172 ) and ( #64723 ). Fix crash when parsing the requires clause of some generic lambdas. ( #64689 ) Fix crash when the trailing return type of a generic and dependent lambda refers to an init-capture. ( #65067 and #63675 ) Clang now properly handles out of line template specializations when there is a non-template inner-class between the function and the class template. ( #65810 ) Fix a crash when calling a non-constant immediate function in the initializer of a static data member. ( #65985 ). Clang now properly converts static lambda call operator to function pointers on win32. ( #62594 ) Fixed some cases where the source location for an instantiated specialization of a function template or a member function of a class template was assigned the location of a non-defining declaration rather than the location of the definition the specialization was instantiated from. ( #26057 ) Fix a crash when a default member initializer of a base aggregate makes an invalid call to an immediate function. ( #66324 ) Fix crash for a lambda attribute with a statement expression that contains a return . ( #48527 ) Clang now no longer asserts when an UnresolvedLookupExpr is used as an expression requirement. ( #66612 ) Clang now disambiguates NTTP types when printing diagnostics where the NTTP types are compared with the ‘diff’ method. ( #66744 ) Fix crash caused by a spaceship operator returning a comparision category by reference. Fixes: ( #64162 ) Fix a crash when calling a consteval function in an expression used as the size of an array. ( #65520 ) Clang no longer tries to capture non-odr-used variables that appear in the enclosing expression of a lambda expression with a noexcept specifier. ( #67492 ) Fix crash when fold expression was used in the initialization of default argument. Fixes: ( #67395 ) Fixed a bug causing destructors of constant-evaluated structured bindings initialized by array elements to be called in the wrong evaluation context. Fix crash where ill-formed code was being treated as a deduction guide and we now produce a diagnostic. Fixes: ( #65522 ) Fixed a bug where clang incorrectly considered implicitly generated deduction guides from a non-templated constructor and a templated constructor as ambiguous, rather than prefer the non-templated constructor as specified in [standard.group]p3. Fixed a crash caused by incorrect handling of dependence on variable templates with non-type template parameters of reference type. Fixes: ( #65153 ) Clang now properly compares constraints on an out of line class template declaration definition. Fixes: ( #61763 ) Fix a bug where implicit deduction guides are not correctly generated for nested template classes. Fixes: ( #46200 ) ( #57812 ) Diagnose use of a variable-length array in a coroutine. The design of coroutines is such that it is not possible to support VLA use. Fixes: ( #65858 ) Fix bug where we were overriding zero-initialization of class members when default initializing a base class in a constant expression context. Fixes: ( #69890 ) Fix crash when template class static member imported to other translation unit. Fixes: ( #68769 ) Clang now rejects incomplete types for __builtin_dump_struct . Fixes: ( #63506 ) Fixed a crash for C++98/03 while checking an ill-formed _Static_assert expression. Fixes: ( #72025 ) Clang now defers the instantiation of explicit specifier until constraint checking completes (except deduction guides). Fixes: ( #59827 ) Fix crash when parsing nested requirement. Fixes: ( #73112 ) Fixed a crash caused by using return type requirement in a lambda. Fixes: ( #63808 ) ( #64607 ) ( #64086 ) Fixed a crash where we lost uninstantiated constraints on placeholder NTTP packs. Fixes: ( #63837 ) Fixed a regression where clang forgets how to substitute into constraints on template-template parameters. Fixes: ( #57410 ) and ( #76604 ) Fix a bug where clang would produce inconsistent values when std::source_location::current() was used in a function template. Fixes ( #78128 ) Clang now allows parenthesized initialization of arrays in operator new[] . Fixes: ( #68198 ) Fixes CTAD for aggregates on nested template classes. Fixes: ( #77599 ) Fix crash when importing the same module with an dynamic initializer twice in different visibility. Fixes ( #67893 ) Remove recorded #pragma once state for headers included in named modules. Fixes ( #77995 ) Set the __cpp_auto_cast feature test macro in C++23 mode. Fix crash for inconsistent deducing state of function return types in importing modules. Fixes ( #78830 ) Fixes ( #60085 ) Fixed a bug where variables referenced by requires-clauses inside nested generic lambdas were not properly injected into the constraint scope. ( #73418 ) Fix incorrect code generation caused by the object argument of static operator() and static operator[] calls not being evaluated. Fixes ( #67976 ) Fix crash when using an immediate-escalated function at global scope. ( #82258 ) Correctly immediate-escalate lambda conversion functions. ( #82258 ) Fix a crash when an unresolved overload set is encountered on the RHS of a .* operator. ( #53815 ) Fixed a regression in CTAD that a friend declaration that befriends itself may cause incorrect constraint substitution. ( #86769 ) Bug Fixes to AST Handling ¶ Fixed an import failure of recursive friend class template. Issue 64169 Remove unnecessary RecordLayout computation when importing UnaryOperator. The computed RecordLayout is incorrect if fields are not completely imported and should not be cached. Issue 64170 Fixed hasAnyBase not binding nodes in its submatcher. ( #65421 ) Fixed a bug where RecursiveASTVisitor fails to visit the initializer of a bitfield. Issue 64916 Fixed a bug where range-loop-analysis checks for trivial copyability, rather than trivial copy-constructibility Issue 47355 Fixed a bug where Template Instantiation failed to handle Lambda Expressions with certain types of Attributes. ( #76521 ) Miscellaneous Bug Fixes ¶ Miscellaneous Clang Crashes Fixed ¶ Fixed a crash when parsing top-level ObjC blocks that aren’t properly terminated. Clang should now also recover better when an @end is missing between blocks. Issue 64065 Fixed a crash when check array access on zero-length element. Issue 64564 Fixed a crash when an ObjC ivar has an invalid type. See ( #68001 ) Fixed a crash in C when redefined struct is another nested redefinition. Issue 41302 Fixed a crash when -ast-dump=json was used for code using class template deduction guides. Fixed a crash when a lambda marked as static referenced a captured variable in an expression. Issue 74608 Fixed a crash with modules and a constexpr destructor. Issue 68702 OpenACC Specific Changes ¶ OpenACC Implementation effort is beginning with semantic analysis and parsing of OpenACC pragmas. The -fopenacc flag was added to enable these new, albeit incomplete changes. The _OPENACC macro is currently defined to 1 , as support is too incomplete to update to a standards-required value. Added -fexperimental-openacc-macro-override , a command line option to permit overriding the _OPENACC macro to be any digit-only value specified by the user, which permits testing the compiler against existing OpenACC workloads in order to evaluate implementation progress. Target Specific Changes ¶ AMDGPU Support ¶ Use pass-by-reference (byref) in stead of pass-by-value (byval) for struct arguments in C ABI. Callee is responsible for allocating stack memory and copying the value of the struct if modified. Note that AMDGPU backend still supports byval for struct arguments. The default value for -mcode-object-version is now 5. See AMDHSA Code Object V5 Metadata for more details. X86 Support ¶ Added option -m[no-]evex512 to disable ZMM and 64-bit mask instructions for AVX512 features. Support ISA of USER_MSR . * Support intrinsic of _urdmsr . * Support intrinsic of _uwrmsr . Support ISA of AVX10.1 . -march=pantherlake and -march=clearwaterforest are now supported. Added ABI handling for __float128 to match with GCC. Emit warnings for options to enable knl/knm specific ISAs: AVX512PF, AVX512ER and PREFETCHWT1. From next version (LLVM 19), these ISAs’ intrinsic supports will be deprecated: * intrinsic series of _exp2a23_ * intrinsic series of _rsqrt28_ * intrinsic series of _rcp28_ * intrinsic series of _prefetch_i[3|6][2|4]gather_ * intrinsic series of _prefetch_i[3|6][2|4]scatter_ Arm and AArch64 Support ¶ C++ function name mangling has been changed to align with the specification ( https://github.com/ARM-software/abi-aa/blob/main/aapcs64/aapcs64.rst ). This affects C++ functions with SVE ACLE parameters. Clang will use the old manglings if -fclang-abi-compat=17 or lower is specified. New AArch64 asm constraints have been added for r8-r11(Uci) and r12-r15(Ucj). Support has been added for the following processors (-mcpu identifiers in parenthesis): For Arm: Cortex-M52 (cortex-m52). For AArch64: Cortex-A520 (cortex-a520). Cortex-A720 (cortex-a720). Cortex-X4 (cortex-x4). Alpha support has been added for SVE2.1 intrinsics. Support has been added for -fstack-clash-protection and -mstack-probe-size command line options. Function Multi Versioning has been extended to support Load-Acquire RCpc instructions v3 (rcpc3) as well as Memory Copy and Memory Set Acceleration instructions (mops) when targeting AArch64. The feature identifiers (in parenthesis) can be used with either of the target_version and target_clones attributes. Android Support ¶ Android target triples are usually suffixed with a version. Clang searches for target-specific runtime and standard libraries in directories named after the target (e.g. if you’re building with --target=aarch64-none-linux-android21 , Clang will look for lib/aarch64-none-linux-android21 under its resource directory to find runtime libraries). If an exact match isn’t found, Clang would previously fall back to a directory without any version (which would be lib/aarch64-none-linux-android in our example). Clang will now look for directories for lower versions and use the newest version it finds instead, e.g. if you have lib/aarch64-none-linux-android21 and lib/aarch64-none-linux-android29 , | 2026-01-13T09:30:34 |
https://docs.aws.amazon.com/de_de/AmazonCloudFront/latest/DeveloperGuide/lambda-edge-event-request-response.html | So arbeitet Lambda@Edge mit Anforderungen und Antworten - Amazon CloudFront So arbeitet Lambda@Edge mit Anforderungen und Antworten - Amazon CloudFront Dokumentation Amazon CloudFront Entwicklerhandbuch Die vorliegende Übersetzung wurde maschinell erstellt. Im Falle eines Konflikts oder eines Widerspruchs zwischen dieser übersetzten Fassung und der englischen Fassung (einschließlich infolge von Verzögerungen bei der Übersetzung) ist die englische Fassung maßgeblich. So arbeitet Lambda@Edge mit Anforderungen und Antworten Wenn Sie eine CloudFront Verteilung mit einer Lambda @Edge -Funktion verknüpfen, CloudFront fängt sie Anfragen und Antworten an CloudFront Edge-Standorten ab. Sie können Lambda-Funktionen ausführen, wenn die folgenden CloudFront Ereignisse eintreten: Wann CloudFront erhält er eine Anfrage von einem Zuschauer (Viewer-Anfrage) Bevor CloudFront eine Anfrage an den Ursprung weitergeleitet wird (ursprüngliche Anfrage) Wann CloudFront erhält er eine Antwort vom Ursprung (ursprüngliche Antwort) Before CloudFront gibt die Antwort an den Zuschauer zurück (Antwort des Betrachters) Wenn Sie verwenden AWS WAF, wird die Lambda @Edge Viewer-Anfrage ausgeführt, nachdem alle AWS WAF Regeln angewendet wurden. Weitere Informationen erhalten Sie unter Arbeiten mit Anforderungen und Antworten und Lambda@Edge-Ereignisstruktur . JavaScript ist in Ihrem Browser nicht verfügbar oder deaktiviert. Zur Nutzung der AWS-Dokumentation muss JavaScript aktiviert sein. Weitere Informationen finden auf den Hilfe-Seiten Ihres Browsers. Dokumentkonventionen Anpassen mit Lambda@Edge Anwendungsmöglichkeiten von Lambda@Edge Hat Ihnen diese Seite geholfen? – Ja Vielen Dank, dass Sie uns mitgeteilt haben, dass wir gute Arbeit geleistet haben! Würden Sie sich einen Moment Zeit nehmen, um uns mitzuteilen, was wir richtig gemacht haben, damit wir noch besser werden? Hat Ihnen diese Seite geholfen? – Nein Vielen Dank, dass Sie uns mitgeteilt haben, dass diese Seite überarbeitet werden muss. Es tut uns Leid, dass wir Ihnen nicht weiterhelfen konnten. Würden Sie sich einen Moment Zeit nehmen, um uns mitzuteilen, wie wir die Dokumentation verbessern können? | 2026-01-13T09:30:34 |
https://logging.apache.org/log4j/2.x/migrate-from-slf4j.html | Migrating from SLF4J :: Apache Log4j a subproject of Apache Logging Services Home Download Release notes Support Versioning and maintenance policy Security Manual Getting started Installation API Loggers Event Logger Simple Logger Status Logger Fluent API Fish tagging Levels Markers Thread Context Messages Flow Tracing Implementation Architecture Configuration Configuration file Configuration properties Programmatic configuration Appenders File appenders Rolling file appenders Database appenders Network Appenders Message queue appenders Delegating Appenders Layouts JSON Template Layout Pattern Layout Lookups Filters Scripts JMX Extending Plugins Performance Asynchronous loggers Garbage-free logging References Plugin reference Java API reference Resources F.A.Q. Migrating from Log4j 1 Migrating from Logback Migrating from SLF4J Building GraalVM native images Integrating with Hibernate Integrating with Jakarta EE Integrating with service-oriented architectures Development Components Log4j IOStreams Log4j Spring Boot Support Log4j Spring Cloud Configuration JUL-to-Log4j bridge Log4j-to-JUL bridge Related projects Log4j Jakarta EE Log4j JMX GUI Log4j Kotlin Log4j Scala Log4j Tools Log4j Transformation Tools Home Resources Migrating from SLF4J Edit this Page Migrating from SLF4J SLF4J is a logging API whose reference implementation is Logback , just like Log4j API is a logging API whose reference implementation is Log4j Core. In this page we will guide you through migrating from SLF4J to Log4j API as your logging API. Instead of migrating your logging API, SLF4J, are you looking for migrating your logging implementation, Logback? Please refer to Migrating from Logback . Struggling with the logging API, implementation, and bridge concepts? Click for an introduction. Logging API A logging API is an interface your code or your dependencies directly logs against. It is required at compile-time. It is implementation agnostic to ensure that your application can write logs, but is not tied to a specific logging implementation. Log4j API, SLF4J , JUL (Java Logging) , JCL (Apache Commons Logging) , JPL (Java Platform Logging) and JBoss Logging are major logging APIs. Logging implementation A logging implementation is only required at runtime and can be changed without the need to recompile your software. Log4j Core, JUL (Java Logging) , Logback are the most well-known logging implementations. Logging bridge Logging implementations accept input from a single logging API of their preference; Log4j Core from Log4j API, Logback from SLF4J, etc. A logging bridge is a simple logging implementation of a logging API that forwards all messages to a foreign logging API. Logging bridges allow a logging implementation to accept input from other logging APIs that are not their primary logging API. For instance, log4j-slf4j2-impl bridges SLF4J calls to Log4 API and effectively enables Log4j Core to accept input from SLF4J. To make things a little bit more tangible, consider the following visualization of a typical Log4j Core installation with bridges for an application: Figure 1. Visualization of a typical Log4j Core installation with SLF4J, JUL, and JPL bridges Migrating If your application or library logs using SLF4J, you can migrate it to Log4j API as follows: Remove org.slf4j:slf4j-api dependency Follow the instructions shared in the "Getting started" page for installing log4j-api and using it Search for org.slf4j usages in your project and replace them with Log4j API equivalents For an exhaustive list of code changes that need to be carried out, refer to the SLF4J to Log4j API migration OpenRewrite recipe . This you can use to either manually follow the described migrations, or run OpenRewrite to automatically migrate the code. org.slf4j.LoggerFactory Replace its usages with org.apache.logging.log4j.LogManager . Note that LogManager.getLogger(Foo.class) can be simplified as LogManager.getLogger() , if Foo is the enclosing class of the field. org.slf4j.Logger Replace its usages with org.apache.logging.log4j.Logger . Since SLF4J’s Logger is almost a parent of Log4j’s Logger , most methods should work without any changes. org.slf4j.MDC Replace its usages with org.apache.logging.log4j.ThreadContext . If you use @Slf4j from Lombok , you need to replace them with @Log4j2 instead. At this stage, you should have your application or library logging using Log4j API. If it is a library that you migrated, then you don’t need to take any extra steps. Unlike applications, libraries should be logging implementation agnostic. That is, libraries should log through a logging API, but leave the decision of the logging implementation to the application. If it is an application that you migrated, and you are not using Log4j Core as your logging implementation, then you can consider doing so. Certain Log4j API features (e.g., garbage-free logging ) require an end-to-end setup which is mostly possible using Log4j API in combination with Log4j Core. See Installation for installing Log4j Core. If you are using Logback, refer to Migrating from Logback . Copyright © 1999-2025 The Apache Software Foundation . Licensed under the Apache Software License, Version 2.0 . Please read our privacy policy . Apache, Log4j, and the Apache feather logo are trademarks or registered trademarks of The Apache Software Foundation. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. | 2026-01-13T09:30:34 |
https://logging.apache.org/log4j/2.x/manual/flowtracing.html | Flow Tracing :: Apache Log4j a subproject of Apache Logging Services Home Download Release notes Support Versioning and maintenance policy Security Manual Getting started Installation API Loggers Event Logger Simple Logger Status Logger Fluent API Fish tagging Levels Markers Thread Context Messages Flow Tracing Implementation Architecture Configuration Configuration file Configuration properties Programmatic configuration Appenders File appenders Rolling file appenders Database appenders Network Appenders Message queue appenders Delegating Appenders Layouts JSON Template Layout Pattern Layout Lookups Filters Scripts JMX Extending Plugins Performance Asynchronous loggers Garbage-free logging References Plugin reference Java API reference Resources F.A.Q. Migrating from Log4j 1 Migrating from Logback Migrating from SLF4J Building GraalVM native images Integrating with Hibernate Integrating with Jakarta EE Integrating with service-oriented architectures Development Components Log4j IOStreams Log4j Spring Boot Support Log4j Spring Cloud Configuration JUL-to-Log4j bridge Log4j-to-JUL bridge Related projects Log4j Jakarta EE Log4j JMX GUI Log4j Kotlin Log4j Scala Log4j Tools Log4j Transformation Tools Home Manual API Flow Tracing Edit this Page Flow Tracing Log4j API provides convenience logging methods to aid the tracking of the data flow through an application, which is referred to as flow tracing . Logging implementations can choose to generate specialized log events allowing users to handle these messages different from the rest – see Example configuration . Flow tracing is known to help with the following use cases: Troubleshooting without requiring a debugging session Helping educate new developers in learning the application Usage Logger provides following methods for flow tracing purposes: traceEntry() Marks the entry to a block traceExit() Marks the exit from a block catching() Reports caught exceptions throwing() Reports exceptions that are either discarded or unlikely to be handled The most used traceEntry() and traceExit() methods are intended to mark the entry and exit points of a particular block of code: Example traceEntry() and traceExit() usage public void someMethod() { LOGGER.traceEntry(); (1) // method body LOGGER.traceExit(); (2) } 1 traceEntry() marks the entry to the block 2 traceExit() marks the exit from the block Both traceEntry() and traceExit() also accept parameters. You can use them to track the input and output of the associated block: Example traceEntry() and traceExit() usage with arguments public String someMethod(String input) { logger.traceEntry(null, input); (1) // method body String output = ...; return logger.traceExit(output); (2) } 1 traceEntry() marks the entry to the block along with the input 2 traceExit() marks the exit from the block along with the output The catching() method can be used by an application when it catches an exception that it will not rethrow, either explicitly or attached to another exception: Example catching() usage public void someMethod() { try { // Business logic } catch (Exception error) { logger.catching(error); (1) } } 1 catching() reports the caught exception The throwing() method can be used by an application when it is throwing an exception that is unlikely to be handled, such as a RuntimeException . This will ensure that proper diagnostics are available if needed. Example throwing() usage public void someMethod() { try { // Business logic } catch (RuntimeException error) { throw logger.throwing(error); (1) } } 1 thrown() reports the caught exception that is about to be rethrown. Plus, rethrowing the exception, contrary to the catching() example suppressing the exception. public void someMethod() { try { // Let's assume an exception is thrown here String msg = messages[messages.length]; } catch (Exception ex) { logger.throwing(ex); (1) } } 1 The throwing() method logs exceptions that are thrown and not caught. Aspect-oriented programming Logging has been a notorious example for demonstrating aspect-oriented programming (AOP). For instance, using AOP, you can inject logging statements to methods that match a particular footprint, e.g., all public methods in com.mycompany package. With a couple of lines of AOP instructions, you can log input and output of all matching functions. Flow tracing methods fits like a glove to this AOP use case. You can see a demonstration of this in the log4j-samples-aspectj project demonstrating how you can implement this use case using Log4j API flow methods and Spring Boot AspectJ support. Implementation This section explains how flow tracing is implemented by different logging implementations. Log4j Core Log4j Core, the reference implementation of Log4j API, implements the flow tracing methods such that It generates specialized log events Its behaviour is configurable Log events Log4j Core implements the flow tracing methods such that the generated log events are decorated to accommodate any need to selectively handle them: Method Level Markers Message traceEntry() TRACE ENTER , FLOW EntryMessage extending from FlowMessage traceExit() TRACE EXIT , FLOW ExitMessage extending from FlowMessage throwing() ERROR THROWING , EXCEPTION Plain message catching() ERROR CATCHING , EXCEPTION Plain message Configuration Flow tracing implementation of Log4j Core can be configured using the following system properties: log4j2.flowMessageFactory Env. variable LOG4J_FLOW_MESSAGE_FACTORY Type Class<? extends FlowMessageFactory> Default value DefaultFlowMessageFactory Fully qualified class name of a FlowMessageFactory implementation to be used by all loggers. Logback Logback is another logging implementation for the SLF4J logging API, just like Log4j Core is a logging implementation for the Log4j API . Using Log4j-to-SLF4J bridge, Logback can be configured to consume Log4j API . Log4j-to-SLF4J bridge implements flow tracing methods such that log events are generated with same marker and level changes of Log4j Core . They only differ in generated message types, since SLF4J has no extensible message contract like Log4j, but plain String -based messages. This effectively means Logback also has access to the stated marker and level changes while using Log4j API flow tracing methods. Example configuration In this section, we will share logging implementation configuration examples to filter on flow tracing log events. Log4j Core Log4j Core is the reference implementation of Log4j API. In the example configurations below, we will employ a Pattern Layout depending on the associated markers of the log event: XML JSON YAML Properties log4j2.xml snippet <MarkerFilter marker="FLOW" onMatch="ACCEPT" onMismatch="NEUTRAL"/> (1) <Appenders> <Console name="CONSOLE"> <PatternLayout> <MarkerPatternSelector defaultPattern="%d %5p [%t] %c{1} -- %m%n"> (2) <PatternMatch key="ENTER" pattern="%d %5p [%t] %c{1} => %m%n"/> (3) <PatternMatch key="EXIT" pattern="%d %5p [%t] %c{1} <= %m%n"/> (4) </MarkerPatternSelector> </PatternLayout> </Console> </Appenders> log4j2.json snippet "MarkerFilter": { (1) "marker": "FLOW", "onMatch": "ACCEPT", "onMismatch": "NEUTRAL" }, "Appenders": { "Console": { "name": "CONSOLE", "PatternLayout": { "MarkerPatternSelector": { "defaultPattern": "%d %5p [%t] %c{1} -- %m%n", (2) "PatternMatch": [ { (3) "key": "ENTER", "pattern": "%d %5p [%t] %c{1} => %m%n" }, { (4) "key": "EXIT", "pattern": "%d %5p [%t] %c{1} <= %m%n" } ] } } } }, log4j2.yaml snippet MarkerFilter: (1) marker: "FLOW" onMatch: "ACCEPT" onMismatch: "NEUTRAL" Appenders: Console: name: "CONSOLE" PatternLayout: MarkerPatternSelector: defaultPattern: "%d %5p [%t] %c{1} -- %m%n" (2) PatternMatch: - key: "ENTER" (3) pattern: "%d %5p [%t] %c{1} => %m%n" - key: "EXIT" (4) pattern: "%d %5p [%t] %c{1} <= %m%n" log4j2.properties snippet filter.0.type = MarkerFilter (1) filter.0.marker = FLOW filter.0.onMatch = ACCEPT filter.0.onMismatch = NEUTRAL appender.0.type = Console appender.0.name = CONSOLE appender.0.layout.type = PatternLayout appender.0.layout.patternSelector.type = MarkerPatternSelector appender.0.layout.patternSelector.defaultPattern = "%d %5p [%t] %c{1} -- %m%n (2) appender.0.layout.patternSelector.properties.0.type = PatternMatch appender.0.layout.patternSelector.properties.0.key = ENTER appender.0.layout.patternSelector.properties.0.pattern = %d %5p [%t] %c{1} => %m%n (3) appender.0.layout.patternSelector.properties.1.type = PatternMatch appender.0.layout.patternSelector.properties.1.key = EXIT appender.0.layout.patternSelector.properties.1.pattern = %d %5p [%t] %c{1} <= %m%n (4) 1 Accepting log events marked with FLOW regardless of their level 2 By default, log event messages will be formatted with a -- prefix 3 Log events marked with ENTER (that is, generated by traceEntry() ) will have their message formatted with a ⇒ prefix 4 Log events marked with EXIT (that is, generated by traceExit() ) will have their message formatted with a ⇐ prefix Logback Logback is another logging implementation for the SLF4J logging API, just like Log4j Core is a logging implementation for the Log4j API . Using Log4j-to-SLF4J bridge, Logback can be configured to consume Log4j API . Below we will use a combination of EvaluatorFilter , MarkerFilter , and OnMarkerEvaluator in Logback to adapt the formatting pattern of messages written to console based on flow tracing specific markers: logback.xml snippet <turboFilter class="MarkerFilter"> (1) <Marker>FLOW</Marker> <OnMatch>ACCEPT</OnMatch> </turboFilter> <appender name="CONSOLE_DEFAULT" class="ConsoleAppender"> <filter class="EvaluatorFilter"> (2) <evaluator class="OnMarkerEvaluator"> <marker>ENTER</marker> <marker>EXIT</marker> </evaluator> <onMismatch>ACCEPT</onMismatch> <onMatch>DENY</onMatch> </filter> <encoder class="PatternLayoutEncoder"> (3) <pattern><![CDATA[%d %5p [%t] %c{1} -- %m%n]]></pattern> </encoder> </appender> <appender name="CONSOLE_FLOW_ENTER" class="ConsoleAppender"> <filter class="EvaluatorFilter"> (4) <evaluator class="OnMarkerEvaluator"> <marker>ENTER</marker> </evaluator> <onMismatch>DENY</onMismatch> <onMatch>ACCEPT</onMatch> </filter> <encoder class="PatternLayoutEncoder"> (5) <pattern><![CDATA[%d %5p [%t] %c{1} => %m%n]]></pattern> </encoder> </appender> <appender name="CONSOLE_FLOW_EXIT" class="ConsoleAppender"> <filter class="EvaluatorFilter"> (6) <evaluator class="OnMarkerEvaluator"> <marker>EXIT</marker> </evaluator> <onMismatch>DENY</onMismatch> <onMatch>ACCEPT</onMatch> </filter> <encoder class="PatternLayoutEncoder"> (7) <pattern><![CDATA[%d %5p [%t] %c{1} <= %m%n]]></pattern> </encoder> </appender> <root level="WARN"> <appender-ref ref="CONSOLE_DEFAULT"/> <appender-ref ref="CONSOLE_FLOW_ENTER"/> <appender-ref ref="CONSOLE_FLOW_EXIT"/> </root> 1 Accepting log events marked with FLOW regardless of their level 2 In CONSOLE_DEFAULT appender, excluding all log events marked with ENTER and EXIT 3 In CONSOLE_DEFAULT appender, log event messages will be formatted with a - prefix 4 In CONSOLE_FLOW_ENTER appender, accepting only log events marked with ENTER 5 In CONSOLE_FLOW_ENTER appender, log event messages will be formatted with a → prefix 6 In CONSOLE_FLOW_EXIT appender, accepting only log events marked with EXIT 7 In CONSOLE_FLOW_EXIT appender, log event messages will be formatted with a ← prefix Copyright © 1999-2025 The Apache Software Foundation . Licensed under the Apache Software License, Version 2.0 . Please read our privacy policy . Apache, Log4j, and the Apache feather logo are trademarks or registered trademarks of The Apache Software Foundation. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. | 2026-01-13T09:30:34 |
https://penneo.com/da/real-estate/ | Ejendomsbranchen - Penneo Produkter Penneo Sign Validator Hvorfor Penneo Integrationer Løsninger Anvendelsesscenarier Digital signering Dokumenthåndtering Udfyld og underskriv PDF-formularer Automatisering af underskriftsprocesser Overholdelse af eIDAS Brancher Revision og regnskab Finans og bank Advokatydelser Ejendom Administration og HR Priser Ressourcer Vidensunivers Trust Center Produktopdateringer SIGN Hjælpecenter KYC Hjælpecenter Systemstatus LOG PÅ Penneo Sign Log ind på Penneo Sign. LOG PÅ Penneo KYC Log ind på Penneo KYC. LOG PÅ BOOK ET MØDE GRATIS PRØVEPERIODE DA EN NO FR NL Produkter Penneo Sign Validator Hvorfor Penneo Integrationer Løsninger Revision og regnskab Finans og bank Advokatydelser Ejendom Administration og HR Anvendelsesscenarier Digital signering Dokumenthåndtering Udfyld og underskriv PDF-formularer Automatisering af underskriftsprocesser Overholdelse af eIDAS Priser Ressourcer Vidensunivers Trust Center Produktopdateringer SIGN Hjælpecenter KYC Hjælpecenter Systemstatus BOOK ET MØDE GRATIS PRØVEPERIODE LOG PÅ DA EN NO FR NL Penneo Sign Log ind på Penneo Sign. LOG PÅ Penneo KYC Log ind på Penneo KYC. LOG PÅ Mindre papirarbejde, mere tid til fremragende kundeservice Penneo hjælper ejendomsmæglere og ejendomsadministrationsselskaber med at optimere dokumentunderskrift , så de kan fokusere på at levere en bedre oplevelse for lejere, købere og sælgere. UDFORSK PENNEO Forældede processer kan føre til ineffektivitet og mindre tid til kunderne Forældede dokumentunderskriftsprocesser skaber betydelig ineffektivitet. Manuelt arbejde, langsomme godkendelsesforløb og gentagne administrative opgaver mindsker produktiviteten og stjæler tid fra værdifulde kunderelationer. Ud over driftsmæssig ineffektivitet kan forældede processer også påvirke kundeoplevelsen negativt. Lejere, købere og sælgere forventer hurtige og problemfri transaktioner – men langsom dokumenthåndtering kan føre til frustration. Se, hvordan Penneo kan hjælpe dig Øg produktiviteten ved at integrere Penneo med dine værktøjer Ved at integrere Penneo med dine eksisterende værktøjer kan du eliminere besværet ved at skifte mellem platforme og spare værdifuld tid. Penneo tilbyder forudbyggede integrationer med ejendoms- og ejendomsadministrationssoftware som Unik Bolig, WebBolig, EG Bolig og EG Strato . Derudover kan du oprette integrationer, der er skræddersyet til dine behov, ved hjælp af Penneos åbne API. Se alle vores integrationer Automatiser dokumentunderskrivningen og forbedr medarbejderoplevelsen Penneo minimerer arbejdsbyrden i forbindelse med dokumentunderskrift bidrager til en bedre kundeoplevelse ved at: Automatisere underskrift af lejekontrakter, købsaftaler og andre nødvendige dokumenter. Give sikre og juridisk bindende digitale signaturer med eID’er eller pas. Giver medarbejdere og kunder mulighed for at underskrive dokumenter hvor som helst og på hvilken som helst enhed. Se alle funktioner Eliminer manuelt arbejde og luk aftaler hurtigere Med integrationer til nøgleværktøjer og automatiserede signeringsflows kan du minimere administrative flaskehalse, forbedre nøjagtigheden og forbedre kundeoplevelsen – så du kan afslutte aftaler hurtigt og effektivt. Penneo overholder GDPR, har ISO 27001- og 27701-certificeringer og bruger kryptering til at beskytte dine data og dokumenter på alle trin. Med Penneo kan du oprette kvalificerede elektroniske signaturer (QES) ved hjælp af pas, norsk BankID, itsme® eller .beID, samt avancerede elektroniske signaturer (AdES) med MitID, MitID Erhverv eller svensk BankID. Få fuldt overblik over hele underskriftsprocessen med detaljerede aktivitetslogs – og giv dit team de bedste forudsætninger for at minimere fejl og arbejde effektivt . Gør det nemt for dine kunder at underskrive dokumenter digitalt – når som helst og hvor som helst. Modernisering af jeres processer fremmer innovation, øger produktiviteten og gør jeres organisation til en attraktiv og fremsynet arbejdsplads. Se, hvordan Penneo fungerer Over 3000 companies trust Penneo Se hvordan Penneo kan hjælpe dig BOOK ET UFORPLIGTENDE MØDE Produkter Penneo Sign Priser Integrationer Åben API Validator Hvorfor Penneo Løsninger Revision og regnskab Finans og bank Advokatydelser Ejendom Administration og HR Anvendelsesscenarier Digital signering Dokumenthåndtering Udfyld og underskriv PDF-formularer Automatisering af underskriftsprocesser Overholdelse af eIDAS Ressourcer Vidensunivers Trust Center Produktopdateringer SUPPORT SIGN Hjælpecenter KYC Hjælpecenter Systemstatus Virksomhed Om os Karriere Privatlivspolitik Vilkår Brug af cookies Accessibility Statement Whistleblower Policy Kontakt os PENNEO A/S - Gærtorvet 1-5, DK-1799 København V - CVR: 35633766 | 2026-01-13T09:30:34 |
https://logging.apache.org/log4j/2.x/graalvm.html | Building GraalVM native images :: Apache Log4j a subproject of Apache Logging Services Home Download Release notes Support Versioning and maintenance policy Security Manual Getting started Installation API Loggers Event Logger Simple Logger Status Logger Fluent API Fish tagging Levels Markers Thread Context Messages Flow Tracing Implementation Architecture Configuration Configuration file Configuration properties Programmatic configuration Appenders File appenders Rolling file appenders Database appenders Network Appenders Message queue appenders Delegating Appenders Layouts JSON Template Layout Pattern Layout Lookups Filters Scripts JMX Extending Plugins Performance Asynchronous loggers Garbage-free logging References Plugin reference Java API reference Resources F.A.Q. Migrating from Log4j 1 Migrating from Logback Migrating from SLF4J Building GraalVM native images Integrating with Hibernate Integrating with Jakarta EE Integrating with service-oriented architectures Development Components Log4j IOStreams Log4j Spring Boot Support Log4j Spring Cloud Configuration JUL-to-Log4j bridge Log4j-to-JUL bridge Related projects Log4j Jakarta EE Log4j JMX GUI Log4j Kotlin Log4j Scala Log4j Tools Log4j Transformation Tools Home Resources Building GraalVM native images Edit this Page Building GraalVM native images Since version 2.25.0 both Log4j API and its reference implementation provide out-of-the-box support for creating native executables using GraalVM . This document complements the Installation Guide and provides additional details on the steps necessary to create native images that use the Log4j API. The information is split depending on which Log4j API implementation you are using. Struggling with the logging API, implementation, and bridge concepts? Click for an introduction. Logging API A logging API is an interface your code or your dependencies directly logs against. It is required at compile-time. It is implementation agnostic to ensure that your application can write logs, but is not tied to a specific logging implementation. Log4j API, SLF4J , JUL (Java Logging) , JCL (Apache Commons Logging) , JPL (Java Platform Logging) and JBoss Logging are major logging APIs. Logging implementation A logging implementation is only required at runtime and can be changed without the need to recompile your software. Log4j Core, JUL (Java Logging) , Logback are the most well-known logging implementations. Logging bridge Logging implementations accept input from a single logging API of their preference; Log4j Core from Log4j API, Logback from SLF4J, etc. A logging bridge is a simple logging implementation of a logging API that forwards all messages to a foreign logging API. Logging bridges allow a logging implementation to accept input from other logging APIs that are not their primary logging API. For instance, log4j-slf4j2-impl bridges SLF4J calls to Log4 API and effectively enables Log4j Core to accept input from SLF4J. To make things a little bit more tangible, consider the following visualization of a typical Log4j Core installation with bridges for an application: Figure 1. Visualization of a typical Log4j Core installation with SLF4J, JUL, and JPL bridges Are you looking for an example of GraalVM application that uses the Log4j API? Check out the log4j-samples-graalvm project. Using Simple Logger If you use Simple Logger shipped with Log4j API in your application, no additional steps are required to compile a GraalVM native image. Using Log4j Core Since version 2.25.0 , Log4j Core and all its official extensions are bundled with the necessary GraalVM reachability metadata to help GraalVM with the creation of native images. Additional steps are only required: If you use a configuration file, which is not in a standard location , you need to create a META-INF/native-image/<groupId>/<artifactId>/resource-config.json file in your classpath with content: { "resources": { "includes": [ { "pattern": "path/to/your/configuration/file" } ] } } If you use third-party Log4j Plugin JARs you need to make sure they contain a reflect-config.json metadata file. If that is not the case, please point the maintainer to the Log4j Plugin registration documentation . Using JUL Since version 2.24.0 the Log4j API to JUL bridge is tested for compatibility with GraalVM. Although java.util.logging is embedded into the JRE, currently not all j.u.l.Formatter and j.u.l.Handler implementations have the required GraalVM metadata. See the official Add Logging to a Native Executable guide for more information on how to add additional elements to your configuration. See reflect-config.json in our log4j-samples-graalvm example project for an example on how to enable j.u.l.FileHandler . Using Logback Since version 2.24.0 the Log4j API to SLF4J bridge is tested for compatibility with GraalVM. While Logback itself does not provide any GraalVM metadata, the data is available in the third-party GraalVM reachability metadata repository . See the GraalVM Reachability Metadata Support documentation appropriate for your build tool for more information: Gradle Plugin documentation Maven Plugin documentation Copyright © 1999-2025 The Apache Software Foundation . Licensed under the Apache Software License, Version 2.0 . Please read our privacy policy . Apache, Log4j, and the Apache feather logo are trademarks or registered trademarks of The Apache Software Foundation. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. | 2026-01-13T09:30:34 |
https://www.iso.org/es/sectores/medioambiente | ISO - Sostenibilidad ambiental Ir directamente al contenido principal Aplicaciones OBP español English français русский Menú Normas Sectores Salud Tecnologías de la información y afines Gestión y servicios Seguridad, protección y gestión de riesgos Transporte Energía Diversidad e inclusión Sostenibilidad ambiental Alimentos y agricultura Materiales Edificación y construcción Ingeniería Sobre nosotros Perspectivas y actualidad Perspectivas Todos los artículos Salud Inteligencia artificial Cambio climático Transporte Ciberseguridad Gestión de la calidad Energías renovables Seguridad y salud en el trabajo Actualidad Opinión de expertos El mundo de las normas Kit de prensa Resources ISO 22000 explained ISO 9001 explained ISO 14001 explained Participar Tienda Buscar Carrito Sostenibilidad ambiental Gestión ambiental Economía circular Cambio climático Calidad del aire Ciudades inteligentes Calidad del suelo Calidad del agua Otros Las Normas Internacionales sobre sostenibilidad ambiental ofrecen una forma clara y práctica de alcanzar la excelencia operacional, cumplir los requisitos legales y satisfacer las expectativas de las partes interesadas. Al adoptar estas normas ISO, las organizaciones pueden posicionarse como líderes, ahorrar dinero y recursos, y ganarse la confianza y el reconocimiento. Normas esenciales ISO 50001 Sistemas de gestión de la energía — Requisitos con orientación para su uso Revisado en 2024 CHF 179 ISO 14001 Sistemas de gestión ambiental — Requisitos con orientación para su uso Publicado en 2015 CHF 179 ISO 17298 Biodiversity — Considering biodiversity in the strategy and operations of organizations — Requirements and guidelines Publicado en 2025 CHF 135 ISO 14044 Environmental management — Life cycle assessment — Requirements and guidelines Revisado en 2022 CHF 196 ISO 14040 Environmental management — Life cycle assessment — Principles and framework Revisado en 2022 CHF 155 ISO 14064-1 Greenhouse gases Part 1: Specification with guidance at the organization level for quantification and reporting of greenhouse gas emissions and removals Publicado en 2018 CHF 196 ISO 14067 Greenhouse gases — Carbon footprint of products — Requirements and guidelines for quantification Publicado en 2018 CHF 196 Cargar más Perspectivas Opinion La biodiversidad es responsabilidad de todos La pérdida de biodiversidad puede parecer con frecuencia lejana: una especie de ranas que desaparece en lo más recóndito de la selva o un arrecife de coral que se blanquea bajo el calentamiento de los mares. Pero no nos confundamos, esta crisis está aquí y ahora. Energía renovable: impulsar la transición hacia un mundo sostenible A medida que el mundo hace la transición hacia un futuro con bajas emisiones de carbono, la tecnología se pone a la cabeza y ofrece soluciones ampliables a escala para un planeta más ecológico. Construir un camino sostenible hacia los informes ESG El impulso hacia un futuro más sostenible ha propulsado las consideraciones ESG, o ambientales, sociales y de gobernanza, en su forma completa, a la primera línea de las reuniones de los consejos de administración de las empresas de todo el mundo. Sectores Sostenibilidad ambiental Mapa del sitio Normas Beneficios Normas más comunes Evaluación de la conformidad ODS Sectores Salud Tecnologías de la información y afines Gestión y servicios Seguridad, protección y gestión de riesgos Transporte Energía Sostenibilidad ambiental Materiales Sobre nosotros Qué es lo que hacemos Estructura Miembros Events Estrategia Perspectivas y actualidad Perspectivas Todos los artículos Salud Inteligencia artificial Cambio climático Transporte Actualidad Opinión de expertos El mundo de las normas Kit de prensa Resources ISO 22000 explained ISO 9001 explained ISO 14001 explained Participar Who develops standards Deliverables Get involved Colaboración para acelerar una acción climática eficaz Resources Drafting standards Tienda Tienda Publications and products ISO name and logo Privacy Notice Copyright Cookie policy Media kit Jobs Help and support Seguimos haciendo que la vida sea mejor , más fácil y más segura . Inscríbase para recibir actualizaciones por correo electrónico © Reservados todos los derechos Todos los materiales y publicaciones de ISO están protegidos por derechos de autor y sujetos a la aceptación por parte del usuario de las condiciones de derechos de autor de ISO. Cualquier uso, incluida la reproducción, requiere nuestra autorización por escrito. Dirija todas las solicitudes relacionadas con los derechos de autor a copyright@iso.org . Nos comprometemos a garantizar que nuestro sitio web sea accesible para todo el mundo. Si tiene alguna pregunta o sugerencia relacionada con la accesibilidad de este sitio web, póngase en contacto con nosotros. Añadir al carrito | 2026-01-13T09:30:34 |
http://docs.buildbot.net/current/manual/cmdline.html#cmdline-restart%20(worker) | 2.7. Command-line Tool — Buildbot 4.3.0 documentation Buildbot 1. Buildbot Tutorial 2. Buildbot Manual 2.1. Introduction 2.2. Installation 2.3. Concepts 2.4. Secret Management 2.5. Configuration 2.6. Customization 2.7. Command-line Tool 2.7.1. buildbot 2.7.1.1. Administrator Tools 2.7.1.2. Developer Tools 2.7.1.3. Other Tools 2.7.1.4. .buildbot config directory 2.7.2. buildbot-worker 2.7.2.1. create-worker 2.7.2.2. start 2.7.2.3. restart 2.7.2.4. stop 2.8. Resources 2.9. Optimization 2.10. Plugin Infrastructure in Buildbot 2.11. Deployment 2.12. Upgrading 3. Buildbot Development 4. Release Notes 5. Older Release Notes 6. API Indices Buildbot 2. Buildbot Manual 2.7. Command-line Tool View page source 2.7. Command-line Tool This section describes command-line tools available after buildbot installation. The two main command-line tools are buildbot and buildbot-worker . The former handles a Buildbot master and the former handles a Buildbot worker. Every command-line tool has a list of global options and a set of commands which have their own options. One can run these tools in the following way: buildbot [global options] command [command options] buildbot-worker [global options] command [command options] The buildbot command is used on the master, while buildbot-worker is used on the worker. Global options are the same for both tools which perform the following actions: --help Print general help about available commands and global options and exit. All subsequent arguments are ignored. --verbose Set verbose output. --version Print current buildbot version and exit. All subsequent arguments are ignored. You can get help on any command by specifying --help as a command option: buildbot command --help You can also use manual pages for buildbot and buildbot-worker for quick reference on command-line options. The remainder of this section describes each buildbot command. See Command Line Index for a full list. 2.7.1. buildbot The buildbot command-line tool can be used to start or stop a buildmaster or buildbot, and to interact with a running buildmaster. Some of its subcommands are intended for buildmaster admins, while some are for developers who are editing the code that the buildbot is monitoring. 2.7.1.1. Administrator Tools The following buildbot sub-commands are intended for buildmaster administrators: create-master buildbot create-master -r {BASEDIR} This creates a new directory and populates it with files that allow it to be used as a buildmaster’s base directory. You will usually want to use the option -r option to create a relocatable buildbot.tac . This allows you to move the master directory without editing this file. upgrade-master buildbot upgrade-master {BASEDIR} This upgrades a previously created buildmaster’s base directory for a new version of buildbot master source code. This will copy the web server static files, and potentially upgrade the db. start buildbot start [--nodaemon] {BASEDIR} This starts a buildmaster which was already created in the given base directory. The daemon is launched in the background, with events logged to a file named twistd.log . The option –nodaemon option instructs Buildbot to skip daemonizing. The process will start in the foreground. It will only return to the command-line when it is stopped. Additionally, the user can set the environment variable START_TIMEOUT to specify the amount of time the script waits for the master to start until it declares the operation as failure. restart buildbot restart [--nodaemon] {BASEDIR} Restart the buildmaster. This is equivalent to stop followed by start The option –nodaemon option has the same meaning as for start . stop buildbot stop {BASEDIR} This terminates the daemon (either buildmaster or worker) running in the given directory. The --clean option shuts down the buildmaster cleanly. With --no-wait option buildbot stop command will send buildmaster shutdown signal and will immediately exit, not waiting for complete buildmaster shutdown. sighup buildbot sighup {BASEDIR} This sends a SIGHUP to the buildmaster running in the given directory, which causes it to re-read its master.cfg file. checkconfig buildbot checkconfig {BASEDIR|CONFIG_FILE} This checks if the buildmaster configuration is well-formed and contains no deprecated or invalid elements. If no arguments are used or the base directory is passed as the argument the config file specified in buildbot.tac is checked. If the argument is the path to a config file then it will be checked without using the buildbot.tac file. cleanupdb buildbot cleanupdb {BASEDIR|CONFIG_FILE} [-q] This command is frontend for various database maintenance jobs: optimiselogs: This optimization groups logs into bigger chunks to apply higher level of compression. This script runs for as long as it takes to finish the job including the time needed to check master.cfg file. copy-db buildbot copy-db {DESTINATION_URL} {BASEDIR} [-q] This command copies all buildbot data from source database configured in the buildbot configuration file to the destination database. The URL of the destination database is specified on the command line. The destination database may have different type from the source database. The destination database must be empty. The script will initialize it in the same way as if a new Buildbot installation was created. Source database must be already upgraded to the current Buildbot version by the buildbot upgrade-master command. 2.7.1.2. Developer Tools These tools are provided for use by the developers who are working on the code that the buildbot is monitoring. try This lets a developer to ask the question What would happen if I committed this patch right now? . It runs the unit test suite (across multiple build platforms) on the developer’s current code, allowing them to make sure they will not break the tree when they finally commit their changes. The buildbot try command is meant to be run from within a developer’s local tree, and starts by figuring out the base revision of that tree (what revision was current the last time the tree was updated), and a patch that can be applied to that revision of the tree to make it match the developer’s copy. This (revision, patch) pair is then sent to the buildmaster, which runs a build with that SourceStamp . If you want, the tool will emit status messages as the builds run, and will not terminate until the first failure has been detected (or the last success). There is an alternate form which accepts a pre-made patch file (typically the output of a command like svn diff ). This --diff form does not require a local tree to run from. See try –diff concerning the --diff command option. For this command to work, several pieces must be in place: the Try_Jobdir or : Try_Userpass , as well as some client-side configuration. Locating the master The try command needs to be told how to connect to the try scheduler, and must know which of the authentication approaches described above is in use by the buildmaster. You specify the approach by using --connect=ssh or --connect=pb (or try_connect = 'ssh' or try_connect = 'pb' in .buildbot/options ). For the PB approach, the command must be given a option –master argument (in the form HOST : PORT ) that points to TCP port that you picked in the Try_Userpass scheduler. It also takes a option –username and option –passwd pair of arguments that match one of the entries in the buildmaster’s userpass list. These arguments can also be provided as try_master , try_username , and try_password entries in the .buildbot/options file. For the SSH approach, the command must be given option –host and option –username , to get to the buildmaster host. It must also be given option –jobdir , which points to the inlet directory configured above. The jobdir can be relative to the user’s home directory, but most of the time you will use an explicit path like ~buildbot/project/trydir . These arguments can be provided in .buildbot/options as try_host , try_username , try_password , and try_jobdir . If you need to use something different from the default ssh command for connecting to the remote system, you can use –ssh command line option or try_ssh in the configuration file. The SSH approach also provides a option –buildbotbin argument to allow specification of the buildbot binary to run on the buildmaster. This is useful in the case where buildbot is installed in a virtualenv on the buildmaster host, or in other circumstances where the buildbot command is not on the path of the user given by option –username . The option –buildbotbin argument can be provided in .buildbot/options as try_buildbotbin The following command line arguments are deprecated, but retained for backward compatibility: --tryhost is replaced by option –host --trydir is replaced by option –jobdir --master is replaced by option –masterstatus Likewise, the following .buildbot/options file entries are deprecated, but retained for backward compatibility: try_dir is replaced by try_jobdir masterstatus is replaced by try_masterstatus Waiting for results If you provide the option –wait option (or try_wait = True in .buildbot/options ), the buildbot try command will wait until your changes have either been proven good or bad before exiting. Unless you use the option –quiet option (or try_quiet=True ), it will emit a progress message every 60 seconds until the builds have completed. The SSH connection method does not support waiting for results. Choosing the Builders A trial build is performed on multiple Builders at the same time, and the developer gets to choose which Builders are used (limited to a set selected by the buildmaster admin with the TryScheduler ’s builderNames= argument). The set you choose will depend upon what your goals are: if you are concerned about cross-platform compatibility, you should use multiple Builders, one from each platform of interest. You might use just one builder if that platform has libraries or other facilities that allow better test coverage than what you can accomplish on your own machine, or faster test runs. The set of Builders to use can be specified with multiple option –builder arguments on the command line. It can also be specified with a single try_builders option in .buildbot/options that uses a list of strings to specify all the Builder names: try_builders = [ "full-OSX" , "full-win32" , "full-linux" ] If you are using the PB approach, you can get the names of the builders that are configured for the try scheduler using the get-builder-names argument: buildbot try --get-builder-names --connect = pb --master = ... --username = ... --passwd = ... Specifying the VC system The try command also needs to know how to take the developer’s current tree and extract the (revision, patch) source-stamp pair. Each VC system uses a different process, so you start by telling the try command which VC system you are using, with an argument like option –vc=cvs or option –vc=git . This can also be provided as try_vc in .buildbot/options . The following names are recognized: bzr cvs darcs hg git mtn p4 svn Finding the top of the tree Some VC systems (notably CVS and SVN) track each directory more-or-less independently, which means the try command needs to move up to the top of the project tree before it will be able to construct a proper full-tree patch. To accomplish this, the try command will crawl up through the parent directories until it finds a marker file. The default name for this marker file is .buildbot-top , so when you are using CVS or SVN you should touch .buildbot-top from the top of your tree before running buildbot try . Alternatively, you can use a filename like ChangeLog or README , since many projects put one of these files in their top-most directory (and nowhere else). To set this filename, use --topfile=ChangeLog , or set it in the options file with try_topfile = 'ChangeLog' . You can also manually set the top of the tree with --topdir=~/trees/mytree , or try_topdir = '~/trees/mytree' . If you use try_topdir , in a .buildbot/options file, you will need a separate options file for each tree you use, so it may be more convenient to use the try_topfile approach instead. Other VC systems which work on full projects instead of individual directories (Darcs, Mercurial, Git, Monotone) do not require try to know the top directory, so the option –try-topfile and option –try-topdir arguments will be ignored. If the try command cannot find the top directory, it will abort with an error message. The following command line arguments are deprecated, but retained for backward compatibility: --try-topdir is replaced by option –topdir --try-topfile is replaced by option –topfile Determining the branch name Some VC systems record the branch information in a way that try can locate it. For the others, if you are using something other than the default branch, you will have to tell the buildbot which branch your tree is using. You can do this with either the option –branch argument, or a try_branch entry in the .buildbot/options file. Determining the revision and patch Each VC system has a separate approach for determining the tree’s base revision and computing a patch. CVS try pretends that the tree is up to date. It converts the current time into a option -D time specification, uses it as the base revision, and computes the diff between the upstream tree as of that point in time versus the current contents. This works, more or less, but requires that the local clock be in reasonably good sync with the repository. SVN try does a svn status -u to find the latest repository revision number (emitted on the last line in the Status against revision: NN message). It then performs an svn diff -r NN to find out how your tree differs from the repository version, and sends the resulting patch to the buildmaster. If your tree is not up to date, this will result in the try tree being created with the latest revision, then backwards patches applied to bring it back to the version you actually checked out (plus your actual code changes), but this will still result in the correct tree being used for the build. bzr try does a bzr revision-info to find the base revision, then a bzr diff -r$base.. to obtain the patch. Mercurial hg parents --template '{node}\n' emits the full revision id (as opposed to the common 12-char truncated) which is a SHA1 hash of the current revision’s contents. This is used as the base revision. hg diff then provides the patch relative to that revision. For try to work, your working directory must only have patches that are available from the same remotely-available repository that the build process’ source.Mercurial will use. Perforce try does a p4 changes -m1 ... to determine the latest changelist and implicitly assumes that the local tree is synced to this revision. This is followed by a p4 diff -du to obtain the patch. A p4 patch differs slightly from a normal diff. It contains full depot paths and must be converted to paths relative to the branch top. To convert the following restriction is imposed. The p4base (see P4Source ) is assumed to be //depot Darcs try does a darcs changes --context to find the list of all patches back to and including the last tag that was made. This text file (plus the location of a repository that contains all these patches) is sufficient to re-create the tree. Therefore the contents of this context file are the revision stamp for a Darcs-controlled source tree. It then does a darcs diff -u to compute the patch relative to that revision. Git git branch -v lists all the branches available in the local repository along with the revision ID it points to and a short summary of the last commit. The line containing the currently checked out branch begins with “* “ (star and space) while all the others start with “ “ (two spaces). try scans for this line and extracts the branch name and revision from it. Then it generates a diff against the base revision. Todo I’m not sure if this actually works the way it’s intended since the extracted base revision might not actually exist in the upstream repository. Perhaps we need to add a –remote option to specify the remote tracking branch to generate a diff against. Monotone mtn automate get_base_revision_id emits the full revision id which is a SHA1 hash of the current revision’s contents. This is used as the base revision. mtn diff then provides the patch relative to that revision. For try to work, your working directory must only have patches that are available from the same remotely-available repository that the build process’ source.Monotone will use. patch information You can provide the option –who=dev to designate who is running the try build. This will add the dev to the Reason field on the try build’s status web page. You can also set try_who = dev in the .buildbot/options file. Note that option –who=dev will not work on version 0.8.3 or earlier masters. Similarly, option –comment=COMMENT will specify the comment for the patch, which is also displayed in the patch information. The corresponding config-file option is try_comment . Sending properties You can set properties to send with your change using either the option –property=key=value option, which sets a single property, or the option –properties=key1=value1,key2=value2… option, which sets multiple comma-separated properties. Either of these can be specified multiple times. Note that the option –properties option uses commas to split on properties, so if your property value itself contains a comma, you’ll need to use the option –property option to set it. try –diff Sometimes you might have a patch from someone else that you want to submit to the buildbot. For example, a user may have created a patch to fix some specific bug and sent it to you by email. You’ve inspected the patch and suspect that it might do the job (and have at least confirmed that it doesn’t do anything evil). Now you want to test it out. One approach would be to check out a new local tree, apply the patch, run your local tests, then use buildbot try to run the tests on other platforms. An alternate approach is to use the buildbot try --diff form to have the buildbot test the patch without using a local tree. This form takes a option –diff argument which points to a file that contains the patch you want to apply. By default this patch will be applied to the TRUNK revision, but if you give the optional option –baserev argument, a tree of the given revision will be used as a starting point instead of TRUNK. You can also use buildbot try --diff=- to read the patch from stdin . Each patch has a patchlevel associated with it. This indicates the number of slashes (and preceding pathnames) that should be stripped before applying the diff. This exactly corresponds to the option -p or option –strip argument to the patch utility. By default buildbot try --diff uses a patchlevel of 0, but you can override this with the option -p argument. When you use option –diff , you do not need to use any of the other options that relate to a local tree, specifically option –vc , option –try-topfile , or option –try-topdir . These options will be ignored. Of course you must still specify how to get to the buildmaster (with option –connect , option –tryhost , etc). 2.7.1.3. Other Tools These tools are generally used by buildmaster administrators. sendchange This command is used to tell the buildmaster about source changes. It is intended to be used from within a commit script, installed on the VC server. It requires that you have a PBChangeSource ( PBChangeSource ) running in the buildmaster (by being set in c['change_source'] ). buildbot sendchange --master {MASTERHOST}:{PORT} --auth {USER}:{PASS} --who {USER} {FILENAMES..} The option –auth option specifies the credentials to use to connect to the master, in the form user:pass . If the password is omitted, then sendchange will prompt for it. If both are omitted, the old default (username “change” and password “changepw”) will be used. Note that this password is well-known, and should not be used on an internet-accessible port. The option –master and option –username arguments can also be given in the options file (see .buildbot config directory ). There are other (optional) arguments which can influence the Change that gets submitted: --branch (or option branch ) This provides the (string) branch specifier. If omitted, it defaults to None , indicating the default branch . All files included in this Change must be on the same branch. --category (or option category ) This provides the (string) category specifier. If omitted, it defaults to None , indicating no category . The category property can be used by schedulers to filter what changes they listen to. --project (or option project ) This provides the (string) project to which this change applies, and defaults to ‘’. The project can be used by schedulers to decide which builders should respond to a particular change. --repository (or option repository ) This provides the repository from which this change came, and defaults to '' . --revision This provides a revision specifier, appropriate to the VC system in use. --revision_file This provides a filename which will be opened and the contents used as the revision specifier. This is specifically for Darcs, which uses the output of darcs changes --context as a revision specifier. This context file can be a couple of kilobytes long, spanning a couple lines per patch, and would be a hassle to pass as a command-line argument. --property This parameter is used to set a property on the Change generated by sendchange . Properties are specified as a name : value pair, separated by a colon. You may specify many properties by passing this parameter multiple times. --comments This provides the change comments as a single argument. You may want to use option –logfile instead. --logfile This instructs the tool to read the change comments from the given file. If you use - as the filename, the tool will read the change comments from stdin. --encoding Specifies the character encoding for all other parameters, defaulting to 'utf8' . --vc Specifies which VC system the Change is coming from, one of: cvs , svn , darcs , hg , bzr , git , mtn , or p4 . Defaults to None . user Note that in order to use this command, you need to configure a CommandlineUserManager instance in your master.cfg file, which is explained in Users Options . This command allows you to manage users in buildbot’s database. No extra requirements are needed to use this command, aside from the Buildmaster running. For details on how Buildbot manages users, see Users . --master The user command can be run virtually anywhere provided a location of the running buildmaster. The option –master argument is of the form MASTERHOST : PORT . --username PB connection authentication that should match the arguments to CommandlineUserManager . --passwd PB connection authentication that should match the arguments to CommandlineUserManager . --op There are four supported values for the option –op argument: add , update , remove , and get . Each are described in full in the following sections. --bb_username Used with the option –op=update option, this sets the user’s username for web authentication in the database. It requires option –bb_password to be set along with it. --bb_password Also used with the option –op=update option, this sets the password portion of a user’s web authentication credentials into the database. The password is first encrypted prior to storage for security reasons. --ids When working with users, you need to be able to refer to them by unique identifiers to find particular users in the database. The option –ids option lets you specify a comma separated list of these identifiers for use with the user command. The option –ids option is used only when using option –op=remove or option –op=get . --info Users are known in buildbot as a collection of attributes tied together by some unique identifier (see Users ). These attributes are specified in the form {TYPE}={VALUE} when using the option –info option. These {TYPE}={VALUE} pairs are specified in a comma separated list, so for example: --info=svn=jdoe,git='John Doe <joe@example.com>' The option –info option can be specified multiple times in the user command, as each specified option will be interpreted as a new user. Note that option –info is only used with option –op=add or with option –op=update , and whenever you use option –op=update you need to specify the identifier of the user you want to update. This is done by prepending the option –info arguments with {ID:} . If we were to update 'jschmo' from the previous example, it would look like this: --info=jdoe:git='Joe Doe <joe@example.com>' Note that option –master , option –username , option –passwd , and option –op are always required to issue the user command. The option –master , option –username , and option –passwd options can be specified in the option file with keywords user_master , user_username , and user_passwd , respectively. If user_master is not specified, then option –master from the options file will be used instead. Below are examples of how each command should look. Whenever a user command is successful, results will be shown to whoever issued the command. For option –op=add : buildbot user --master={MASTERHOST} --op=add \ --username={USER} --passwd={USERPW} \ --info={TYPE}={VALUE},... For option –op=update : buildbot user --master={MASTERHOST} --op=update \ --username={USER} --passwd={USERPW} \ --info={ID}:{TYPE}={VALUE},... For option –op=remove : buildbot user --master={MASTERHOST} --op=remove \ --username={USER} --passwd={USERPW} \ --ids={ID1},{ID2},... For option –op=get : buildbot user --master={MASTERHOST} --op=get \ --username={USER} --passwd={USERPW} \ --ids={ID1},{ID2},... A note on option –op=update : when updating the option –bb_username and option –bb_password , the option –info doesn’t need to have additional {TYPE}={VALUE} pairs to update and can just take the {ID} portion. 2.7.1.4. .buildbot config directory Many of the buildbot tools must be told how to contact the buildmaster that they interact with. This specification can be provided as a command-line argument, but most of the time it will be easier to set them in an options file. The buildbot command will look for a special directory named .buildbot , starting from the current directory (where the command was run) and crawling upwards, eventually looking in the user’s home directory. It will look for a file named options in this directory, and will evaluate it as a Python script, looking for certain names to be set. You can just put simple name = 'value' pairs in this file to set the options. For a description of the names used in this file, please see the documentation for the individual buildbot sub-commands. The following is a brief sample of what this file’s contents could be. # for status-reading tools masterstatus = 'buildbot.example.org:12345' # for 'sendchange' or the debug port master = 'buildbot.example.org:18990' Note carefully that the names in the options file usually do not match the command-line option name. master Equivalent to option –master for sendchange . It is the location of the pb.PBChangeSource for `sendchange . username Equivalent to option –username for the sendchange command. branch Equivalent to option –branch for the sendchange command. category Equivalent to option –category for the sendchange command. try_connect Equivalent to option –connect , this specifies how the try command should deliver its request to the buildmaster. The currently accepted values are ssh and pb . try_builders Equivalent to option –builders , specifies which builders should be used for the try build. try_vc Equivalent to option –vc for try , this specifies the version control system being used. try_branch Equivalent to option –branch , this indicates that the current tree is on a non-trunk branch. try_topdir try_topfile Use try_topdir , equivalent to option –try-topdir , to explicitly indicate the top of your working tree, or try_topfile , equivalent to option –try-topfile to name a file that will only be found in that top-most directory. try_host try_username try_dir When try_connect is ssh , the command will use try_host for option –tryhost , try_username for option –username , and try_dir for option –trydir . Apologies for the confusing presence and absence of ‘try’. try_username try_password try_master Similarly, when try_connect is pb , the command will pay attention to try_username for option –username , try_password for option –passwd , and try_master for option –master . try_wait masterstatus try_wait and masterstatus (equivalent to option –wait and master , respectively) are used to ask the try command to wait for the requested build to complete. 2.7.2. buildbot-worker buildbot-worker command-line tool is used for worker management only and does not provide any additional functionality. One can create, start, stop and restart the worker. 2.7.2.1. create-worker This creates a new directory and populates it with files that let it be used as a worker’s base directory. You must provide several arguments, which are used to create the initial buildbot.tac file. The option -r option is advisable here, just like for create-master . buildbot-worker create-worker -r {BASEDIR} {MASTERHOST}:{PORT} {WORKERNAME} {PASSWORD} The create-worker options are described in Worker Options . 2.7.2.2. start This starts a worker which was already created in the given base directory. The daemon is launched in the background, with events logged to a file named twistd.log . buildbot-worker start [--nodaemon] BASEDIR The option –nodaemon option instructs Buildbot to skip daemonizing. The process will start in the foreground. It will only return to the command-line when it is stopped. 2.7.2.3. restart buildbot-worker restart [--nodaemon] BASEDIR This restarts a worker which is already running. It is equivalent to a stop followed by a start . The option –nodaemon option has the same meaning as for start . 2.7.2.4. stop This terminates the daemon worker running in the given directory. buildbot stop BASEDIR Previous Next © Copyright Buildbot Team Members. Built with Sphinx using a theme provided by Read the Docs . | 2026-01-13T09:30:34 |
https://logging.apache.org/log4j/2.x/manual/scripts.html | Scripts :: Apache Log4j a subproject of Apache Logging Services Home Download Release notes Support Versioning and maintenance policy Security Manual Getting started Installation API Loggers Event Logger Simple Logger Status Logger Fluent API Fish tagging Levels Markers Thread Context Messages Flow Tracing Implementation Architecture Configuration Configuration file Configuration properties Programmatic configuration Appenders File appenders Rolling file appenders Database appenders Network Appenders Message queue appenders Delegating Appenders Layouts JSON Template Layout Pattern Layout Lookups Filters Scripts JMX Extending Plugins Performance Asynchronous loggers Garbage-free logging References Plugin reference Java API reference Resources F.A.Q. Migrating from Log4j 1 Migrating from Logback Migrating from SLF4J Building GraalVM native images Integrating with Hibernate Integrating with Jakarta EE Integrating with service-oriented architectures Development Components Log4j IOStreams Log4j Spring Boot Support Log4j Spring Cloud Configuration JUL-to-Log4j bridge Log4j-to-JUL bridge Related projects Log4j Jakarta EE Log4j JMX GUI Log4j Kotlin Log4j Scala Log4j Tools Log4j Transformation Tools Home Manual Implementation Configuration Scripts Edit this Page Scripts Log4j provides support for JSR 223 scripting languages to be used in some of its components. In order to enable a scripting language, its name must be included in the log4j2.scriptEnableLanguages configuration property. Each component that allows scripts can contain on of the following configuration elements: Script This element specifies the content of the script directly and has: a required language configuration attribute that specifies the name of the JSR 223 language to use, a required scriptText configuration attribute that contains the text of the script. In the XML configuration format, the text of the script can also be written as content of the <Script> XML element. This allows the usage of a CDATA block. The element can be assigned a name using the name configuration attribute. See also Plugin reference . ScriptFile This element points to an external script file and has: a required path attribute that points to the path to a file name. an optional language attribute that specifies the name of the JSR 223 language to use. If not provided, the language is deduced from the extension of the file. an optional isWatched attribute. If set to true the script file will be monitored for changes. The element can be assigned a name using the name configuration attribute. See also Plugin reference . ScriptRef This element references a named script from the global Scripts container plugin in the configuration file. See also Plugin reference . The environment in which the script runs is different for each Log4j script-based component. XML JSON YAML Properties Snippet from an example log4j2.xml <Appenders> <Console name="STDOUT"> <PatternLayout> <ScriptPatternSelector defaultPattern="%d %p %m%n"> <ScriptRef ref="SELECTOR_SCRIPT"/> <PatternMatch key="NoLocation" pattern="[%-5level] %c{1.} %msg%n"/> <PatternMatch key="Flow" pattern="[%-5level] %c{1.} ====== %C{1.}.%M:%L %msg ======%n"/> </ScriptPatternSelector> </PatternLayout> </Console> </Appenders> <Loggers> <Logger name="EventLogger"> <ScriptFilter onMatch="ACCEPT" onMismatch="DENY"> <Script name="EVENT_LOGGER_FILTER" language="groovy"><![CDATA[ if (logEvent.getMarker() != null && logEvent.getMarker().isInstanceOf("FLOW")) { return true; } else if (logEvent.getContextMap().containsKey("UserId")) { return true; } return false; ]]> </Script> </ScriptFilter> </Logger> <Root level="INFO"> <ScriptFilter onMatch="ACCEPT" onMismatch="DENY"> <ScriptRef ref="ROOT_FILTER"/> </ScriptFilter> <AppenderRef ref="STDOUT"/> </Root> </Loggers> <Scripts> <Script name="SELECTOR_SCRIPT" language="javascript"><![CDATA[ var result; if (logEvent.getLoggerName().equals("JavascriptNoLocation")) { result = "NoLocation"; } else if (logEvent.getMarker() != null && logEvent.getMarker().isInstanceOf("FLOW")) { result = "Flow"; } result; ]]> </Script> <ScriptFile name="ROOT_FILTER" path="scripts/filter.groovy"/> </Scripts> Snippet from an example log4j2.json "Appenders": { "Console": { "name": "STDOUT", "PatternLayout": { "ScriptPatternSelector": { "defaultPattern": "%d %p %m%n", "ScriptRef": { "ref": "SELECTOR_SCRIPT", "PatternMatch": [ { "key": "NoLocation", "pattern": "[%-5level] %c{1.} %msg%n" }, { "key": "Flow", "pattern": "[%-5level] %c{1.} ====== %C{1.}.%M:%L %msg ======%n" } ] } } } } }, "Loggers": { "Logger": { "name": "EventLogger", "ScriptFilter": { "onMatch": "ACCEPT", "onMismatch": "DENY", "Script": { "name": "EVENT_LOGGER_FILTER", "language": "groovy", "scriptText": "if (logEvent.getMarker() != null && logEvent.getMarker().isInstanceOf('FLOW'))) { return true; } else if (logEvent.getContextMap().containsKey('UserId')) { return true; } return false;" } } }, "Root": { "level": "INFO", "ScriptFilter": { "onMatch": "ACCEPT", "onMismatch": "DENY", "ScriptRef": { "ref": "ROOT_FILTER" } }, "AppenderRef": { "ref": "STDOUT" } } }, "Scripts": { "Script": { "name": "SELECTOR_SCRIPT", "language": "javascript", "scriptText": "var result; if (logEvent.getLoggerName().equals('JavascriptNoLocation')) { result = 'NoLocation'; } else if (logEvent.getMarker() != null && logEvent.getMarker().isInstanceOf('FLOW')) { result = 'Flow'; } result;" }, "ScriptFile": { "name": "ROOT_FILTER", "path": "scripts/filter.groovy" } } Snippet from an example log4j2.yaml Appenders: Console: name: "STDOUT" PatternLayout: ScriptPatternSelector: defaultPattern: "%d %p %m%n" ScriptRef: ref: "SELECTOR_SCRIPT" PatternMatch: - key: "NoLocation" pattern: "[%-5level] %c{1.} %msg%n" - key: "Flow" pattern: "[%-5level] %c{1.} ====== %C{1.}.%M:%L %msg ======%n" Loggers: Logger: name: "EventLogger" ScriptFilter: onMatch: "ACCEPT" onMismatch: "DENY" Script: name: "EVENT_LOGGER_FILTER" language: "groovy" scriptText: | if (logEvent.getMarker() != null && logEvent.getMarker().isInstanceOf("FLOW")) { return true; } else if (logEvent.getContextMap().containsKey("UserId")) { return true; } return false; Root: level: "INFO" ScriptFilter: onMatch: "ACCEPT" onMismatch: "DENY" ScriptRef: ref: "ROOT_FILTER" AppenderRef: ref: "STDOUT" Scripts: Script: name: "SELECTOR_SCRIPT" language: "javascript" scriptText: | var result; if (logEvent.getLoggerName().equals("JavascriptNoLocation")) { result = "NoLocation"; } else if (logEvent.getMarker() != null && logEvent.getMarker().isInstanceOf("FLOW")) { result = "Flow"; } result; ScriptFile: name: "ROOT_FILTER" path: "scripts/filter.groovy" Snippet from an example log4j2.properties appender.0.type = Console appender.0.name = STDOUT appender.0.layout.type = PatternLayout appender.0.layout.selector = ScriptPatternSelector appender.0.layout.selector.defaultPattern = %d %p %m%n appender.0.layout.selector.scriptRef.type = ScriptRef appender.0.layout.selector.scriptRef.ref = SELECTOR_SCRIPT appender.0.layout.selector.match[0].type = PatternMatch appender.0.layout.selector.match[0].key = NoLocation appender.0.layout.selector.match[0].pattern = [%-5level] %c{1.} %msg%n appender.0.layout.selector.match[1].type = PatternMatch appender.0.layout.selector.match[1].key = Flow appender.0.layout.selector.match[1].pattern = \ [%-5level] %c{1.} ====== %C{1.}.%M:%L %msg ======%n logger.0.name = EventLogger logger.0.filter.0.type = ScriptFilter logger.0.filter.0.onMatch = ACCEPT logger.0.filter.0.onMismatch = DENY logger.0.filter.0.script.type = Script logger.0.filter.0.script.name = EVENT_LOGGER_FILTER logger.0.filter.0.script.language = groovy logger.0.filter.0.script.scriptText = \ if (logEvent.getMarker() != null\ && logEvent.getMarker().isInstanceOf("FLOW"))) {\ return true;\ } else if (logEvent.getContextMap().containsKey("UserId")) {\ return true;\ }\ return false; rootLogger.level = INFO rootLogger.filter.0.type = ScriptFilter rootLogger.filter.0.onMatch = ACCEPT rootLogger.filter.0.onMismatch = DENY rootLogger.filter.0.scriptRef.type = ScriptRef rootLogger.filter.0.scriptRef.ref = ROOT_FILTER rootLogger.appenderRef.0.ref = STDOUT script.0.type = Script script.0.name = SELECTOR_SCRIPT script.0.language = javascript script.0.scriptText = \ var result;\ if (logEvent.getLoggerName().equals("JavascriptNoLocation")) {\ result = "NoLocation";\ } else if (logEvent.getMarker() != null\ && logEvent.getMarker().isInstanceOf("FLOW")) {\ result = "Flow";\ }\ result; script.1.type = ScriptFile script.1.name = ROOT_FILTER script.1.path = scripts/filter.groovy A special note on Beanshell JSR 223 scripting engines are supposed to identify that they support the Compilable interface if they support compiling their scripts. Beanshell does extend the Compilable interface, but an attempt to compile a script ends up in an Error being thrown. Log4j catches the throwable, but issues a warning in Status Logger . 2015-09-27 16:13:23,095 main DEBUG Script BeanShellSelector is compilable 2015-09-27 16:13:23,096 main WARN Error compiling script java.lang.Error: unimplemented at bsh.engine.BshScriptEngine.compile(BshScriptEngine.java:175) at bsh.engine.BshScriptEngine.compile(BshScriptEngine.java:154) at org.apache.logging.log4j.core.script.ScriptManager$MainScriptRunner.<init>(ScriptManager.java:125) at org.apache.logging.log4j.core.script.ScriptManager.addScript(ScriptManager.java:94) Copyright © 1999-2025 The Apache Software Foundation . Licensed under the Apache Software License, Version 2.0 . Please read our privacy policy . Apache, Log4j, and the Apache feather logo are trademarks or registered trademarks of The Apache Software Foundation. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. | 2026-01-13T09:30:34 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.