New targets for esp32s2 and esp32s3 #46

Activity

1. ivmarkov commented on Apr 5, 2021

   

   ivmarkov

   on Apr 5, 2021

   Last edited by ivmarkov

   Author

   More actions

   ... and while we are at it, how about putting some extra info in the targets, like unix, vendor = espressif and env = newlib. Mentioned here.

   For those who have no interest in using this with the ESP-IDF SDK, these would do no harm, as they won't be trying to build the STD crates anyway. However, for me this extra info is very beneficial, as most of my patches against STD are checking for generic stuff, like cfg(unix) and target_env = newlib. A few also check for target_os = none and target_vendor = espressif.
2. MabezDev commented on Apr 15, 2021

   

   MabezDev

   on Apr 15, 2021

   Member

   More actions

   Hi @ivmarkov,

   I've just updated the fork to 1.51, with a target def for the esp32s2, it seems esp32s3 support has not yet landed in llvm.

   Also: shall we create a target for esp32c3?

   I'm not yet convinced this is necessary, and I think we should try and lean on upstream support where we can until we really need custom definitions.

   As for the custom defs for libstd porting, I'm not apposed to them haven't really looked into the libstd porting effort enough yet.
3. ivmarkov commented on Jul 22, 2021

   

   ivmarkov

   on Jul 22, 2021

   Author

   More actions

   Closing as the esp32s2 target is there, and the ESP-IDF-specific targets for Xtensa & RiscV are part of the libstd pull request.
4. ivmarkov

   closed this as completedon Jul 22, 2021