#9946: Parallel build of Singular 3-1-1-4-package fails in other cases
------------------------+---------------------------------------------------
   Reporter:  mpatel    |       Owner:  tbd         
       Type:  defect    |      Status:  needs_review
   Priority:  blocker   |   Milestone:  sage-4.6    
  Component:  packages  |    Keywords:              
     Author:            |    Upstream:  N/A         
   Reviewer:            |      Merged:              
Work_issues:            |  
------------------------+---------------------------------------------------

Comment(by drkirkby):

 Replying to [comment:19 leif]:
 > {{{
 > #!C
 >     if (sizeof(int) != 4) {
 >         fprintf(stderr,"Your system is odd. On everying except a Cray X
 MP, an int is 4 bytes\n");
 >         fprintf(stderr,"Exiting...\n");
 >         exit(3);
 >     }
 > }}}
 > LOL, ever heard of 16-bit systems (or compilers)? And even some old
 compilers on 32-bit systems had 2-byte {{{int}}}s IIRC (of course that's
 odd). I can't await having {{{sizeof(int)>=16}}}... ;-)

 No, but when I was testing http://atlc.sourceforge.net/ for portability, I
 found on a Cray X MP running Unicos that:

  * sizeof(long)=8
  * sizeof(int)=8
  * sizeof(short)=8

 The latter was a real pain to me.

 So nothing would totally surprise me.

 I've now set this up compiling in 5 different directories on machine

  * Maximum delay of 1 second (mean 500 ms)
  * Maximum delay of 100 ms (mean 50 ms)
  * Maximum delay of 10 ms (mean 5 ms)
  * Maximum delay of 1 ms (mean 500 us)
  * Maximum delay of 100 us (mean = 50 us)

 I suspect that the first of these is too long, so will slow builds
 considerably and the last is too short, so will not be too different from
 no delay.


 > The allocation of {{{delay_as_string}}} is useless (actually a space
 leak :) ) unless you {{{str[n]cpy()}}} the result of {{{getenv(...)}}} to
 it, but who cares.
 >

 Yes, you are correct. I'll change that, but it's not a big deal for now.
 It's a start.


 I don't know how this would fit in with Nathann's:

 ''... though my way of seeing it would really be to avoid spending hours
 wondering "how it could fail" when it seems so easy to just test it and
 write patches when errors are reported. ''


 Somehow I doubt it would fit in too well.

 If I don't get any problems, and there are are problems found by others,
 it would make me wonder how else one could try to find such problems. This
 was my best stab at an answer, but perhaps it is not ideal.

 I think really there should be a delay on the linker too, which I have not
 implemented. I've only done this on the compilers gcc, g++ and gfortran.

 Dave

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9946#comment:20>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica, 
and MATLAB

-- 
You received this message because you are subscribed to the Google Groups 
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/sage-trac?hl=en.

Reply via email to