[PATCH 12/42] libcrypt/crypt-md5.c: Fix overflow issues
Joel Sherrill
joel.sherrill at oarcorp.com
Mon Mar 23 23:15:25 UTC 2015
On March 23, 2015 3:23:59 PM CDT, Sebastian Huber <sebastian.huber at embedded-brains.de> wrote:
>
>
>----- Am 23. Mrz 2015 um 16:51 schrieb Gedare Bloom gedare at gwu.edu:
>
>> I guess this is a problem for 16-bit targets? changing the constants
>> to 16UL and 8UL also should work. A comment should be made that this
>> is only for 16-bit targets. If we rid RTEMS of those, we can get rid
>> of some of these shenanigans...
>
>It would be interesting to know if we have at least one real
>application running RTEMS on a 16-bit target. Apart from warning fixes
>I don't see any activity in this area.
The h8 port was user submitted and from a real application. The avr was a GSOC effort. The m32c is by me because it pushes odd size issues.
I don't want this to devolve before we branch but I have been making a list of targets and bsps to begin removing after 4.11. I want one last release with them all.
My plan is to announce a timeline from announcement of removal until removal, then go architecture by architecture and announce candidates to the list. Then after no response, remove them.
But we need to branch 4.11 first.
--joel
More information about the devel
mailing list