search for: jodin

...ThinLTO link, the linker does not see any uses of your > alternate memset and it is therefore removed as dead code. Have you tried > marking it with __attribute__((used))? Another thing that might work is to > mark it weak. > > Teresa > > On Fri, Aug 28, 2020 at 8:26 AM Romaric Jodin via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> Hi everyone, >> >> I have 2 implementations of "memset". A standard one, and another one >> optimized when the pointer and the size respect some specific constraints. >> I am able to choose...

...looked into theLTO archive used and I found both memset functions. It feels like when the compiler gets in "EmitTargetCodeForMemSet", it has already forgotten about the optimized memset function that was in the archive because it was not used initially. Any idea why? Thanks in advance, JODIN Romaric -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200828/adaaafa8/attachment.html>

Hi all, I'm working in a company to port LLVM on their own processor. I'm trying to run the test-suite, but it seems that it is usually run directly on the processor which is tested. In my case, I cannot run it on the processor, but I have a simulator on which I would like to run the test-suite. Also, it seems to me that the test-suite start by compiling some tools that have to be run

Hi everyone, I'm working in a company to port LLVM on their own processors. I'm try to support several set of instructions and several architectures. I'm using the "--target" options to choose my set of instructions, and I would like to use the "-mcpu" to choose the architecture of which I want to compile the code. Does it seem right? But at the moment I cannot

Hi, I have an issue with some builtins that are reordered (during instructions selection it seems) with others instructions and/or others builtins. Is it normal? How could I prevent it from happening? Thanks, Romaric

Hi, I'm working on OpenCL and I'm using clang as compiler (based on clang 3.7.0). I have a issue, I'm generating a bitcode file (that I can print before before the generation). But when I'm trying to read it again with clang, I have this issue: "error: Invalid record" How can I managed to know where it comes from? Thank you, Romaric Here is what is print before the