Broken RISC-V code in newlib

Eric Salem ericsalem@gmail.com
Tue Mar 25 15:19:12 GMT 2025


On 3/25/25 10:14 AM, Kito Cheng wrote:
> BTW, I can reproduce those build issue on my clean build as well

Are there any sort of flags you set for your build? I build a stock Newlib
library but I still can't get the build to break for me. I'm wondering how
it knows to use the port specific includes when <> is used to include the
header file for my build and not yours.

> 
> On Tue, Mar 25, 2025 at 11:08 PM Jeff Law <jlaw@ventanamicro.com> wrote:
>>
>> On 3/25/25 8:12 AM, Eric Salem wrote:
>>
>>>
>>> I'm having a hard time recreating this on my machine, which is why I wouldn't have gotten these errors. Can you apply the below patch? It should address the errors. I want to make sure it works for you before emailing the list with a fix.
>> Yea, I can throw it into the tester, it's got provisions for this kind
>> of evaluation.  Results in an hour or so depending on my morning meeting
>> schedule ;-)
>>
>> jeff
>>


More information about the Newlib mailing list