Patch to build Open MPI on Alpha (Was: Re: Access to developer machine)
[ Sorry for resurrecting an old thread! And please CC me in replies, I'm
not subscribed. ]
Am Dienstag, den 03.02.2009, 21:23 +0100 schrieb Oliver Falk:
Le me know the patch you (might) produce, so I can check on Fedora/Alpha
:-) If you like...
Well, I finally succeeded in developing a patch, and you can find the
result attached. It would be really great if you could test and/or
review it, since I do not know if the assembly is correct; I tried to
teach myself Alpha assembly and have no idea if I got it. ;)
I'm very intersted in your feedback, especially if it works on Fedora. I
was able to build Debian packages on Albeniz and am quite confident that
the patch works. You can either reply to me or send a message to the
corresponding bug. (510...@bugs.debian.org)
Thanks in advance!
Best regards
Manuel
--- a/ompi/contrib/vt/vt/vtlib/vt_pform_linux.c
+++ b/ompi/contrib/vt/vt/vtlib/vt_pform_linux.c
@@ -170,6 +170,8 @@
# elif defined(__ia64__)
/* ... ITC */
clock_value = __getReg(_IA64_REG_AR_ITC);
+# elif defined(__alpha__)
+asm volatile (rpcc %0 : =r (clock_value));
# else
/* ... TSC */
{
--- a/opal/asm/base/ALPHA.asm
+++ b/opal/asm/base/ALPHA.asm
@@ -197,3 +197,28 @@
addl $31,$0,$0
ret $31,($26),1
.end opal_atomic_cmpset_rel_64
+ .align 2
+ .align 4
+ .globl opal_sys_timer_get_cycles
+ .ent opal_sys_timer_get_cycles
+$opal_sys_timer_get_cycles..ng:
+opal_sys_timer_get_cycles:
+ .eflag 48
+ .frame $30,0,$26,0
+ .prologue 0
+ .set macro
+ wmb
+ 1: ldq_l $0, 0($16)
+ cmpeq $0, $17, $0
+ beq $0, 2f
+ mov $18, $0
+ stq_c $0, 0($16)
+ beq $0, 1b
+ jmp 3f
+2: mov $31, $0
+3:
+
+ .set nomacro
+ rpcc $0
+ ret
+ .end opal_sys_timer_get_cycles
--- a/opal/asm/generated/atomic-alpha-linux.s
+++ b/opal/asm/generated/atomic-alpha-linux.s
@@ -197,5 +197,30 @@
addl $31,$0,$0
ret $31,($26),1
.end opal_atomic_cmpset_rel_64
+ .align 2
+ .align 4
+ .globl opal_sys_timer_get_cycles
+ .ent opal_sys_timer_get_cycles
+$opal_sys_timer_get_cycles..ng:
+opal_sys_timer_get_cycles:
+ .eflag 48
+ .frame $30,0,$26,0
+ .prologue 0
+ .set macro
+ wmb
+ 1: ldq_l $0, 0($16)
+ cmpeq $0, $17, $0
+ beq $0, 2f
+ mov $18, $0
+ stq_c $0, 0($16)
+ beq $0, 1b
+ jmp 3f
+2: mov $31, $0
+3:
+
+ .set nomacro
+ rpcc $0
+ ret
+ .end opal_sys_timer_get_cycles
.section .note.GNU-stack,,@progbits
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
Re: Access to developer machine
On Tue, 2009-02-03 at 19:35 +0100, Manuel Prinz wrote: 1. The box available for developers is albeniz, right? Correct. 2. Since this is the first time I request to use such a service, is there any documentation on how to work on the machine? (Like use chroot X.) Run 'dchroot -l' to get a list of available chroots. 'dchroot sid' to go into the sid chroot. 3. Is it possible to install libtool from experimental? It is required by upstream in case the build system needs to be touched. Contact debian-ad...@l.d.o to get stuff installed in chroots. Cheers, Julien -- To UNSUBSCRIBE, email to debian-alpha-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Access to developer machine
Manuel Prinz schrieb: [ Please CC me in replies. I'm not subscribed. ] Dear Alpha porters, in order to track down the issue that prevents Open MPI from building on Alpha (bug #510845), I'd like to request access to machine where I can work on the issue. I tried to get some information on this but still have some questions which I hope you can answer: 1. The box available for developers is albeniz, right? 2. Since this is the first time I request to use such a service, is there any documentation on how to work on the machine? (Like use chroot X.) 3. Is it possible to install libtool from experimental? It is required by upstream in case the build system needs to be touched. Thanks in advance for your time and support! Best regards Manuel Do you require Debian/Alpha, or would Fedora/Alpha also be fine? (Sorry, Debianers :-)) -of -- To UNSUBSCRIBE, email to debian-alpha-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Access to developer machine
Manuel Prinz schrieb: Hello Uwe! Am Dienstag, den 03.02.2009, 21:05 +0100 schrieb Uwe Schindler: You can get access to my alpha (Alphastation 500), too. It is running debian testing. I could also install libtool from experimental. That would be really great! I'd prefer that to Oliver's offer since it's easier to rule out possible distro-specific issues. Oliver, thanks a lot for your offer nevertheless! I'm quite overwhelmed by the all support I get here! Thank you all! :) That's fine for me. Le me know the patch you (might) produce, so I can check on Fedora/Alpha :-) If you like... -of -- To UNSUBSCRIBE, email to debian-alpha-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Access to developer machine
Am Dienstag, den 03.02.2009, 21:23 +0100 schrieb Oliver Falk: Le me know the patch you (might) produce, so I can check on Fedora/Alpha :-) If you like... Sure! The more testing, the better! ;) Best regards Manuel signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
RE: Access to developer machine
You can get access to my alpha (Alphastation 500), too. It is running debian testing. I could also install libtool from experimental. Uwe - Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: u...@thetaphi.de -Original Message- From: Oliver Falk [mailto:oli...@linux-kernel.at] Sent: Tuesday, February 03, 2009 8:17 PM To: Manuel Prinz Cc: debian-alpha@lists.debian.org Subject: Re: Access to developer machine Manuel Prinz schrieb: [ Please CC me in replies. I'm not subscribed. ] Dear Alpha porters, in order to track down the issue that prevents Open MPI from building on Alpha (bug #510845), I'd like to request access to machine where I can work on the issue. I tried to get some information on this but still have some questions which I hope you can answer: 1. The box available for developers is albeniz, right? 2. Since this is the first time I request to use such a service, is there any documentation on how to work on the machine? (Like use chroot X.) 3. Is it possible to install libtool from experimental? It is required by upstream in case the build system needs to be touched. Thanks in advance for your time and support! Best regards Manuel Do you require Debian/Alpha, or would Fedora/Alpha also be fine? (Sorry, Debianers :-)) -of -- To UNSUBSCRIBE, email to debian-alpha-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org -- To UNSUBSCRIBE, email to debian-alpha-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
RE: Access to developer machine
Hello Uwe! Am Dienstag, den 03.02.2009, 21:05 +0100 schrieb Uwe Schindler: You can get access to my alpha (Alphastation 500), too. It is running debian testing. I could also install libtool from experimental. That would be really great! I'd prefer that to Oliver's offer since it's easier to rule out possible distro-specific issues. Oliver, thanks a lot for your offer nevertheless! I'm quite overwhelmed by the all support I get here! Thank you all! :) Best regards Manuel signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
Re: Access to developer machine
Hi Oliver! Am Dienstag, den 03.02.2009, 20:17 +0100 schrieb Oliver Falk: Do you require Debian/Alpha, or would Fedora/Alpha also be fine? (Sorry, Debianers :-)) To track down the issue, Fedora should be fine, as Fedora has the following available: * required: libibverbs-dev = 1.1, gfortran, gcc * optional: automake = 1.10, autoconf = 2.63, m4 = 1.4.11 and libtool = 2.2, subversion libibverbs-dev is not really required but it would be nice to build against it since we do so in Debian. Many thanks for offering support! (That's how I read your mail.) ;) Best regards Manuel P.S.: I looked the versions up at fedoraproject.org and it seems like everything is available in recent Fedora versions, so yes, Fedora/Alpha would be fine! signature.asc Description: Dies ist ein digital signierter Nachrichtenteil
