Linux x86 testers needed!

All,

We are in desperate need of linux x86 testers (32 or 64 bit). If you could set one up, the LLVM project would be very grateful. Right now we have virtually no testers covering this platform.

Directions to set up a tester are here:
http://llvm.org/docs/TestingGuide.html#nightly

These directions could be improved of course. If you have any questions, I will be happy to assist you in setting up your nightly tester.

Thanks!
-Tanya

Hello,

All,

We are in desperate need of linux x86 testers (32 or 64 bit). If you
could set one up, the LLVM project would be very grateful. Right now
we have virtually no testers covering this platform.

I think I might be able to set up a nightly tester for Linux x86 (32-bit).

Although I've been following LLVM for quite a while now, I feel like I can't really contribute to it, because of lack of time and knowledge. Hopefully this way I can contribute...

I have some questions though:

*) Is something more expected besides donating cycles-to-burn, e.g. active bug reporting/resolving of bugs found by the nightly tester and such?
It's not that I'm not willing to (in fact, I'd love to), but I just wouldn't be able to find the time to do it properly. I try to report bugs I run into from time to time, but that's highly dependent on how busy I am doing my actual Phd work (to which LLVM is only partially related).

*) I'll probably need the machine for experiments now and then, I'm guessing it's ok the nightly test isn't run every single night?

greetings,

Kenneth

I had planned to try again once 2.3 is out, but if you're short on Linux
testers, I'll join in.

Available platforms:
* x86_64
* i686 compatibility
Given that I had problems getting the latter to run, I think I should
concentrate on x86_64.
Should I switch PIC off for that?

Regards,
Jo

Although I’ve been following LLVM for quite a while now, I feel like I
can’t really contribute to it, because of lack of time and knowledge.
Hopefully this way I can contribute…

Excellent!

I have some questions though:

*) Is something more expected besides donating cycles-to-burn, e.g.
active bug reporting/resolving of bugs found by the nightly tester and
such?
It’s not that I’m not willing to (in fact, I’d love to), but I just
wouldn’t be able to find the time to do it properly. I try to report
bugs I run into from time to time, but that’s highly dependent on how
busy I am doing my actual Phd work (to which LLVM is only partially
related).

Not necessary at all, while always appreciated. I think the biggest thing would be that if you notice something that wouldn’t even show up in the nightly (like a complete failure to build or something) to maybe send an email, especially if its repeatable, and continues. For the most part however, there are lots of people willing and eager to fix bugs once they know about them. Additionally the nightly testers provide other insight regarding performance and different system behaviors.

*) I’ll probably need the machine for experiments now and then, I’m
guessing it’s ok the nightly test isn’t run every single night?

The nightly tester system is well equipped for handling even moderately intermittent submissions – I think you’ll be fine! =]

-Chandler

Hi Tanya, I got the go-ahead from Laurent Guerby
for using the gcc compile farm for running the llvm
nightly tester (http://gcc.gnu.org/wiki/CompileFarm).
I will try to set this up, but in fact anyone can
apply for a login as described at the above webpage.

Ciao,

Duncan.

PS: The machines are all running linux and are mostly
amd64 or x86-32, but there is also an alpha.

Wow, this is great news!! Thanks Duncan!

-Tanya

We are in desperate need of linux x86 testers (32 or 64 bit). If you
could set one up, the LLVM project would be very grateful. Right now
we have virtually no testers covering this platform.

I think I might be able to set up a nightly tester for Linux x86 (32-
bit).

Although I've been following LLVM for quite a while now, I feel like I
can't really contribute to it, because of lack of time and knowledge.
Hopefully this way I can contribute...

That would be great! Thank you!

I have some questions though:

*) Is something more expected besides donating cycles-to-burn, e.g.
active bug reporting/resolving of bugs found by the nightly tester and
such?

The best case scenario is when someone actually watches the nightly tester, but at this point, we will take anything (even if its just cycles). It would be helpful if you do see a failure, to either bring it to attention on the llvm-testresults mailing list or to file a PR. People are supposed to watch the nightly testers when they commit, but as you can imagine.. that doesn't always happen. However, if you don't have time to do this.. then don't worry.

It's not that I'm not willing to (in fact, I'd love to), but I just
wouldn't be able to find the time to do it properly. I try to report
bugs I run into from time to time, but that's highly dependent on how
busy I am doing my actual Phd work (to which LLVM is only partially
related).

Yes, I understand.

*) I'll probably need the machine for experiments now and then, I'm
guessing it's ok the nightly test isn't run every single night?

You can run it as often as you like. The only downside is that it makes it harder to track down problems, but since we don't have any linux testers at the moment.. occasional testing is better than none at all :slight_smile:

-Tanya

I had planned to try again once 2.3 is out, but if you're short on Linux
testers, I'll join in.

Available platforms:
* x86_64
* i686 compatibility
Given that I had problems getting the latter to run, I think I should
concentrate on x86_64.
Should I switch PIC off for that?

Thanks! Running a linux tester would be a huge help for the project.

However, I am not sure why you need to switch PIC off. Could you explain a bit more?

-Tanya

Just a FYI.

Default x86-64 relocation model is PIC. I think we should definitely test that. x86-32 llc default is dynamic-no-pic. In order to test pic, you have to pass something like this to the NewNightlyTest.pl script:

-test-opts "TARGET_FLAGS= TARGET_LLCFLAGS=\"-relocation-model=pic -disable-fp-elim\" EXTRA_LLI_OPTS=\"-relocation-model=pic -disable-fp-elim\""

