SShortSingh.
Back to feed

Audit finds VHDL standard's float package computes sqrt(2) incorrectly

0
·2 views

A GitHub repository published an audit of the IEEE float package used in the VHDL hardware description language. The audit reports that the package's square root implementation returns an incorrect result for sqrt(2). The finding was shared on Hacker News, where it received 10 points and 5 comments. The source material provides only the repository link and discussion metadata, so details of the specific error and its impact are not included here. The report highlights a possible correctness issue in a standardized hardware design library.

Read the full story at Hacker News

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

Business observability helps banks catch silent payment failures that dashboards miss

A significant share of instant transfers can fail in short windows while technical dashboards still show healthy services, and customers are often the first to notice. Business observability links system behaviour to business outcomes such as amount, channel, transfer type and result, keeping engineers and business owners working from one shared data set. The approach starts by mapping one journey, such as a transfer, into business states and turning useful transitions into business events. Event data can be captured through agent rules, an ingestion API, log transformation or workflow actions, each suited to different situations. Teams are advised to avoid storing sensitive personal data and to mask any such fields at ingestion.

0
ProgrammingDEV Community ·

Microsoft Pushes Back Claude Haiku 4.5 Retirement Date on Foundry to February 2027

Between Friday and Saturday, several AI model shutdown dates changed, with Microsoft Foundry moving its claude-haiku-4-5 retirement from November 15 to February 22, 2027. Google's Gemini API also postponed multiple preview model shutdowns to later dates. Both providers describe their listed dates as provisional, with Google calling them the earliest possible dates and Microsoft noting it can retire models early for security or compliance reasons. The article's author argues that developers should treat shutdown dates as values to re-check from official sources rather than fixed entries in calendars or tickets. The two official sources for Claude on Foundry also temporarily disagreed on the date before aligning.

0
ProgrammingDEV Community ·

AI Developer Tools in 2026: Which Ones Actually Boost Productivity

According to Stack Overflow's 2026 Developer Survey, developers using AI coding assistants finish tasks 55% faster, yet many teams still choose poorly suited tools. Monthly subscriptions for these products add up quickly, often reaching $80 to $120 per engineer once review, testing, and documentation tools are included. The article describes a Warsaw fintech team of eight that switched from Copilot to Cursor and Cody, cutting feature delivery from 11 days to 6 for a small increase in tool costs. It compares Copilot, which fits VS Code and GitHub workflows, with Cursor, which handles larger codebases through broader context awareness. The author recommends a two-week parallel trial measuring merged pull requests, introduced bugs, and review time before committing to a tool.

0
ProgrammingDEV Community ·

Logging pipeline cuts noise by storing structured run records and aggregating p50/p95

A DEV Community post describes a logging approach that stores one structured record per pipeline run, including durations and statuses. Rather than scanning raw logs, the method aggregates performance metrics such as p50 and p95 percentiles. The article links to a source repository and a Mbin instance. It also points to the author's profile on DEV for further context.