similar to: [LLVMdev] [PATCH] Fix for bugpoint -remote-client

Hello Evan, Thanks for looking at the patch. > This should use std::cerr and make sure it is wrapped inside the DEBUG > macro. Will do. > Also, we don't want RemoteRunSafely.sh to be under utils/bugpoint. > Can you move it to test-suite? Are you planning to change the llvm > test suite makefile to make use of RemoteRunSafely.sh? I thought about bugpoint remote mode

> bugpoint should be a standalone tool. It should not require a separate > script to handle remote execution. Why is the script needed? Bugpoint is a standalone too and does not require any separate script. The script is a helper for using ssh as a remote client. Bugpoint should not be aware of any details how the test program will be delivered to a remote target, get executed there, and

On Jul 8, 2009, at 1:52 PM, Viktor Kutuzov wrote: >> bugpoint should be a standalone tool. It should not require a >> separate >> script to handle remote execution. Why is the script needed? > > Bugpoint is a standalone too and does not require any separate script. > The script is a helper for using ssh as a remote client. Ok. > > Bugpoint should not be aware

Thanks Viktor. + std::cout << "<run locally>" << std::flush; This should use std::cerr and make sure it is wrapped inside the DEBUG macro. Also, we don't want RemoteRunSafely.sh to be under utils/bugpoint. Can you move it to test-suite? Are you planning to change the llvm test suite makefile to make use of RemoteRunSafely.sh? Thanks, Evan On Jul 7,

On Jul 8, 2009, at 12:42 AM, Viktor Kutuzov wrote: > Hello Evan, > > Thanks for looking at the patch. > >> This should use std::cerr and make sure it is wrapped inside the >> DEBUG >> macro. > > Will do. > >> Also, we don't want RemoteRunSafely.sh to be under utils/bugpoint. >> Can you move it to test-suite? Are you planning to change the

Hi Viktor, I did not see your patches, can you send them again. Here are the changes that I have made that seem to get remote execution working for bugpoint. I have not yet changed the test system to provide -remote- client and -remote-port. David -------------- next part -------------- A non-text attachment was scrubbed... Name: patch2 Type: application/octet-stream Size: 1906 bytes Desc:

I just checked in my changes to bugpoint and Makefile.programs in the test suite. These changes shouldn't conflict with yours. revision 75292 revision 75293 bugpoint now works for remote ARM if you run it directly from the command line. It doesn't work correctly when invoked from the test makefile because envvar PWD is being set to /bin/pwd and so causing GCC::ExecuteProgram to

David, Please find attached 2 diffs. Please notice that RemoteRunSafely.sh may get moved to the test suite sub-tree. We have targeted different areas fso far which is great. What's your plan? I have been thinking of using -run-custom and -safe-run-custom argumants for the cross-tools to keep bugpoint out of knowing any target details ans such. Best regards, Viktor ----- Original Message

> I will investigate. I'm in the middle of it as well. Best regards, Viktor ----- Original Message ----- From: "David Goodwin" <david_goodwin at apple.com> To: "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu> Sent: Friday, July 10, 2009 2:43 PM Subject: Re: [LLVMdev] Heads up! Working on bugpoint >I just checked in my changes to bugpoint and

Hello everyone, The bugpoint is changed to escalate remote client return status 255 (per discussion - Re: [llvm-commits] [llvm] r75665 - /llvm/trunk/tools/bugpoint/ToolRunner.cpp) Please find the patch attached. -Viktor -------------- next part -------------- A non-text attachment was scrubbed... Name: ToolRunner.diff Type: application/octet-stream Size: 4710 bytes Desc: not available URL:

I'm starting work on getting bugpoint working with remote execution for arm. Is anyone else working on this? David

Hello David, I'm working on bugpoint. There are 2 patched out there for review that fix problems and make remote execution work. I'm looking at adding it to the test-suit and use make to run tests remotely for cross-compilation (following Evan's suggestion). Let's coorddinate our effort. Best regards, Viktor ----- Original Message ----- From: "David Goodwin"

Hi, I am trying to reduce what I believe to be a miscompilation bug. Running lli on my bitcode file causes a segmentation fault. However, running bugpoint as bugpoint file.bc gives me the following errors, /tmp/ccAdmNqH.o: In function `_ZL17bus_error_handleriP7siginfoPv': bugpoint-test-program.bc-Vega5s.cbe.c:(.text+0x1b4e1): undefined reference to `std::cerr' /tmp/ccAdmNqH.o: In

We have had a script for a while that does this for you in http://llvm.org/svn/llvm-project/llvm/trunk/utils/crosstool/ARM/ . It also uses the CodeSourcery toolchain so it saves you some effort. Does that work for you? On Mon, Jan 18, 2010 at 2:52 PM, Viktor Kutuzov <vkutuzov at accesssoftek.com>wrote: > Hello Corina, > > I used a two-stage sequence to build the llvm and llvm-gcc

--emit-llvm?? On Fri, Oct 30, 2009 at 7:55 AM, Viktor Kutuzov <vkutuzov at accesssoftek.com>wrote: > Hello everyone, > > I'm working on passing parameters for gold/LTO plug-in and could add this > one as well. > Just need an option name. Could anybody suggest one? > > Viktor > > ----- Original Message ----- > From: "Nick Lewycky" <nicholas at

Hi All, I'm using LLVM/Clang 3.1 release. I first compiled llvm/clang using GCC per the instructions on the web with cmake. I then compiled libc++ per the instructions on the web. I then tried to compile llvm/clang with previously compiled clang and libc++ using "-std=c++0x -stdlib=libc++" flags. But the compilation fails at: > [ 58%] Building CXX object

On 2012-06-26 04:22, Ashok Nalkund wrote: ... >> /local/mnt/workspace/ashoknn/519_libcxx_transition/llvm/src/tools/bugpoint/ToolRunner.cpp:131:12: error: invalid operands to binary expression ('llvm::raw_ostream' and 'std::ostringstream' >> (aka 'basic_ostringstream<char>')) >> errs() << OS; >> ~~~~~~ ^ ~~ > Hi Ashok,

Hello Corina, I used a two-stage sequence to build the llvm and llvm-gcc with the codesourcery toolchain and my custom built arm toolchain. There is some scripted chunks for each step. I have attached them as a single file to this email. May be it will help you somehow. Viktor. --- From: llvmdev-bounces at cs.uiuc.edu [llvmdev-bounces at cs.uiuc.edu] On Behalf Of corina s [corina_fff at

--emit-llvm, if not conflict >>> Paul Davey <plmdvy at gmail.com> 10/30/2009 11:11 AM >>> --emit-llvm?? On Fri, Oct 30, 2009 at 7:55 AM, Viktor Kutuzov <vkutuzov at accesssoftek.com> wrote: Hello everyone, I'm working on passing parameters for gold/LTO plug-in and could add this one as well. Just need an option name. Could anybody suggest one? Viktor

Hi David, It looks like you added the PWD= magic to Makefile.spec. It is preventing me from running bugpoint on the desktop, with errors like this: /Users/sabre/llvm/projects/llvm-test/External/SPEC/Sandbox.sh bugpoint- train Output/176.gcc.bugpoint-opt /Users/sabre/cvs/benchmarks/ speccpu2000/benchspec/CINT2000/176.gcc/data/train/input/ \