Where are the default archs defined? I’m not seeing it, looking through 
testcases/dotest.py.

 

--

Qualcomm Innovation Center, Inc.

The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux 
Foundation Collaborative Project

 

From: Zachary Turner [mailto:ztur...@google.com] 
Sent: Wednesday, January 20, 2016 11:55 AM
To: Ted Woodward; LLDB
Subject: Re: [lldb-dev] Getting lldb tests working on Hexagon

 

If it should never run with x86_64 on Hexagon, then don't bother using command 
lines, just change dotest.py so that when the target is hexagon, the default 
archs doesn't include x86_64

 

On Wed, Jan 20, 2016 at 9:48 AM Ted Woodward via lldb-dev 
<lldb-dev@lists.llvm.org <mailto:lldb-dev@lists.llvm.org> > wrote:

I’m trying to get the lldb tests running using lldb built with Hexagon support. 
Some tests are running correctly, but others are failing/skipped etc. 

 

First, I’d like to get it to skip tests that shouldn’t be run. For example, I 
see output that looks like this:

Configuration: arch=x86_64 
compiler=/prj/dsp/qdsp6/release/internal/branch-8.0/linux64/latest/Tools/bin/hexagon-clang

 

Or

 

Config=x86_64-/prj/dsp/qdsp6/release/internal/branch-8.0/linux64/latest/Tools/bin/hexagon-clang

 

Those are clearly incorrect. 

 

My dotest line is:

python dotest.py -C 
/prj/dsp/qdsp6/release/internal/branch-8.0/linux64/latest/Tools/bin/hexagon-clang
 --executable /local/mnt/workspace/ted/8.0/build/bin/lldb

 

How does the –A flag affect the Configuration/Config outputs above?

 

Ted

 

--

Qualcomm Innovation Center, Inc.

The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux 
Foundation Collaborative Project

 

_______________________________________________
lldb-dev mailing list
lldb-dev@lists.llvm.org <mailto:lldb-dev@lists.llvm.org> 
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

_______________________________________________
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Reply via email to