RTEMS | Draft: Support for building RTEMS with LLVM toolchains (!1539)

[Sebastian Huber (@sebhub)]

Sebastian Huber started a new discussion on cpukit/libtest/llvmcovdumpinfo.c: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1539#note_161197

 > + * CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
 > + * ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
 > + * POSSIBILITY OF SUCH DAMAGE.
 > + */
 > +
 > +#ifdef HAVE_CONFIG_H
 > +#include "config.h"
 > +#endif
 > +
 > +#include <stdint.h>
 > +#include <stddef.h>
 > +#include <rtems/test-cov.h>
 > +
 > +/*
 > + * Data structures below (ProfDataIoVec, ProfDataWriter), WriterCallback
 > + * and lprofWriteData functions are copied from LLVM sources

The comment states that these declarations are copied from `InstrProfilingInternal.h` of compiler-rt. compiler-rt is licensed under Apache-2.0 WITH LLVM-exception. The file declares only BSD-2-Clause. New code in cpukit must be BSD-2-Clause. Please write these declarations from the documented interface, or tell us which part needs the LLVM license.

`lprofWriteData()` and `ProfDataIOVec` are internal to compiler-rt. LLVM gives no stability promise for them. Which LLVM versions did you test? Please state the supported range in the file.

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1539#note_161197
You're receiving this email because of your account on gitlab.rtems.org. Unsubscribe from this thread: https://gitlab.rtems.org/-/namespace/49/sent_notifications/6-ac4ou0me2r1uk6sds5a9y5jgo-1d/unsubscribe | Manage all notifications: https://gitlab.rtems.org/-/profile/notifications | Help: https://gitlab.rtems.org/help


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20261016/be0f1bb6/attachment-0001.htm>