Displaying 20 results from an estimated 20000 matches similar to: "Windows/Clang build instrumented/PGO"
2017 Oct 15
2
darwin bootstrap failure
On Sat, Oct 14, 2017 at 11:25 AM, Don Hinton via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
> Hi Jack:
>
> Yes, I was just looking at that. Seems like TableGen wasn't done along with
> the rest of llvm. I'll work up a complete patch shortly.
This also broke the build for MSVC when doing a debug build (though no
builder seems to be picking up the failure!). After
2017 Oct 15
2
darwin bootstrap failure
On Sun, Oct 15, 2017 at 10:58 AM, Don Hinton <hintonda at gmail.com> wrote:
> Thanks Aaron.
>
> I don't have a Windows system, and haven't seen any buildbot failures, so I
> it's difficult to come up with a patch for something I can't reproduce
> locally or see any actual failures. Could you send me the commands you used
> that uncovered the failure?
This
2017 Oct 15
2
darwin bootstrap failure
On Sun, Oct 15, 2017 at 11:19 AM, Don Hinton <hintonda at gmail.com> wrote:
> On Sun, Oct 15, 2017 at 8:06 AM, Aaron Ballman <aaron at aaronballman.com>
> wrote:
>>
>> On Sun, Oct 15, 2017 at 10:58 AM, Don Hinton <hintonda at gmail.com> wrote:
>> > Thanks Aaron.
>> >
>> > I don't have a Windows system, and haven't seen any
2017 Oct 14
3
darwin bootstrap failure
On Sat, Oct 14, 2017 at 10:25 AM, Don Hinton <hintonda at gmail.com> wrote:
> Hi Jack:
>
> Looks like I missed this one in my recent change.
>
> Please let me know if this solves your problem:
>
> $ git diff
> diff --git a/utils/TableGen/InfoByHwMode.cpp
> b/utils/TableGen/InfoByHwMode.cpp
> index 7e1e1864356..8d3636432aa 100644
> ---
2017 Oct 14
2
darwin bootstrap failure
On Sat, Oct 14, 2017 at 11:25 AM, Don Hinton <hintonda at gmail.com> wrote:
> Hi Jack:
>
> Yes, I was just looking at that. Seems like TableGen wasn't done along
> with the rest of llvm. I'll work up a complete patch shortly.
>
> Btw, I'm curious how this happened. Do you have a stale CMakeCache.txt by
> any chance? You might check the value for
2017 Oct 14
2
darwin bootstrap failure
On Sat, Oct 14, 2017 at 11:38 AM, Don Hinton <hintonda at gmail.com> wrote:
> Sorry, LLVM_FORCE_ENABLE_DUMP is the variable, which is used along with
> LLVM_ENABLE_ASSERTIONS to set LLVM_ENABLE_DUMP.
>
> Again, I'm working on a fix, but could you also provide your cmake
> command? Looks like we aren't handling your use case correctly.
>
> thanks..
> don
>
2017 Oct 15
2
darwin bootstrap failure
On Sun, Oct 15, 2017 at 12:40 PM, Don Hinton <hintonda at gmail.com> wrote:
> On Sun, Oct 15, 2017 at 8:34 AM, Aaron Ballman <aaron at aaronballman.com>
> wrote:
>>
>> FWIW, most of the ones I was fixing up were guarded by NDEBUG instead
>> of LLVM_ENABLE_DUMP. Switching to LLVM_ENABLE_DUMP fixed the link
>> errors for me -- the only one I struggled with
2017 Oct 14
2
darwin bootstrap failure
On Sat, Oct 14, 2017 at 4:22 PM, Don Hinton <hintonda at gmail.com> wrote:
> Hi Jack:
>
> The only way I could reproduce the problem you are seeing was to rerun
> cmake with -DCMAKE_BUILD_TYPE=Debug in a build directory previously
> configured with -DCMAKE_BUILD_TYPE=Release. I can fix that, but not sure
> if it's what you are seeing.
>
> If this isn't your
2017 Oct 14
2
darwin bootstrap failure
Is anyone else seeing this bootstrap failure on current svn trunk?
[ 6%] Linking CXX executable ../../bin/llvm-tblgen
cd /sw/src/fink.build/llvm60-6.0.0-1/build/stage1/utils/TableGen &&
/sw/bin/cmake -E cmake_link_script CMakeFiles/llvm-tblgen.dir/link.txt
--verbose=1
/sw/src/fink.build/llvm60-6.0.0-1/opt-bin/ccclang++ -fno-common -fPIC
-fvisibility-inlines-hidden -Werror=date-time
2016 Mar 18
2
Building with LLVM_PARALLEL_XXX_JOBS
On Thu, Mar 17, 2016 at 11:45 AM, Sedat Dilek <sedat.dilek at gmail.com> wrote:
> On Thu, Mar 17, 2016 at 10:05 AM, Sedat Dilek <sedat.dilek at gmail.com> wrote:
>> On Mon, Mar 14, 2016 at 5:30 PM, Chris Bieneman <cbieneman at apple.com> wrote:
>> [ brutal-snip ]
>> ...
>>> [ TODO#S: Before doing a 2nd build (and in a 3rd run using more
>>>
2014 Feb 27
3
[LLVMdev] Understanding some of the recent cmake build changes
I was a bit confused with what the difference was between the old
target_link_libraries(foo bar)
and the new
target_link_libraries(foo INTERFACE|PRIVATE|PUBLIC bar)
To try to find out, I decided to look at the generated build.ninja.
The difference that shows up is far fewer order only dependencies. For
example
build lib/TableGen/CMakeFiles/LLVMTableGen.dir/Error.cpp.o:
CXX_COMPILER
2016 Feb 17
2
Error cross building LLVM for MinGW
Hi,
I recently switched over to using cmake to build my clang/LLVM based
ELLCC cross development project (http://ellcc.org). I also recently
updated to LLVM svn version 258915 from 258477.
I use ELLCC to cross compile all the tools for various Linux targets and
for Windows. Yesterday, after updating the LLVM sources, I got the
following error when cross building for MinGW:
[ 3%] Built
2020 Apr 23
3
Cannot build master
I am nuilding that now.
CC=clang CXX=clang++ cmake -DCMAKE_INSTALL_PREFIX=$HOME/opt/llvm11-git \
-DCMAKE_BUILD_TYPE=Release \
-DBUILD_SHARED_LIBS=ON \
-DLLVM_ENABLE_EH=ON \
-DLLVM_ENABLE_RTTI=ON \
-DLLVM_HOST_TRIPLE=x86_64-pc-linux-gnu \
-DLLVM_TARGETS_TO_BUILD="AMDGPU;MSP430;WebAssembly;X86" \
2009 May 22
0
[LLVMdev] CMake build maturity [was: Re: Arm port]
Hi, just chiming in here...
Óscar Fuentes wrote:
> [...]
>
> This is a simple guide for using cmake with LLVM:
>
> http://www.llvm.org/docs/CMake.html
>
> The makefiles distributed with LLVM have nothing to do with cmake.
>From the few times I tried building LLVM with CMake I got the impression
that it wasn't completely mature yet (the "TODO" sections in
2012 Jan 26
2
[LLVMdev] HELP - tblgen -gen-asm-matcher restrictions on .td content
I'm trying to generate MipsGenAsmMatcher.inc for MipsAsmParser.cpp.
What added restrictions for the .td file contents are there for tblgen -gen-asm-matcher?
For the Mips platform we create the following .inc files through tblgen.
tablegen(LLVM MipsGenRegisterInfo.inc -gen-register-info)
tablegen(LLVM MipsGenInstrInfo.inc -gen-instr-info)
tablegen(LLVM MipsGenCodeEmitter.inc -gen-emitter)
2020 Apr 23
2
Cannot build master
Do you really need to build the C library for MLIR?
If so, it looks like it's just a missing dependency - MPFR library. Or if
you do have that library available, it's missing expected features.
On Thu, Apr 23, 2020 at 12:29 PM Luke A. Guest via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> Here's the error:
>
> [1921/7570] /usr/lib/llvm/10/bin/clang++
2004 Oct 23
2
[LLVMdev] Link error with TOOLLINKOPTS=-ldbghelp on MinGW
Hi LLVM'ers
When linking tblgen tool I get below error message on MinGW.
I have put TOOLLINKOPTS=-ldbghelp in Makefile.config.
However, when rearranging library dbghelp to the end of the g++
line, tblgen gets linked.
--------------------------
make[2]: Entering directory `/C/Projects/build/MinGW/llvm/utils/TableGen'
Linking Debug executable tblgen
/C/Projects/build/MinGW/llvm/mklib
2012 Feb 03
0
[LLVMdev] HELP - tblgen -gen-asm-matcher restrictions on .td content
Hi Jack,
On Jan 25, 2012, at 6:45 PM, "Carter, Jack" <jcarter at mips.com> wrote:
> I'm trying to generate MipsGenAsmMatcher.inc for MipsAsmParser.cpp.
>
> What added restrictions for the .td file contents are there for tblgen -gen-asm-matcher?
>
Lots, as you're finding, almost all of them completely undocumented. :(
> For the Mips platform we create
2013 Apr 23
4
[LLVMdev] [PATCH] Handle tied sub-operands in AsmMatcherEmitter
Hi Ulrich,
Thank you for looking at this. Apologies again for taking unjustifiably long to get back to you. This is really good stuff and I very much want to see this go in. I like it enough I’m going to try to talk you into doing even more work on improving this code. ;)
Fair warning up front: You’re digging into some pretty fundamental problems in how the assemblers and code generators like to
2013 Apr 24
0
[LLVMdev] [PATCH] Handle tied sub-operands in AsmMatcherEmitter
Hi Jim,
> Thank you for looking at this. Apologies again for taking
> unjustifiably long to get back to you. This is really good stuff and
> I very much want to see this go in. I like it enough I’m going to
> try to talk you into doing even more work on improving this code. ;)
>
> Fair warning up front: You’re digging into some pretty fundamental
> problems in how the