search for: teleman

...or the Solaris linker only (/usr/bin/ld). It looks like /project/helder/scratch/packages2/bin/ld is actually the GNU linker, and it doesn't understand -C. I'll file the bug about the endian stuff, but we'll also have to have an <endian.h> in Solaris as well. --Stefan -- Stefan Teleman KDE e.V. stefan.teleman at gmail.com

On Fri, Jul 8, 2016 at 4:52 AM, Stefan Teleman via llvm-dev < llvm-dev at lists.llvm.org> wrote: > On Thu, Jul 7, 2016 at 1:36 PM, Oscar Guido via llvm-dev > <llvm-dev at lists.llvm.org> wrote: > > Hello, > > I get the following error while trying to configure an llvm build on > > Solaris 10-SPARC: >...

...e not only required, but also in everyone's best interests (not just our own). i'm waiting for legal approvals at this point, and i don't have a better solution handy at the moment. The only thing i can offer is "stay tuned, we're working on it". :-) --Stefan -- Stefan Teleman KDE e.V. stefan.teleman at gmail.com

On Mon, Nov 18, 2019 at 11:55 AM David Chisnall via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > On 18/11/2019 16:39, Stefan Teleman via llvm-dev wrote: > > I can't recall an instance when I had difficulty using, or was > > intimidated by, email, for saying something on a mailing list. > > Subscribing to a mailing list, particularly one as high-traffic as > LLVM-Dev, is a high friction activity. I was c...

Is there anything I can do regarding the linker issue? The solaris linker is in /usr/ccs/bin/ld but I think llvm wants to use the gnu linker. gcc in my system was compiled with the solaris linker. Thanks, Jorge On Mon, Jun 24, 2013 at 6:18 PM, Stefan Teleman <stefan.teleman at gmail.com>wrote: > On Mon, Jun 24, 2013 at 6:17 PM, Jorge Rodrigues <skeept at gmail.com> wrote: > > Norm, > > > > thanks for the help. Applying the fix solves the issue I mentioned but > now I > > have more issues. > > > >...

...aying something on a mailing list. I am very unclear as to what problem this Discourse thing is supposed to solve. Being welcoming, or off-putting, has nothing to do with the form of the communications medium IMO. It has much more to do with the contents and style of the communication. -- Stefan Teleman stefan.teleman at gmail.com

Hello,    I get the following error while trying to configure an llvm build on Solaris 10-SPARC: CMake Error at projects/libcxx/CMakeLists.txt:268 (message):   C++11 is required but the compiler does not support -std=c++11 However, the error is about a missing header file (llvm/Support/Solaris.h) as reported in build/CMakeFiles/CMakeError.log: Performing C++ SOURCE FILE Test

...eduler > will assert if it ever sees that instruction. > > ​The scheduler does not assert if it sees LDADDAL, or any other of the LSE instructions on ThunderX2. We've been generating LSE code for months now, with LLVM built in debug+assert+expensive-checks mode. --Stefan​ -- Stefan Teleman stefan.teleman at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20170929/f99a1ed6/attachment.html>

On Jun 24, 2013, at 4:18 PM, Stefan Teleman <stefan.teleman at gmail.com> wrote: > I'll file the bug about the endian stuff, but we'll also have to have > an <endian.h> in Solaris as well. Do you still have issues after r182419? commit 01ef4f6982451e6a7c00a713d9ae677d3a15d042 Author: Jakob Stoklund Olesen <sto...

> On Sep 22, 2017, at 10:34 AM, Thorsten Schütt via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Hi all, > > I am looking at the scheduling model of the ThunderX2. I am trying to figure out the cost of the LDADDALX instruction. The following program’s output is: > name LDADDALX; class 872 > microops 65535 > I would have assumed that the microops are less than

...and creating mapped segments ranges. Lather, rinse, repeat until all the addressable segments are mapped in msan.h. But I was wondering if there isn't a more efficient way of accomplishing this mapping. Any help/suggestions/ideas will be greatly appreciated. Thank you. --Stefan -- Stefan Teleman stefan.teleman at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180404/32f07818/attachment.html>

Norm, thanks for the help. Applying the fix solves the issue I mentioned but now I have more issues. I can install clang, but when running I cannot compile and link files. If I compile with -c flag it works but compiling the following x.c file gives an error: x.c: int main(void) { return 0; } > ./clang x.c /project/helder/scratch/packages2/bin/ld: unrecognized option '-C'

Hi all, I am looking at the scheduling model of the ThunderX2. I am trying to figure out the cost of the LDADDALX instruction. The following program’s output is: name LDADDALX; class 872 microops 65535 I would have assumed that the microops are less than 20. The ThunderX2 has a detailed cost model for LSE. Could somebody tell me what I am doing wrong? Cheers, Tom #define GET_REGINFO_ENUM

I run configure in a build folder using CC=gcc CXX=g++ ../configure --prefix=/project/scratch/packages2/clang \ --enable-targets=host --enable-shared The configure runs fine but when I type make I get the error: make[1]: Entering directory `/project/scratch/tmp/llvm-3.3/build/lib/Support' llvm[1]: Compiling APFloat.cpp for Release+Asserts build In file included from

FWIW, the talks linked by Mehdi really do talk about these things and why I don't think the really are the correct trade-off. Even if you imagine an unsigned type that doesn't allow wrapping, I think this is a really bad type. The problem is that you have made the most common value of the type (zero in every study I'm aware of) be a boundary condition. Today, it wraps to a huge value

Hello everyone, *Short version:*I've set up an LLVM Discord server for real time chat (similar to IRC) and an LLVM Discourse server for forums (similar to email lists): https://discord.gg/xS7Z362 https://llvm.discourse.group/ Please join and use these new services. They are only partially set up and still very new, so don't hesitate to improve them and/or reach out to this thread with