# c/c++ Published articles for c/c++. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## В OpenIDE появилась поддержка C/C++ благодаря независимому разработчику DevFeed: [В OpenIDE появилась поддержка C/C++ благодаря независимому разработчику]() Original publisher: [Read original article]() Author: honest\_niceman (Haulmont) Published: 2026-09-16T15:22:55Z Content type: news Language: ru Sources: [Tagir Valeev]() Topics: [c/c++](), [CMake]() Tags: [c](), [c-c-plus-plus](), [c-plus-plus](), [clangd](), [cmake](), [ide-c-plus-plus-5a4cbf95fd05](), [intellij-platform](), [openide](), [rdev](), [tag-a071763eb5bb]() ### AI overview OpenIDE's marketplace has published the C/C++ Support plugin, created by an independent community developer. The beta plugin provides code completion, syntax highlighting, navigation, symbol renaming, project creation, and CMake-based compilation and builds. ### Source excerpt В маркетплейсе OpenIDE появился плагин C/C++ Support, для работы с C и C++. Его написал независимый разработчик из сообщества. Поддержку C++ пользователи просили давно, и автор решил не ждать, а взяться за неё самостоятельно. Читать далее ## NeoEyes NE302 - A tiny USB-C-powered WiFi 6 Edge AI Vision camera based on STM32N6 MCU DevFeed: [NeoEyes NE302 - A tiny USB-C-powered WiFi 6 Edge AI Vision camera based on STM32N6 MCU]() Original publisher: [Read original article]() Author: Jean-Luc Aufranc (CNXSoft) Published: 2026-09-12T02:19:36Z Content type: news Language: en Sources: [CNX Software - Embedded Systems News]() Topics: [Embedded Systems](), [Microcontroller](), [wifi 6](), [Hardware](), [object-detection]() Tags: [c-c-plus-plus](), [camera](), [computer-vision](), [edge-ai](), [embedded-systems](), [hardware](), [mcu](), [object-detection](), [open-source](), [stm32](), [stmicro-stm32](), [vision](), [wifi-6]() ### AI overview The article reports on CamThink's NeoEyes NE302, a compact USB-C-powered Wi-Fi 6 edge AI vision camera built around the STM32N6 MCU. It describes the device's reduced memory and feature set compared with the NE301, along with its camera, wireless, debugging, video-encoding, object-detection, networking, OTA, and security capabilities. ### Source excerpt CamThink NeoEyes NE302 is a tiny WiFi 6 Edge AI camera based on an STM32N6 Arm Cortex-M55 MCU with Neural-ART NPU which the company says is "especially suitable for developers and makers". I initially thought about it as a smaller version of the CamThink NeoEyes NE301 based on the same STM32N6 MCU and 4MP OS04C10 camera sensor. But it's quite a different device. First, it doesn't have a battery, and the USB-C is only used for power. Memory and storage capacities have been reduced to 32 MB PSRAM and 64 MP SPI flash, and a range of built-in and optional features have been removed, including 4G LTE module (global or US), audio wafers, PIR motion connector, and a 16-pin GPIO header, as well as support for PoE power. CamThink NeoEyes NE302 specifications: Vision MCU STMicro STM32N6 MCU Core - Arm 32-bit Cortex-M55 CPU @ up to 800MHz with Arm Helium [...] The post NeoEyes NE302 - A tiny USB-C-powered WiFi 6 Edge AI Vision camera based on STM32N6 MCU appeared first on CNX Software - Embedded Systems News. ## ESP32-C5 Pico board follows Raspberry Pi Pico form factor, ships with on-board or external antenna DevFeed: [ESP32-C5 Pico board follows Raspberry Pi Pico form factor, ships with on-board or external antenna]() Original publisher: [Read original article]() Author: Jean-Luc Aufranc (CNXSoft) Published: 2026-09-09T07:00:50Z Content type: news Language: en Sources: [CNX Software - Embedded Systems News]() Topics: [ESP32-C5](), [Raspberry Pi](), [Espressif](), [cpu](), [RISC-V](), [SOC](), [Bluetooth](), [wifi 6](), [zigbee](), [Matter](), [Embedded Systems](), [ESP-IDF]() Tags: [802-15-4](), [arduino](), [battery](), [ble](), [bluetooth](), [bluetooth-le](), [boot](), [c-c-plus-plus](), [development-board](), [embedded-systems](), [esp-idf](), [esp32](), [esp32-c5](), [espressif](), [gpio](), [hardware](), [iot](), [matter](), [news](), [port](), [raspberry-pi](), [risc-v](), [thread](), [usb](), [waveshare](), [wifi-6](), [zigbee]() ### AI overview The Waveshare ESP32-C5 Pico is a development board in the Raspberry Pi Pico form factor. It uses an ESP32-C5-MINI-1 series module with a RISC-V processor, dual-band WiFi 6, Bluetooth LE, and 802.15.4 support for Zigbee, Thread, and Matter. The board includes GPIO headers, USB-C, buttons, LEDs, and Li-Ion battery support, with variants offering PCB or external antennas. ### Source excerpt Waveshare ESP32-C5 Pico board brings the ESP32-C5 dual-band WiFi 6, Bluetooth LE, and 802.15.4 (Zigbee/Thread) SoC to the Raspberry Pi Pico form factor. The board features an ESP32-C5-MINI-1 Series module with PCB or external antenna, two 20-pin GPIO headers, a USB-C port for power and programming, Reset and Boot buttons, and a few LEDs. It also supports Li-Ion battery charging and discharging. Waveshare ESP32-C5 Pico specifications: Wireless module - ESP32-C5-MINI-1 or ESP32-C5-MINI-1U Wireless MCU - Espressif Systems ESP32-C5HF4 CPU Single-core 32-bit RISC-V processor @ up to 240 MHz Low-power RISC-V core @ 48 MHz acting as the main processor for power-sensitive applications Memory - 384 KB SRAM on-chip Storage - 320 KB ROM, 4MB SPI flash Wireless Dual-band (2.4/5 GHz) 802.11ax WiFi 6, 802.11b/g/n WiFi 4 backward compatibility WiFi modes: Station mode, SoftAP mode, SoftAP + Station mode, and promiscuous mode Bluetooth 5.0 Low Energy (LE) with Mesh support, up [...] The post ESP32-C5 Pico board follows Raspberry Pi Pico form factor, ships with on-board or external antenna appeared first on CNX Software - Embedded Systems News. ## FREE-WILi 2 portable hacking multitool features two RP2350 MCUs, ESP32-C5, ICE40 FPGA, and Raspberry Pi CM0 DevFeed: [FREE-WILi 2 portable hacking multitool features two RP2350 MCUs, ESP32-C5, ICE40 FPGA, and Raspberry Pi CM0]() Original publisher: [Read original article]() Author: Debashis Das Published: 2026-09-09T00:00:02Z Content type: news Language: en Sources: [CNX Software - Embedded Systems News]() Topics: [Embedded Systems](), [Raspberry Pi](), [ESP32-C5](), [Hardware](), [Hacking](), [Linux]() Tags: [802-15-4](), [ble](), [bluetooth](), [broadcom-bcmxxxx](), [c-c-plus-plus](), [can](), [electronics](), [embedded](), [esp32](), [esp32-c5](), [espressif](), [fpga](), [hack](), [hacking](), [hardware](), [lattice](), [linux](), [lora](), [meshtastic](), [nfc](), [open-hardware](), [python](), [raspberry-pi](), [raspberry-pi-rp2350](), [rfid](), [rust](), [security](), [som](), [stm32](), [stmicro-stm32](), [texas-instruments-simplelink](), [thread](), [tools](), [video](), [wi-fi](), [wifi-6](), [wireless](), [zigbee]() ### AI overview The FREE-WILi 2 Founder Edition is an open-hardware, portable multitool for hardware hackers, pentesters, and embedded-system developers. It combines two Raspberry Pi RP2350 MCUs, an ESP32-C5, a Lattice ICE40UP5K FPGA, and a Raspberry Pi CM0 capable of running a full Linux OS, along with touchscreen controls, expansion headers, and multiple wireless interfaces. ### Source excerpt The FREE-WILi 2 (Founder Edition) is an open-hardware, portable hacking multitool and lab designed for hardware hackers, pentesters, and embedded system developers. Designed as an "open electronics multitool," it combines a range of chips and modules into a handheld device, including two Raspberry Pi RP2350 MCUs, an ESP32-C5 for wireless connectivity, a Lattice ICE40UP5K FPGA, and a Raspberry Pi CM0 for running a full Linux OS. The device also features a 3.5-inch capacitive touchscreen, a 14-button physical interface, and modular "Orca" headers for hardware expansion. Its wireless features include 2.4/5GHz Wi-Fi, Bluetooth, LoRa, sub-GHz RF, NFC, 125kHz RFID, and IR. These features make it very suitable for wireless testing, embedded hardware debugging, real-time control, electronics development, and retro gaming, with support for Adafruit Fruit Jam, PICO-8, and Doom. FREE-WILi 2 specifications: Compute Main MCUs - 2x Raspberry Pi RP2350B (One for main controls, one dedicated to display) SoM - Raspberry [...] The post FREE-WILi 2 portable hacking multitool features two RP2350 MCUs, ESP32-C5, ICE40 FPGA, and Raspberry Pi CM0 appeared first on CNX Software - Embedded Systems News. ## Petoi Quaddle - A mini robot dog for physical AI experimentation (Crowdfunding) DevFeed: [Petoi Quaddle - A mini robot dog for physical AI experimentation (Crowdfunding)]() Original publisher: [Read original article]() Author: Jean-Luc Aufranc (CNXSoft) Published: 2026-09-04T08:03:49Z Content type: news Language: en Sources: [CNX Software - Embedded Systems News]() Topics: [Robotics](), [Physical AI](), [ESP32-S3](), [Arduino](), [Raspberry Pi](), [coding](), [Open Source]() Tags: [3d-printing](), [arduino](), [broadcom-bcmxxxx](), [c-c-plus-plus](), [crowdfunding](), [edge-ai](), [education](), [esp32](), [esp32-s3](), [esphome](), [espressif](), [hardware](), [micropython](), [open-source](), [physical-ai](), [raspberry-pi](), [robot-dog](), [robotics](), [ros](), [simulator](), [smart-home](), [smart-speaker](), [stem](), [video]() ### AI overview The Petoi Quaddle is a mini robot dog designed for learning robotics, coding, physical AI, and 3D printing. It uses an ESP32-S3 motion core, optional AI hardware, OpenCat firmware, and multiple programming environments. Petoi launched it on Kickstarter with three models and planned December 2026 shipping. ### Source excerpt If you are not into ducks, but still would like to play around with physical AI, the Petoi Quaddle is a mini robot dog equipped with 4 servos controlling its legs and is designed to help people learn robotics, coding, AI, and 3D printing. The robot is powered by an ESP32-S3 motion core for servo control and wireless connectivity, and an optional ESP32-S3 AI core to enable voice commands and Smart Home control. The robot can walk, strafe, spin, talk back, and react to the user's touch. Three models are available depending on the user's requirements: Builder, Buddy, and Scout. A Raspberry Pi Zero can also be mounted on the top in place of the ESP32-S3-based AI core. Petoi Quaddle runs OpenCat open-source firmware (Arduino) already used in the earlier Petoi Bittle robot dog, first introduced in 2020. The robot can be programmed in a visual programming IDE with drag-and-drop [...] The post Petoi Quaddle - A mini robot dog for physical AI experimentation (Crowdfunding) appeared first on CNX Software - Embedded Systems News. ## Artery AT32F406 and AT32F408 Cortex-M4F MCUs feature optional high-speed USB OTG PHY DevFeed: [Artery AT32F406 and AT32F408 Cortex-M4F MCUs feature optional high-speed USB OTG PHY]() Original publisher: [Read original article]() Author: Debashis Das Published: 2026-09-03T09:40:39Z Content type: news Language: en Sources: [CNX Software - Embedded Systems News]() Topics: [Microcontroller](), [Embedded Systems](), [Arm](), [USB](), [Internet of things](), [cpu](), [Hardware]() Tags: [arm](), [boot](), [bootloader](), [c-c-plus-plus](), [cortex-m4](), [cpu](), [development-board](), [embedded](), [embedded-systems](), [hardware](), [industrial](), [iot](), [mcu](), [microcontrollers](), [processors](), [specifications](), [usb]() ### AI overview The article describes Artery Technology's AT32F406 and AT32F408 Arm Cortex-M4F microcontrollers, which run at up to 216 MHz. The AT32F408 adds USB 2.0 OTG High-Speed support with an integrated PHY, while both devices provide DSP and floating-point capabilities, configurable memory options, QSPI, and a range of digital and analog peripherals. ### Source excerpt Artery Technology AT32F406 and AT32F408 are two new Arm Cortex-M4F MCUs running at up to 216 MHz, with the F408 adding USB OTG High-Speed and an integrated PHY for industrial automation, IoT, USB accessories, and gaming peripherals. The AT32F406/F408 series both offer DSP instructions and a floating-point unit (FPU), integrate up to 512 KB Flash and 192 KB SRAM, and a 4 KB OTP memory for critical data and parameters. The microcontrollers also offer a QSPI interface for external Flash or RAM expansion, and a range of digital and analog peripheral interfaces. Artery AT32F406/AT32F408 specifications: MCU - 32-bit Arm Cortex-M4F CPU up to 216 MHz; also features Memory Protection Unit (MPU) and DSP instructions Memory/Storage 128 KB to 192 KB SRAM 256 KB to 512 KB Flash memory 26 KB boot memory (configurable as a bootloader or general instruction/data memory) 4 KB OTP (one-time programmable) memory QSPI interface for external SPI [...] The post Artery AT32F406 and AT32F408 Cortex-M4F MCUs feature optional high-speed USB OTG PHY appeared first on CNX Software - Embedded Systems News. ## DIY ESP32-P4 weather station & air quality monitor connects to LoRa and ESP-NOW sensors, various weather APIs DevFeed: [DIY ESP32-P4 weather station & air quality monitor connects to LoRa and ESP-NOW sensors, various weather APIs]() Original publisher: [Read original article]() Author: Jean-Luc Aufranc (CNXSoft) Published: 2026-09-03T04:55:46Z Content type: article Language: en Sources: [CNX Software - Embedded Systems News]() Topics: [ESP32-P4](), [ESP32](), [ESP-NOW](), [lora](), [Hardware](), [monitor](), [Embedded Systems](), [dashboards]() Tags: [arduino](), [ble](), [c-c-plus-plus](), [display](), [diy](), [esp-now](), [esp32](), [esp32-p4](), [espressif](), [hardware](), [iot](), [lora](), [monitor](), [sensors](), [touchscreen](), [waveshare](), [wifi](), [wifi-6](), [wireless]() ### AI overview This article describes an ESP32-P4 weather station and air quality monitor built from off-the-shelf boards. It uses a 10.1-inch dashboard, a Sensirion SEN66 multisensor, and LoRa and ESP-NOW sensor nodes, with optional weather data from several APIs and no required cloud account. ### Source excerpt Harald Kreuzer has built an ESP32-P4 weather station and air quality monitor that features a 10.1-inch dashboard display and a built-in Sensirion SEN66 sensor for particulate matter, CO2, VOC, and NOX, and connects to wireless LoRa and ESP-NOW sensors. The project is entirely made of off-the-shelf boards, so no custom hardware is used, and it should be relatively easy to reproduce. It doesn't require any cloud or user account, although it can connect to a choice of weather APIs (Open-Meteo, OpenWeatherMap or Visual Crossing) to display weather forecasts. The build is fully documented in a long blog post, so we'll highlight the key features of the project in this article. Hardware specifications for the main unit: Based on ESP32-P4-Module-DEV-KIT-C Credit card-sized ESP32-P4-Module-DEV-KIT SBC based on an ESP32-P4NRW32 module with ESP32-P4 with 32MB PSRAM and ESP32-C6 for WiFi and BLE 10.1-inch IPS panel with 1280 x 800 resolution, 800:1 contrast ratio, [...] The post DIY ESP32-P4 weather station & air quality monitor connects to LoRa and ESP-NOW sensors, various weather APIs appeared first on CNX Software - Embedded Systems News. ## Circuit Valley CHC5 - A modular USB, HDMI, and Ethernet camera system (Crowdfunding) DevFeed: [Circuit Valley CHC5 - A modular USB, HDMI, and Ethernet camera system (Crowdfunding)]() Original publisher: [Read original article]() Author: Jean-Luc Aufranc (CNXSoft) Published: 2026-09-02T07:25:10Z Content type: news Language: en Sources: [CNX Software - Embedded Systems News]() Topics: [webcam](), [Hardware](), [USB](), [hdmi](), [Ethernet](), [SOC](), [Embedded Systems](), [Linux](), [SDK](), [Open Source]() Tags: [arm](), [buildroot](), [c-c-plus-plus](), [camera](), [computer-vision](), [edge-ai](), [embedded-systems](), [ethernet](), [fpga](), [hardware](), [hdmi](), [kickstarter](), [linux](), [open-source](), [poe](), [sdk](), [soc](), [usb](), [video](), [xilinx-zynq]() ### AI overview CNX Software reports on Circuit Valley's CHC5, a modular camera system built around an AMD/Xilinx Zynq-7020 SoC FPGA. It supports interchangeable sensor and lens configurations, USB, HDMI, and Gigabit Ethernet interfaces, and image-processing and machine-vision workloads. ### Source excerpt Circuit Valley's CHC5 is a modular camera system based on a Core board powered by an AMD/Xilinx Zynq-7020 SoC FPGA, a range of interface boards with USB, HDMI, or Ethernet (PoE), various sensor boards, and a metal enclosure. The solution can be customized with different lens objectives and different sensors with MIPI D-PHY, LVDS, Sub-LVDS, Low Voltage LVDS, or SLVS interfaces. The Zynq-7020's Cortex-A9 cores can handle complex tasks, while the FPGA fabric takes care of high-speed calculation and correction on the image, and can also be leveraged for AI/machine-vision-specific algorithms or complex low-latency hardware acceleration. CHC5 specifications: Core board SoC - Xilinx AMD Zynq-7020 SoC FPGA CPU - Dual-core Arm Cortex-A9 processor FPGA - 85K logic cells, 4.9Mb Block RAM, 220 DSP slices System Memory - 1GB DDR3 Storage 1 Gbit flash memory MicroSD card slot ISP - Full-fledged ISP implemented on FPGA fabric Multiple interface boards with 10Gbps [...] The post Circuit Valley CHC5 - A modular USB, HDMI, and Ethernet camera system (Crowdfunding) appeared first on CNX Software - Embedded Systems News. ## Escalating a Windows driver registry bug to a kernel write primitive DevFeed: [Escalating a Windows driver registry bug to a kernel write primitive]() Original publisher: [Read original article]() Author: "Graham Sutherland"; "Paweł Płatek" Published: 2026-05-05T11:00:00Z Content type: article Language: en Sources: [The Trail of Bits Blog](), [The Trail of Bits Blog]() Topics: [C++](), [Security](), [Vulnerabilities](), [Code](), [Linux](), [Windows]() Tags: [attacks](), [blog](), [bug](), [c-c-plus-plus](), [c-plus-plus](), [large-language-models](), [linux](), [security](), [testing-handbook](), [vulnerabilities](), [windows]() ### AI overview This Trail of Bits article walks through two C/C++ security challenges: a Linux ping program with command injection and an inet_ntoa global-buffer pointer bug, and a Windows driver registry type-confusion issue that can escalate from local denial of service to a kernel write primitive. It also introduces the c-review Claude skill, which turns the security checklist into platform- and threat-model-aware LLM prompts for finding bugs in codebases. ### Source excerpt We recently added a C/C++ security checklist to the Testing Handbook and challenged readers to spot the bugs in two code samples: a deceptively simple Linux ping program and a Windows driver registry handler. If you found the inet_ntoa global buffer gotcha or the missing RTL_QUERY_REGISTRY_TYPECHECK flag, nice work. If not, here's a full walkthrough of both challenges, plus a deep dive into how the Windows registry type confusion escalates from a local denial of service to a kernel write primitive. Since we first released the new C/C++ security checklist, we also developed a new Claude skill, c-review. It turns the checklist into bug-finding prompts that an LLM can run against a codebase. It's also platform and threat-model aware. Run these commands to install the skill: claude skills add-marketplace https://github.com/trailofbits/skills claude skills enable c-review --marketplace trailofbits/skills The Linux ping program challenge The Linux warmup challenge we showed you in the last blog post has an obvious command injection issue. #include #include #include #include #define ALLOWED_IP "127.3.3.1" int main() { char ip_addr[128]; struct in_addr to_ping_host, trusted_host; // get address if (!fgets(ip_addr, sizeof(ip_addr), stdin)) return 1; ip_addr[strcspn(ip_addr, "\n")] = 0; // verify address if (!inet_aton(ip_addr, &to_ping_host)) return 1; char *ip_addr_resolved = inet_ntoa(to_ping_host); // prevent SSRF if ((ntohl(to_ping_host.s_addr) >> 24) == 127) return 1; // only allowed if (!inet_aton(ALLOWED_IP, &trusted_host)) return 1; char *trusted_resolved = inet_ntoa(trusted_host); if (strcmp(ip_addr_resolved, trusted_resolved) != 0) return 1; // ping char cmd[256]; snprintf(cmd, sizeof(cmd), "ping '%s'", ip_addr); system(cmd); return 0; } There are three validations that have to be bypassed before the system call can be reached with malicious inputs: The inet_aton function "converts the Internet host address from the IPv ## A brief history of C/C++ programming languages DevFeed: [A brief history of C/C++ programming languages]() Original publisher: [Read original article]() Author: Daniel Lemire Published: 2026-04-09T14:58:53Z Content type: opinion Language: en Sources: [Daniel Lemire]() Topics: [C](), [C++](), [Programming](), [Java](), [C#](), [Fortran](), [Go Language](), [JavaScript](), [Python]() Tags: [c-c-plus-plus](), [compilation](), [garbage-collection](), [go](), [history](), [languages](), [memory](), [programming](), [programming-languages]() ### AI overview This article presents a brief history of C and C++, explaining how C emerged for low-level systems programming and how C++ added object-oriented, generic, and compile-time metaprogramming features. It then contrasts their portability challenges with Java and discusses JavaScript, Python, C#, and Go. The supplied text ends mid-sentence. ### Source excerpt Initially, we had languages like Fortran (1957), Pascal (1970), and C (1972). Fortran was designed for number crunching and scientific computing. Pascal was restrictive with respect to low-level access (it was deliberately "safe", as meant for teaching structured programming). So C won out as a language that allowed low-level/unsafe programming (pointer arithmetic, direct memory access) ... Continue reading A brief history of C/C++ programming languages ## Swift 6.3 Released DevFeed: [Swift 6.3 Released]() Original publisher: [Read original article]() Author: Joe Heck Published: 2026-03-24T10:00:00Z Content type: release Language: en Sources: [Swift.org]() Topics: [Swift](), [c/c++](), [cross-platform](), [Android](), [Embedded Software Dev](), [Optimization](), [Tooling]() Tags: [android](), [c](), [c-c-plus-plus](), [cross-platform](), [embedded](), [optimization](), [swift](), [tooling]() ### AI overview Swift 6.3 expands Swift across the software stack with improved C interoperability, cross-platform build tooling, embedded-environment support, and an official Swift SDK for Android. The release also adds module selectors and new controls for compiler optimizations. ### Source excerpt Swift is designed to be the language you reach for at every layer of the software stack. Whether you're building embedded firmware, internet-scale services, or full-featured mobile apps, Swift delivers strong safety guarantees, performance control when you need it, and expressive language features and APIs. Swift 6.3 makes these benefits more accessible across the stack. This release expands Swift into new domains and improves developer ergonomics across the board, featuring: More flexible C interoperability Improvements to cross-platform build tooling Improvements for using Swift in embedded environments An official Swift SDK for Android Read on for an overview of the changes and next steps to get started. Language and Standard Library C interoperability Swift 6.3 introduces the @c attribute, which lets you expose Swift functions and enums to C code in your project. Annotating a function or enum with @c prompts Swift to include a corresponding declaration in the generated C header that you can include in your C/C++ files: @c func callFromC() { ... } // Generated C header void callFromC(void); You can provide a custom name to use for the generated C declaration: @c(MyLibrary_callFromC) func callFromC() { ... } // Generated C header void MyLibrary_callFromC(void); @c also works together with @implementation. This lets you provide a Swift implementation for a function declared in a C header: // C header void callFromC(void); // Implementation written in Swift @c @implementation func callFromC() { ... } When using @c together with @implementation, Swift will validate that the Swift function matches a pre-existing declaration in a C header, rather than including a C declaration in the generated header. Module name selectors Swift 6.3 introduces module selectors to specify which imported module Swift should look in for an API used in your code. If you import more than one module that provides API with the same name, module selectors let you disambiguate which API to use: ## Introduction to Fuzzing ESP-IDF components DevFeed: [Introduction to Fuzzing ESP-IDF components]() Original publisher: [Read original article]() Author: John Lee Published: 2026-01-07T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [ESP-IDF](), [Fuzzing/Fuzz testing](), [Testing](), [Vulnerabilities](), [c/c++]() Tags: [blog](), [c-c-plus-plus](), [c-plus-plus](), [component](), [embedded](), [esp-idf](), [fuzzing](), [how-to](), [security](), [testing](), [vulnerabilities](), [vulnerability]() ### AI overview This article introduces fuzzing for ESP-IDF components and embedded libraries. It explains how to fuzz host-compiled code with sanitizers, compares black-box, grey-box, and white-box approaches, and outlines workflows using a basic mutator, AFL++, and protocol-focused harnesses. ### Source excerpt This article introduces fuzzing -- a technique for finding vulnerabilities -- and demonstrates practical workflows and lessons learned for ESP-IDF components and embedded libraries in general. ## A Glance at GPU Goodness in Java: LLM Inference with TornadoVM DevFeed: [A Glance at GPU Goodness in Java: LLM Inference with TornadoVM]() Original publisher: [Read original article]() Author: Edoardo Vacchi Published: 2025-12-11T03:03:21Z Content type: tutorial Language: en Sources: [Java Advent Calendar]() Topics: [TornadoVM](), [Large Language Model](), [GPU](), [Inference](), [Java](), [openjdk](), [Programming]() Tags: [2025](), [c-c-plus-plus](), [c-plus-plus](), [gpu](), [inference](), [java](), [jdk](), [linux](), [llama3](), [llm](), [openjdk](), [tornadovm]() ### AI overview This tutorial introduces TornadoVM, an OpenJDK plugin that compiles annotated Java code for heterogeneous hardware, and explains how it can run LLM inference on GPUs. It covers installation, a basic GPU kernel, and the GPULlama3 project, which demonstrates running a Llama 3 model in Java with GPU acceleration. ### Source excerpt It seems like it's become a tradition that I announce I have joined a new company for the Java Advent of Code. At least this time it's actually an old friend: I am excited to be back at Red Hat, in the llm-d team! Does that mean I forgot about Java? Of course not. If [...] The post A Glance at GPU Goodness in Java: LLM Inference with TornadoVM appeared first on JVM Advent. ## MuddyWater: Snakes by the riverbank DevFeed: [MuddyWater: Snakes by the riverbank]() Original publisher: [Read original article]() Author: ESET Research Published: 2025-12-02T10:00:15Z Content type: article Language: en Sources: [WeLiveSecurity]() Topics: [backdoor](), [C++]() Tags: [analysis](), [api](), [apt](), [backdoor](), [c](), [c-c-plus-plus](), [c-plus-plus](), [critical-infrastructure](), [cryptographic](), [eset-research](), [iran](), [malware](), [memory](), [persistence](), [socks5](), [techniques](), [tools](), [windows]() ### AI overview ESET analyzes a MuddyWater campaign targeting organizations in Israel and Egypt that uses custom loaders, credential stealers, reverse tunnels, and the MuddyViper backdoor to evade defenses and maintain access. ### Source excerpt MuddyWater targets critical infrastructure in Israel and Egypt, relying on custom malware, improved tactics, and a predictable playbook ## This Shit is Hard: Hardening glibc DevFeed: [This Shit is Hard: Hardening glibc]() Original publisher: [Read original article]() Published: 2025-08-20T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [Security](), [Compiler](), [gcc](), [toolchain](), [chainguard](), [chainguard packages](), [C](), [Linux]() Tags: [c](), [c-c-plus-plus](), [chainguard](), [chainguard-containers](), [chainguard-security](), [compiler](), [compiler-flags](), [gcc](), [glibc](), [hardening](), [openssf](), [security](), [toolchain]() ### AI overview Chainguard describes its effort to build glibc with hardened compiler flags. The work involved collaboration with the upstream GCC and glibc projects to resolve complex issues and ship a hardened version of the library. ### Source excerpt Chainguard uses compiler flags to be proactive in the security of our products. See how our compiler flag usage helped us catch a complex bug in glibc. ## GitHub Copilot Now in Espressif-IDE with Copilot4Eclipse DevFeed: [GitHub Copilot Now in Espressif-IDE with Copilot4Eclipse]() Original publisher: [Read original article]() Author: John Lee Published: 2025-02-13T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [GitHub Copilot](), [AI-assisted coding](), [ide](), [c/c++](), [Artificial Intelligence](), [Extension](), [ESP-IDF](), [ESP32]() Tags: [ai](), [blog](), [c-c-plus-plus](), [c-plus-plus](), [code-generation](), [coding-assistant](), [debug](), [esp-idf](), [esp32](), [espressif](), [espressif-ide](), [github-copilot](), [how-to](), [ide](), [install](), [plugin](), [sign-in](), [subscription]() ### AI overview This article presents Copilot4Eclipse as a plugin that brings GitHub Copilot assistance to Espressif-IDE's Eclipse-based C/C++ editor. It describes code suggestions, completions, refactoring, Copilot Chat, and setup steps including installation and GitHub authentication. ### Source excerpt We all love GitHub Copilot as a powerful AI-powered coding assistant that enhances productivity. However, until now, it has been officially available only for VS Code and a few other editors. But here's some good news for Eclipse users! We have tried the Copilot4Eclipse plugin with the Espressif-IDE LSP C/C++ Editor, and it works amazingly well, helping to write code faster and fix bugs. ## Vulnerabilities in NodeJS C/C++ add-on extensions DevFeed: [Vulnerabilities in NodeJS C/C++ add-on extensions]() Original publisher: [Read original article]() Author: Alessio Della Libera Published: 2024-08-14T05:00:00Z Content type: article Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [Vulnerabilities](), [C++](), [Application Security]() Tags: [add-ons](), [awareness](), [blog](), [c-c-plus-plus](), [code-security](), [developer](), [devrel](), [extensions](), [interest](), [javascript](), [npm-packages](), [open-source-security](), [secrel](), [security](), [security-labs](), [snyk-code](), [snyk-open-source](), [vulnerabilities]() ### AI overview An overview of security vulnerabilities and vulnerable patterns in NodeJS C/C++ add-ons, with remediation guidance for open-source maintainers. ### Source excerpt In this blog post, we aim to provide an overview of common security vulnerabilities and vulnerable patterns that can occur when writing C/C++ add-ons in NodeJS. ## Accelerate C/ C++ security with Snyk DevFeed: [Accelerate C/ C++ security with Snyk]() Original publisher: [Read original article]() Author: Lauren Place; Marcie Cheung Published: 2023-12-05T14:00:00Z Content type: release Language: en Sources: [Blog RSS Feed | Snyk]() Topics: [C++](), [c/c++](), [snyk-code](), [Security](), [Vulnerabilities](), [Code](), [Tooling](), [CI/CD](), [Command-line interface](), [ide]() Tags: [acquisition](), [blog](), [c-c-plus-plus](), [c-cpp](), [c-plus-plus](), [ci-cd](), [cli](), [code](), [code-security](), [developer](), [ide](), [pmm](), [pull-request](), [security](), [snyk](), [snyk-code](), [snyk-open-source](), [tooling](), [vs-code](), [vulnerabilities]() ### AI overview Snyk announced general availability of C/C++ support for Snyk Code. The feature analyzes C/C++ source code directly without requiring compilation or a build, provides fast feedback, and integrates with IDE, CLI, Git, pull request, and CI/CD workflows. It also detects vulnerable open source packages and non-compliant licenses, with support for Windows, Linux, desktop, server, web, embedded applications, and frameworks such as Yocto, STL, and Boost. ### Source excerpt Today, Snyk is welcoming C/C++ security into the world of modern development with the general availability of C/C++ support for Snyk Code! ## Application and AI roundup - September DevFeed: [Application and AI roundup - September]() Original publisher: [Read original article]() Author: Adam Published: 2023-10-04T00:00:00Z Content type: article Language: en Sources: [Shostack & Friends Blog]() Topics: [Application Security](), [Memory Safety](), [c/c++](), [open-source-security](), [Zig](), [Artificial Intelligence](), [cisa]() Tags: [appsec](), [c-c-plus-plus](), [c-plus-plus](), [cybersecurity](), [development](), [memory-safety](), [open-source-software-security]() ### AI overview A September roundup covering application security developments involving memory safety, C and C++, Zig, hardware memory tagging, secure-by-design AI guidance, cybersecurity policy for medical devices, and open-source software security. ### Source excerpt September was a big month in appsec for both memory safety and policy ## Accelerate Your IoT Development with the Espressif WebIDE DevFeed: [Accelerate Your IoT Development with the Espressif WebIDE]() Original publisher: [Read original article]() Author: John Lee Published: 2023-04-17T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [Espressif](), [Internet of things](), [ESP-IDF](), [ide](), [Visual Studio Code](), [Framework](), [Website](), [Web](), [Open Source](), [Docker](), [TypeScript](), [Docker Container]() Tags: [blog](), [browser](), [c-c-plus-plus](), [clang](), [docker](), [eclipse-theia](), [esp-idf](), [esp32](), [espressif](), [esptool](), [ide](), [iot](), [json](), [open-source](), [python](), [qemu](), [theia](), [typescript](), [visual-studio-code](), [web]() ### AI overview This tutorial introduces the Espressif Web IDE, an Eclipse Theia-based IDE that integrates the ESP-IDF extension for Visual Studio Code with additional tools. It explains how to run the IDE from source or in Docker, connect to ESP chip serial ports, flash and monitor devices, and use C/C++ language features. ### Source excerpt The Espressif Web IDE is an implementation of the Eclipse Theia framework with the ESP-IDF extension for Visual Studio Code and few additional tools. You can see it in action in the Espressif DevCon22 presentation below. If you haven't used Eclipse Theia before, it is an open-source framework to develop Cloud & Desktop IDEs and tools in TypeScript with a Visual Studio Code UI and Visual Studio Code extensions support or extensions implemented in the OpenVSX registry. ## Smarter C/C++ inlining with \_\_attribute\_\_((flatten)) DevFeed: [Smarter C/C++ inlining with \_\_attribute\_\_((flatten))]() Original publisher: [Read original article]() Author: Andreas Kling Published: 2020-04-27T00:00:00Z Content type: tutorial Language: en Sources: [Andreas Kling]() Topics: [inlining](), [c/c++](), [Optimization](), [clang](), [gcc](), [build times]() Tags: [build-times](), [c-c-plus-plus](), [clang](), [compiler](), [cpp](), [function](), [gcc](), [inlining](), [optimization](), [performance](), [technical]() ### AI overview This post explains how to use the __attribute__((flatten)) function attribute in C/C++ to apply aggressive inlining selectively. GCC and Clang support the attribute, which inlines a function's callees while limiting the program-size, cache-locality, and build-time costs of broader inlining. ### Source excerpt This post describes a compile-time technique for getting the benefits of aggressive inlining in hot code while protecting cool code from its downsides. ## C/C++ Include Guidelines DevFeed: [C/C++ Include Guidelines]() Original publisher: [Read original article]() Published: 2019-10-13T12:14:00Z Content type: tutorial Language: en Sources: [Thomas Young]() Topics: [c/c++](), [C](), [C++](), [Code quality](), [Code](), [modules]() Tags: [c](), [c-c-plus-plus](), [c-plus-plus](), [code](), [code-quality](), [compilation](), [dependencies](), [implementation](), [modules](), [source](), [structure]() ### AI overview An opinionated set of guidelines for organizing include files in C and C++. It covers header and source-file responsibilities, include ordering, repeated-include protection, dependencies, namespaces, naming, and related practices, while noting that C++20 modules change the situation. ### Source excerpt Some (opinionated) guidelines for include file organisation in C/C++. Intro I present a list of points, probably best considered as guidelines, but which I'll refer to as rules throughout the rest of this post, since it trips off the tongue that bit more easily (or perhaps I just have some hidden authoritarian streak). I'll assume the reader knows something about writing code in C or C++, and understands at least the basics about how compilation with include files works. Sometimes I'll say things are obvious to this intended audience, where I think this is necessary for completeness. This is about an ideal way to organise code. For large existing code bases changing the code to follow all of the rules may not be straightforward but it should be possible to make some incremental steps towards the code structure I describe, resulting in some kind of incremental improvements in overall code quality. Many of the rules have exceptions, and it can interesting to explore reasons for these exceptions, as well as the reasons for the rules themselves. Modules As an aside, please note that this is a 'pre-modules' document. If you're using c++ 20 and modules the situation will be different. (At the time of writing I don't have any experience working with modules, and I'm not aware of all the details about how modules will work. I'm hoping that if we follow the rules described here, we should be reasonably well placed for moving to C++20 modules, but if that's not the case, and there are module related details that you think should be taken into account in this document, please let me know in the comments.) The rules 1. Headers are for linkage details, implementation goes in source files. 2. Each source file should have a single matching header. 3. Linkage to a source file should go only through its header. 4. Guard against repeated includes. 5. Each header should be self-sufficient. 6. Each source file includes its own header first. 7. Low level includes come after high level i ## Modern C++ for C Programmers: introduction DevFeed: [Modern C++ for C Programmers: introduction]() Original publisher: [Read original article]() Published: 2018-07-28T11:29:55Z Content type: article Language: en Sources: [Bert Hubert's writings]() Topics: [C++](), [C](), [Programming](), [Programming language](), [Go Language](), [Rust]() Tags: [2017](), [c](), [c-c-plus-plus](), [c-plus-plus](), [go](), [introduction](), [modern](), [programming](), [rust](), [swift]() ### AI overview This introductory article argues that modern C++ can offer C programmers useful capabilities without requiring them to learn the entire language. It presents C++ as powerful and expressive but complex, and outlines a series focused on a selected subset of practical C++ features, primarily targeting C++14 with occasional C++17 features. ### Source excerpt 2018 is an exciting time to be a programmer, with so many good "full service" programming languages to choose from: C, C++ 2017, Go, Python, Rust and who knows Swift too. Programming languages are complicated beasts - even the simplest languages have specifications that run (or would run) in the hundreds of pages, and once you include everything, no serious language is likely to clock in under a thousand. With this comes the fact that every programming language has good parts, and frequently even more bad parts. ## My First GSOC Experience and Introduction to ReactOS DevFeed: [My First GSOC Experience and Introduction to ReactOS]() Original publisher: [Read original article]() Published: 2017-06-13T00:00:00Z Content type: article Language: en Sources: [Front Page on ReactOS Website]() Topics: [ReactOS](), [Programming](), [c/c++](), [Windows](), [Open Source]() Tags: [c-c-plus-plus](), [free](), [gsoc](), [open-source](), [operating-systems](), [os](), [programming](), [react](), [reactos](), [win32](), [winapi]() ### AI overview A personal introduction from a computer science student describing his interest in programming, open-source software, operating systems, and C/C++. The article explains how ReactOS led him toward applying for his first GSOC project and discovering its welcoming community. ### Source excerpt #Introduction: Hi, I am shriraj (aka sr13), currently pursuing my B.Tech in CSE (Computer Science and Engineering) @ National Institute of Technology Goa, India. I am not just studying CSE but I like to play and experiment with CSE. Programming is just another hobby and I knew that its one of my forte the moment I had felt my first 'Hello World!!' with 'C'. (OK, that might be a little exaggeration XD, but yeah you can tell it when you start enjoying the subject so much that you felt code is better art than a poem. [Next page]()