Qualcomm has open-sourced ELD, a new linker designed specifically for embedded systems. ELD aims to be faster and more memory-efficient than traditional linkers like GNU ld, especially beneficial for resource-constrained devices. It achieves this through features like parallel processing, demand paging, and a simplified design focusing on common embedded use cases. ELD supports ELF and is designed for integration with existing embedded workflows, offering potential improvements in link times and memory usage during development.
Qualcomm has prevailed in a significant licensing dispute with Arm. A confidential arbitration ruling affirmed Qualcomm's right to continue licensing Arm's instruction set architecture for its Nuvia-designed chips under existing agreements. This victory allows Qualcomm to proceed with its plans to incorporate these custom-designed processors into its products, potentially disrupting the server chip market. Arm had argued that the licenses were non-transferable after Qualcomm acquired Nuvia, but the arbitrator disagreed. Financial details of the ruling remain undisclosed.
Hacker News commenters largely discuss the implications of Qualcomm's legal victory over Arm. Several express concern that this decision sets a dangerous precedent, potentially allowing companies to sub-license core technology they don't fully own, stifling innovation and competition. Some speculate this could push other chip designers to RISC-V, an open-source alternative to Arm's architecture. Others question the long-term viability of Arm's business model if they cannot control their own licensing. Some commenters see this as a specific attack on Nuvia's (acquired by Qualcomm) custom core designs, with Qualcomm leveraging their market power. Finally, a few express skepticism about the reporting and suggest waiting for further details to emerge.
Summary of Comments ( 0 )
https://news.ycombinator.com/item?id=43644966
Hacker News users generally expressed cautious optimism about ELD, Qualcomm's new embedded linker. Several commenters questioned its practical advantages over existing linkers like ld, particularly regarding its performance and debugging capabilities. Some wondered about its long-term support given Qualcomm's history with open-source projects. Others pointed out potential benefits like improved memory usage and build times, especially for complex embedded systems. The lack of clear benchmarks comparing ELD to established solutions was a recurring concern. A few users expressed interest in trying ELD for their projects, while others remained skeptical, preferring to wait for more evidence of its real-world effectiveness. The discussion also touched on the challenges of embedded development and the need for better tooling.
The Hacker News post titled "ELD: A new open-source embedded linker tool for embedded systems" has generated several comments discussing various aspects of the new linker and its potential impact.
One commenter expressed skepticism about the genuine openness of the project, pointing out Qualcomm's history with open-source projects and suggesting they might abandon it if it doesn't directly benefit their business interests. They questioned the long-term viability of relying on a tool from a vendor with such a track record.
Another commenter focused on the technical merits, praising the linker's claimed performance improvements and the ability to perform link-time garbage collection, which can significantly reduce the size of embedded binaries. They expressed excitement about potentially integrating it into their own workflow.
Several commenters discussed the challenges and complexities of embedded systems development, highlighting the fragmented tooling landscape and the difficulty of achieving optimal performance and code size. They saw ELD as a potential solution to some of these challenges, particularly for developers working with resource-constrained devices.
One commenter, identifying as an embedded developer, shared their experience with existing linkers and expressed frustration with their limitations, especially when dealing with complex projects. They welcomed the introduction of a new linker, hoping it would offer improved performance and debugging capabilities.
The discussion also touched upon the importance of build systems and the integration of ELD with existing tools. One commenter inquired about CMake integration, emphasizing the need for seamless integration with popular build systems for wider adoption.
A few commenters mentioned other linkers like Mold and LLD, comparing their features and performance with ELD. They speculated on whether ELD could compete with these established tools and what advantages it might offer.
Finally, some commenters expressed interest in learning more about the technical details of ELD, particularly its internal workings and optimization strategies. They hoped for more in-depth documentation and examples to facilitate experimentation and evaluation.