similar to: [LLVMdev] Heads up! Working on bugpoint

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:

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"

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

> 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

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

Hello everyone, Please find the patch attached. This fixes the bugpoint -remote-client and adds a helper script for a remote run. -Viktor -------------- next part -------------- A non-text attachment was scrubbed... Name: ToolRunner.diff Type: application/octet-stream Size: 4210 bytes Desc: not available URL:

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

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,

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:

Something has changed in the last few days that breaks thumb-2 (and possibly all ARM) assembly output. Some, but not all lines are double- spaced, for example: fstd d13, [sp, #+40] fstd d12, [sp, #+32] fstd d11, [sp, #+24] fstd d10, [sp, #+16] fstd d9, [sp, #+8] fstd d8, [sp] sub sp, sp, #872 mov r4, r1 mov r5, r0 cmp r0, #2 ble LBB1_133 @ entry.bb2.i_crit_edge LBB1_1: @

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

It doesn't break the assembler... but it is wrong... and ugly... and many other adjectives. I isolated the change and let the submitter know. David On Jul 17, 2009, at 3:30 PM, Anton Korobeynikov wrote: > Hi David > > On Sat, Jul 18, 2009 at 02:00, David > Goodwin<david_goodwin at apple.com> wrote: >> Something has changed in the last few days that breaks thumb-2

Yes. But it is not really being used by most (any?) targets because post-RA scheduling is disabled by default. Also, the existing model is very limited in what types of micro-architectures can be described. I've been extending it to enable scheduling of multi-issue targets, targets with overlapping FU usage, and targets that use and define registers in multiple pipeline stages. See

Hi David On Sat, Jul 18, 2009 at 02:00, David Goodwin<david_goodwin at apple.com> wrote: > Something has changed in the last few days that breaks thumb-2 (and possibly > all ARM) assembly output. Some, but not all lines are double-spaced, for > example: How does extra whitespace break the things? -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint

--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

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