search for: clang

I think that debug info is slowing a self-hosting build down. This build has been going for ages now and shows no sign of quitting. To reproduce, build a Release+Asserts build of clang. Then use that to build a Debug+Asserts version. Include all of the bells and whistles, like the clang-extras and compiler-rt libraries. The reason I suspect debug info is because of this stack trace: [morbo:llvm] lldb -p 92084 Attaching to process with: process attach -p 92084 Process 92084...

...a bug. Thanks, Manman > On Nov 17, 2013, at 5:52 PM, Bill Wendling <isanbard at gmail.com> wrote: > > I think that debug info is slowing a self-hosting build down. This build has been going for ages now and shows no sign of quitting. To reproduce, build a Release+Asserts build of clang. Then use that to build a Debug+Asserts version. Include all of the bells and whistles, like the clang-extras and compiler-rt libraries. > > The reason I suspect debug info is because of this stack trace: > > [morbo:llvm] lldb -p 92084 > Attaching to process with: > process a...

I think it might be. I’m attaching a preprocessed file that can show the problem. Compile it with ToT. $ clang++ -g -fvisibility-inlines-hidden -fno-exceptions -fno-rtti -fno-common -Woverloaded-virtual -Wcast-qual -fno-strict-aliasing -m64 -pedantic -Wno-long-long -Wall -W -Wno-unused-parameter -Wwrite-strings -Wcovered-switch-default -Wno-uninitialized -Wno-missing-field-initializers -c LLVMTidyModule.i...

...voiding the need for a temporary std::vector on every lookup. Patch by Meador Inge! ------------------------------------------------------------------------ ... but I can't reproduce the failures on my machine. I'm also running x86_64 Linux, I've checked out the same revision of llvm+clang+testsuite as the buildbot, I'm doing a Release+Asserts build. Is anyone else seeing these failures? Any ideas how I can reproduce them here? Thanks, Jay. Example failure from http://lab.llvm.org:8011/builders/clang-x86_64-debian-fnt/builds/4877/steps/make.test-suite/logs/stdio : 0 clang...

hello everyone: On this boring weekend, I tried compile R-trunk on windows 11 arm64 using clangarm64+msys2 on macbook m1 , it surprisingly easy to compiled and run. more investigation and test and code modify need to be done ,but IMO this is a good beginning !! to compile R on windows 11 arm64 just need : 1 svn checkout R-trunk and add USE_LLVM=YES in MKRules.dist or Mkrules.local 2 instal...

...I will disable the debug info verifier until a correct fix is found. Thanks, Manman On Sun, Nov 17, 2013 at 6:04 PM, Bill Wendling <isanbard at gmail.com> wrote: > I think it might be. I’m attaching a preprocessed file that can show the > problem. Compile it with ToT. > > $ clang++ -g -fvisibility-inlines-hidden -fno-exceptions -fno-rtti > -fno-common -Woverloaded-virtual -Wcast-qual -fno-strict-aliasing -m64 > -pedantic -Wno-long-long -Wall -W -Wno-unused-parameter -Wwrite-strings > -Wcovered-switch-default -Wno-uninitialized > -Wno-missing-field-initializers...

> > ok, I now have a problem in the code generator. > > Let's say I want to set a breakpoint somewhere in > > clang/lib/CodeGen/CGExprScalar.cpp > > > > What do I have to do in order to trigger breakpoints, see > > backtraces and so on? > > You set a breakpoint and ask to see a backtrace? > > -eric haha, OK, I think I should be more specific. So, I configured the project with:...

Hi, Have anybody recently built LLVM in Debug mode /within/ space requirements from the Getting Started doc? https://llvm.org/docs/GettingStarted.html#hardware > An LLVM-only build will need about 1-3 GB of space. A full build of LLVM and Clang will need around 15-20 GB of disk space. From my experience this numbers looks drastically low. On FreeBSD my recent builds consumed more than 70 GB and on Linux - more than 60. I am building LLVM, Clang, and LLD with all default targets and default settings. On FreeBSD I am also building Poll...

...ady visited. -eric > Thanks, > Manman > > > > On Sun, Nov 17, 2013 at 6:04 PM, Bill Wendling <isanbard at gmail.com> wrote: >> >> I think it might be. I’m attaching a preprocessed file that can show the >> problem. Compile it with ToT. >> >> $ clang++ -g -fvisibility-inlines-hidden -fno-exceptions -fno-rtti >> -fno-common -Woverloaded-virtual -Wcast-qual -fno-strict-aliasing -m64 >> -pedantic -Wno-long-long -Wall -W -Wno-unused-parameter -Wwrite-strings >> -Wcovered-switch-default -Wno-uninitialized -Wno-missing-field-initia...

