I'm working on lldb. I've just submitted a very small change (r217229) to Triple.h/.cpp. Soon after I get a mail subject: buildbot failure in LLVM on lld-x86_64-darwin13 Details: http://lab.llvm.org:8011/builders/lld-x86_64-darwin13/builds/2571 Blamelist: mg11 My small change certainly did not cause lldb's build to fail on my machine. I looked into the build-log: http://lab.llvm.org:8011/builders/lld-x86_64-darwin13/builds/2571/steps/build_Lld/logs/stdio It wasn't obvious how my change resulted in failure. When I tried to replicate the build of the last 2 targets listed in the log, I did see this, on my machine: $ ninja LLVMCodeGen [15/15] Linking CXX shared library lib/libLLVMCodeGen.so $ ninja LLVMMipsCodeGen ninja: error: unknown target 'LLVMMipsCodeGen' Can anyone help? thanks Matt Member of the CSR plc group of companies. CSR plc registered in England and Wales, registered number 4187346, registered office Churchill House, Cambridge Business Park, Cowley Road, Cambridge, CB4 0WZ, United Kingdom More information can be found at www.csr.com. Keep up to date with CSR on our technical blog, www.csr.com/blog, CSR people blog, www.csr.com/people, YouTube, www.youtube.com/user/CSRplc, Facebook, www.facebook.com/pages/CSR/191038434253534, or follow us on Twitter at www.twitter.com/CSR_plc. New for 2014, you can now access the wide range of products powered by aptX at www.aptx.com.
Hi Matthew,> My small change certainly did not cause lldb's build to fail on my machine. > I looked into the build-log:It's probably just lld building with -Werror (and likely on a different compiler than you too, or you'd have seen the warning). I've fixed this one up in r217233, we'll see what that does to the lld builder.> When I tried to replicate the build of the last 2 targets listed in the log, > I did see this, on my machine:That's usually not particularly useful even if there are targets for them. The builds are very parallel and it's difficult to work out just which target actually caused the problem "ninja check-all" should be fine for most cases. Cheers. Tim.
Hi,
The build log show this error:
/Users/buildslave/as-bldslv9/lld-x86_64-darwin13/llvm.src/lib/Target/ARM/MCTargetDesc/ARMMCTargetDesc.cpp:92:11:
error: enumeration values 'KalimbaSubArch_v3',
'KalimbaSubArch_v4', and 'KalimbaSubArch_v5' not handled in
switch [-Werror,-Wswitch]
switch (triple.getSubArch()) {
This is a warning turned into an error by -Werror. LLVM’s code should be warning
free.
You indeed added these entries to the enum and they seem not to be handled in
ARMMCTargetDesc.cpp. If you don’t know how to add these to ParseARMTriple(), I’d
suggest you revert your change until someone with ARM MC knowledge helps you
out.
Fred
> On 05 Sep 2014, at 09:43, Matthew Gardiner <mg11 at csr.com> wrote:
>
> I'm working on lldb.
>
> I've just submitted a very small change (r217229) to Triple.h/.cpp.
Soon after I get a mail
>
> subject: buildbot failure in LLVM on lld-x86_64-darwin13
> Details:
> http://lab.llvm.org:8011/builders/lld-x86_64-darwin13/builds/2571
> Blamelist: mg11
>
> My small change certainly did not cause lldb's build to fail on my
machine. I looked into the build-log:
>
>
http://lab.llvm.org:8011/builders/lld-x86_64-darwin13/builds/2571/steps/build_Lld/logs/stdio
>
> It wasn't obvious how my change resulted in failure.
>
> When I tried to replicate the build of the last 2 targets listed in the
log, I did see this, on my machine:
>
> $ ninja LLVMCodeGen
> [15/15] Linking CXX shared library lib/libLLVMCodeGen.so
>
> $ ninja LLVMMipsCodeGen
> ninja: error: unknown target 'LLVMMipsCodeGen'
>
> Can anyone help?
>
> thanks
> Matt
>
>
>
> Member of the CSR plc group of companies. CSR plc registered in England and
Wales, registered number 4187346, registered office Churchill House, Cambridge
Business Park, Cowley Road, Cambridge, CB4 0WZ, United Kingdom
> More information can be found at www.csr.com. Keep up to date with CSR on
our technical blog, www.csr.com/blog, CSR people blog, www.csr.com/people,
YouTube, www.youtube.com/user/CSRplc, Facebook,
www.facebook.com/pages/CSR/191038434253534, or follow us on Twitter at
www.twitter.com/CSR_plc.
> New for 2014, you can now access the wide range of products powered by aptX
at www.aptx.com.
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20140905/e00aa031/attachment.html>
Hi Tim, Thanks for helping me with this. The route which I take to build lldb (cmake/ninja on Fedora) seems (irritating) permissive of warnings. So I missed this when I originally submitted my change. I'll certainly bear this in mind if I make any more llvm changes! thanks Matt Tim Northover wrote:> Hi Matthew, > >> My small change certainly did not cause lldb's build to fail on my machine. >> I looked into the build-log: > It's probably just lld building with -Werror (and likely on a > different compiler than you too, or you'd have seen the warning). I've > fixed this one up in r217233, we'll see what that does to the lld > builder. > >> When I tried to replicate the build of the last 2 targets listed in the log, >> I did see this, on my machine: > That's usually not particularly useful even if there are targets for > them. The builds are very parallel and it's difficult to work out just > which target actually caused the problem "ninja check-all" should be > fine for most cases. > > Cheers. > > Tim. > > > To report this email as spam click https://www.mailcontrol.com/sr/MZbqvYs5QwJvpeaetUwhCQ== .Member of the CSR plc group of companies. CSR plc registered in England and Wales, registered number 4187346, registered office Churchill House, Cambridge Business Park, Cowley Road, Cambridge, CB4 0WZ, United Kingdom More information can be found at www.csr.com. Keep up to date with CSR on our technical blog, www.csr.com/blog, CSR people blog, www.csr.com/people, YouTube, www.youtube.com/user/CSRplc, Facebook, www.facebook.com/pages/CSR/191038434253534, or follow us on Twitter at www.twitter.com/CSR_plc. New for 2014, you can now access the wide range of products powered by aptX at www.aptx.com.
Hi Fred,
Thanks. How did you get to
"
The build log show this error:
/Users/buildslave/as-bldslv9/lld-x86_64-darwin13/llvm.src/lib/Target/ARM/MCTargetDesc/ARMMCTargetDesc.cpp:92:11:
error: enumeration values 'KalimbaSubArch_v3',
'KalimbaSubArch_v4', and 'KalimbaSubArch_v5' not handled in
switch [-Werror,-Wswitch]
switch (triple.getSubArch()) {
"
from here
http://lab.llvm.org:8011/builders/lld-x86_64-darwin13/builds/2571
Sorry to seem lame, but I could have fixed it myself if I'd known how to
navigate to that line describing the failed invocation.
thanks
Matt
Frédéric Riss wrote:> Hi,
>
> The build log show this error:
>
/Users/buildslave/as-bldslv9/lld-x86_64-darwin13/llvm.src/lib/Target/ARM/MCTargetDesc/ARMMCTargetDesc.cpp:92:11:
error: enumeration values 'KalimbaSubArch_v3',
'KalimbaSubArch_v4', and 'KalimbaSubArch_v5' not handled in
switch [-Werror,-Wswitch]
> switch (triple.getSubArch()) {
> This is a warning turned into an error by -Werror. LLVM’s code should
> be warning free.
> You indeed added these entries to the enum and they seem not to be
> handled in ARMMCTargetDesc.cpp. If you don’t know how to add these
> to ParseARMTriple(), I’d suggest you revert your change until someone
> with ARM MC knowledge helps you out.
>
> Fred
>
>> On 05 Sep 2014, at 09:43, Matthew Gardiner <mg11 at csr.com
>> <mailto:mg11 at csr.com>> wrote:
>>
>> I'm working on lldb.
>>
>> I've just submitted a very small change (r217229) to Triple.h/.cpp.
>> Soon after I get a mail
>>
>> subject: buildbot failure in LLVM on lld-x86_64-darwin13
>> Details:
>> http://lab.llvm.org:8011/builders/lld-x86_64-darwin13/builds/2571
>> Blamelist: mg11
>>
>> My small change certainly did not cause lldb's build to fail on my
>> machine. I looked into the build-log:
>>
>>
http://lab.llvm.org:8011/builders/lld-x86_64-darwin13/builds/2571/steps/build_Lld/logs/stdio
>>
>> It wasn't obvious how my change resulted in failure.
>>
>> When I tried to replicate the build of the last 2 targets listed in
>> the log, I did see this, on my machine:
>>
>> $ ninja LLVMCodeGen
>> [15/15] Linking CXX shared library lib/libLLVMCodeGen.so
>>
>> $ ninja LLVMMipsCodeGen
>> ninja: error: unknown target 'LLVMMipsCodeGen'
>>
>> Can anyone help?
>>
>> thanks
>> Matt
>>
>>
>>
>> Member of the CSR plc group of companies. CSR plc registered in
>> England and Wales, registered number 4187346, registered office
>> Churchill House, Cambridge Business Park, Cowley Road, Cambridge, CB4
>> 0WZ, United Kingdom
>> More information can be found at www.csr.com. Keep up to date with
>> CSR on our technical blog, www.csr.com/blog, CSR people blog,
>> www.csr.com/people, YouTube, www.youtube.com/user/CSRplc, Facebook,
>> www.facebook.com/pages/CSR/191038434253534, or follow us on Twitter
>> at www.twitter.com/CSR_plc.
>> New for 2014, you can now access the wide range of products powered
>> by aptX at www.aptx.com.
>> _______________________________________________
>> LLVM Developers mailing list
>> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu
>> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>
>
>
> To report this email as spam click here
>
<https://www.mailcontrol.com/sr/qJwgJIkMzpPGX2PQPOmvUvmldA89nuwlzjNwjKOfNSUqPMhWpN7KRjNOsc4jssjX3sDihM%213k4pkxH4nYzTQYQ==>.
>
Possibly Parallel Threads
- [LLVMdev] HELP! Recent failure on llvm buildbot
- [LLVMdev] [PATCH][REQUEST] Could someone submit this CSR Kalimba definitions patch please?
- [LLVMdev] Machine Code for different architectures
- [LLVMdev] Machine Code for different architectures
- [LLVMdev] Machine Code for different architectures