We probably ought to add an option to the script instead.

Evan

Last thing I heard about x86_64 was that PIC didn't work / was not
implemented for that target.

If it works now, then great!

Regards,
Jo

Last thing I heard about x86_64 was that PIC didn't work / was not
implemented for that target.

If it works now, then great!

I am working on it. I think to only missing issue is that we need to
use the PLT in calls to locally define symbols that are externally
visible.

Regards,
Jo

Cheers,

Hello list!

Tanya Lattner wrote:

We are in desperate need of linux x86 testers (32 or 64 bit). If you could set one up, the LLVM project would be very grateful. Right now we have virtually no testers covering this platform.

I've run the test last night to see how long it takes, and I can
afford to cronjob it for the night.

I didn't quite realize it would automatically send the report, but
it did [1] and there are a few test failure from the
Frontend{C,C++} directories. I suppose this is because I have
llvm-gcc4.0 2.1 installed, which might need to be upgraded. Is
there a specific version of llvm-gcc that is prefered for nightly
tests? Shall I go with the latest stable one? 4.0 or 4.2?

What does -enable-linscan do? It's not referenced anywhere in
NewNightlyTest.pl, but it's given as example in [2].

I will also take the freedom to disable the nightly test if I need
the CPU cycles for something else during a night.

jlh

[1] http://llvm.org/nightlytest/test.php?machine=288&night=6315
[2] http://llvm.org/docs/TestingGuide.html#nightly

4.2

I've run the test last night to see how long it takes, and I can
afford to cronjob it for the night.

Great!

I didn't quite realize it would automatically send the report, but
it did [1] and there are a few test failure from the
Frontend{C,C++} directories. I suppose this is because I have
llvm-gcc4.0 2.1 installed, which might need to be upgraded. Is
there a specific version of llvm-gcc that is prefered for nightly
tests? Shall I go with the latest stable one? 4.0 or 4.2?

llvm-gcc4.0 is no longer supported, use llvm-gcc4.2. Please keep in mind that you need to keep llvm-gcc in sync with llvm (same revision number).

What does -enable-linscan do? It's not referenced anywhere in
NewNightlyTest.pl, but it's given as example in [2].

Its an option to enable linear scan register allocator. It probably wasn't default when the docs were written.

I will also take the freedom to disable the nightly test if I need
the CPU cycles for something else during a night.

Understood.

-Tanya

Tanya M. Lattner wrote:

Is
there a specific version of llvm-gcc that is prefered for nightly
tests? Shall I go with the latest stable one? 4.0 or 4.2?

llvm-gcc4.0 is no longer supported, use llvm-gcc4.2. Please keep in mind that you need to keep llvm-gcc in sync with llvm (same revision number).

This basically means llvm-gcc needs to be rebuild every time llvm
is built and the test run. Shouldn't this be part of
NewNightlyTest.pl then?

jlh

llvm-gcc4.0 is no longer supported, use llvm-gcc4.2. Please keep in mind
that you need to keep llvm-gcc in sync with llvm (same revision number).

This basically means llvm-gcc needs to be rebuild every time llvm
is built and the test run. Shouldn't this be part of
NewNightlyTest.pl then?

Yes. Patches accepted :wink:

There is a GSOC student that is supposed to be working on this too.

-Tanya

llvm-gcc4.0 is no longer supported, use llvm-gcc4.2. Please keep in mind
that you need to keep llvm-gcc in sync with llvm (same revision number).

This basically means llvm-gcc needs to be rebuild every time llvm
is built and the test run. Shouldn’t this be part of
NewNightlyTest.pl then?

Yes. Patches accepted :wink:

This is also impeding my running of a nightly tester…

There is a GSOC student that is supposed to be working on this too.

What’s the status/progress/timeline on that front (specifically, this feature)? Last thing I want to do is step on a GSoCers toes, but I’d love to lend a hand on this front where possible. =]

-Chandler

llvm-gcc4.0 is no longer supported, use llvm-gcc4.2. Please keep in mind
that you need to keep llvm-gcc in sync with llvm (same revision number).

This basically means llvm-gcc needs to be rebuild every time llvm
is built and the test run. Shouldn't this be part of
NewNightlyTest.pl then?

Yes. Patches accepted :wink:

This is also impeding my running of a nightly tester...

Well, you can write a simple script that svn update, make, make install and you are done. That will work in most cases. Or just run your tester and update it by hand periodically (thats what most people do).

There is a GSOC student that is supposed to be working on this too.

What's the status/progress/timeline on that front (specifically, this
feature)? Last thing I want to do is step on a GSoCers toes, but I'd love to
lend a hand on this front where possible. =]

No idea, maybe he will respond. Don't let it stop you if you want to contribute.

-Tanya

>>>> llvm-gcc4.0 is no longer supported, use llvm-gcc4.2. Please keep in mind
>>>> that you need to keep llvm-gcc in sync with llvm (same revision number).

>>> This basically means llvm-gcc needs to be rebuild every time llvm
>>> is built and the test run. Shouldn't this be part of
>>> NewNightlyTest.pl then?

>> Yes. Patches accepted :wink:

> This is also impeding my running of a nightly tester...

Well, you can write a simple script that svn update, make, make install
and you are done. That will work in most cases. Or just run your tester
and update it by hand periodically (thats what most people do).

I have added some convenience targets to llvm/test/Makefile (look at
"update" and "happiness") which may give hints.

Cheers,

    Gabor