On Apr 23, 2012, at 2:14 PM, Roland Leißa <leissa at cs.uni-saarland.de> wrote: >>> ok, I now have a problem in the code generator. >>> Let's say I want to set a breakpoint somewhere in >>> clang/lib/CodeGen/CGExprScalar.cpp >>> >>> What do I have to do in order to trigger breakpoints, see >>> backtraces and so on? >> >> You set a breakpoint and ask to see a backtrace? >> >> -eric > > haha, OK, I think I should be more specific. &...

Hi Geoff, Nothing in that backtrace leaps out at me. Based on the stack trace and description my first guess would be a clang misconfiguration rather than a JIT bug. How is that clang invocation being made? Is it from inside a callback from ORC, or is it before you add your module to the JIT? -- Lang. On Mon, Aug 3, 2020 at 5:41 AM Geoff Levner <glevner at gmail.com> wrote: > Here, by the way, is the stack tr...

Hello everyone! After I've checked out Clang and Compiler-RT repositories, I receive this error during compilation: llvm[5]: Compiling PathDiagnostic.cpp for Debug+Asserts build /media/data/dev/llvm/llvm/tools/clang/lib/StaticAnalyzer/Core/PathDiagnostic.cpp: In member function 'bool {anonymous}::CompareDiagnostics::operator()(const clan...

llvm[1]: Compiling APFloat.cpp for Release+Asserts build clang: TargetInfo.cpp:1778: llvm::Type *GetX86_64ByValArgumentPair(llvm::Type *, llvm::Type *, const llvm::TargetData &): Assertion `Lo->isIntegerTy() && "Invalid/unknown lo type"' failed. 0 clang 0x0000000001c132ef 1 clang 0x0000000001c13804 2 libpthre...

Hello, After commit r114523, I start to get crash when compiling with clang (Release+Asserts) for i386: (I know I should fill a bug report instead of posting here, but I don't get much time right now). Trying to compile the following simple code, clang asserts. ---------- round.c -------- #include <math.h> float test() { return llround(1); } -------------------...

...> > > > > > > On Sun, Nov 17, 2013 at 6:04 PM, Bill Wendling <isanbard at gmail.com> > wrote: > >> > >> I think it might be. I’m attaching a preprocessed file that can show the > >> problem. Compile it with ToT. > >> > >> $ clang++ -g -fvisibility-inlines-hidden -fno-exceptions -fno-rtti > >> -fno-common -Woverloaded-virtual -Wcast-qual -fno-strict-aliasing -m64 > >> -pedantic -Wno-long-long -Wall -W -Wno-unused-parameter -Wwrite-strings > >> -Wcovered-switch-default -Wno-uninitialized > -Wno-...

...h problems. -- Roland ----- Original Message ----- > From: "Jim Grosbach" <grosbach at apple.com> > To: "Roland Leißa" <leissa at cs.uni-saarland.de> > Cc: LLVMdev at cs.uiuc.edu > Sent: Montag, 23. April 2012 14:45:42 > Subject: Re: [LLVMdev] gdb + clang/llvm > > > On Apr 23, 2012, at 2:14 PM, Roland Leißa <leissa at cs.uni-saarland.de> > wrote: > > >>> ok, I now have a problem in the code generator. > >>> Let's say I want to set a breakpoint somewhere in > >>> clang/lib/CodeGen/CGExpr...

Thanks for the suggestion. I tried your fix. It worked for my particular case, but then I got a following error: clang-3.5: /home/rail/projects/escala_llvm/trunk/llvm-or1k/lib/CodeGen/RegisterPressure.cpp:39: void decreaseSetPressure(std::vector<unsigned int>&, llvm::PSetIterator): Assertion `CurrSetPressure[*PSetI] >= Weight && "register pressure underflow"' failed. Do you mind...

...rrayRef<llvm::OperandBundleDefT<llvm::Value*> >, const llvm::Twine&): Assertion `(i > = FTy->getNumParams() || FTy->getParamType(i) == Args[i]->getType()) && "Calling a function with a bad signature!"' failed. The same code compiles correctly using clang from the command line. It also works fine using Orc v2 in the master branch of LLVM from the end of May. The problems are way too deep in the LLVM code for me to make any sense of them... Does anybody else have a clue what might have happened to Orc and/or OpenMP in the past couple months to trigg...

Hi, all, I am planning to add clang-tidy checkers for my company. How to add a new module for my company? Please help, thanks in advance. I try to copy files from cert module, and rename cert to Misra, then add a rule named "m-0-1-1" by ./add_new_checker.py. then I run ninja check-clang-tool, but my case is failed due t...

...:vector on every lookup. > > Patch by Meador Inge! > > ------------------------------------------------------------------------ > > ... but I can't reproduce the failures on my machine. I'm also running > x86_64 Linux, I've checked out the same revision of > llvm+clang+testsuite as the buildbot, I'm doing a Release+Asserts > build. > > Is anyone else seeing these failures? Any ideas how I can reproduce them > here? > If the hashing is the culprit, there are many more variables to consider: different pointer values entering the hash can cause d...