Opened 11 years ago

Closed 4 years ago

#3791 closed defect (invalid)

ATLAS.spkg: add Altivec errata support for Linux PPC

Reported by: mabshoff Owned by: mabshoff
Priority: major Milestone: sage-duplicate/invalid/wontfix
Component: build Keywords:
Cc: fbissey, jpflori Merged in:
Authors: Reviewers:
Report Upstream: N/A Work issues:
Branch: Commit:
Dependencies: Stopgaps:

Description 

I was told that this line means that altivec was not detected.
For atlas on linux ppc with altivec, we should use the options
--cflags='-mregnames' -D c -DATL_AVgcc
for configure ( http://math-atlas.sourceforge.net/errata.html#G4gcc ).

With these options, I had "Vector ISA Extension configured as  AltiVec (1,2)".

Best regards,
Bin

Change History (13)

comment:1 Changed 11 years ago by mabshoff

  • Status changed from new to assigned

comment:2 Changed 11 years ago by mabshoff

  • Milestone changed from sage-3.2 to sage-3.1.3

comment:3 Changed 6 years ago by jdemeyer

  • Milestone changed from sage-5.11 to sage-5.12

comment:4 Changed 5 years ago by vbraun_spam

  • Milestone changed from sage-6.1 to sage-6.2

comment:5 Changed 5 years ago by vbraun_spam

  • Milestone changed from sage-6.2 to sage-6.3

comment:6 Changed 5 years ago by vbraun_spam

  • Milestone changed from sage-6.3 to sage-6.4

comment:7 Changed 4 years ago by kcrisman

  • Cc fbissey jpflori added
  • Report Upstream set to N/A

What do you guys think - is this still valid?

comment:8 Changed 4 years ago by jpflori

Frankly, I'd say we don't care about such systems... And from the ticket description it just seems that ATLAS won't be optimized on such systems but would still build.

comment:9 Changed 4 years ago by fbissey

My own experience is that you need to let ATLAS set its own flags on power7 and probably other ppc(64) arch. It detects and adds altivec/vsx flags appropriately. If you touch CFLAGS you have to make sure to include flags that activate altivec (appropriate -mcpu and -mtune does the trick the CPPFLAGS should be included automatically and failure to include the right flags will result in a compilation failure at some point).

Is this for your project of building a last tiger ppc binary?

comment:10 Changed 4 years ago by kcrisman

Is this for your project of building a last tiger ppc binary?

No, although that is going fine. This is just me seeing random tickets that possibly could be closed as wontfix/invalid... I can't say whether it would but if you both agree then I say you should do so :)

comment:11 Changed 4 years ago by fbissey

  • Status changed from new to needs_review

comment:12 Changed 4 years ago by fbissey

  • Status changed from needs_review to positive_review

I am putting it as "invalid".

comment:13 Changed 4 years ago by vbraun

  • Milestone changed from sage-6.4 to sage-duplicate/invalid/wontfix
  • Resolution set to invalid
  • Status changed from positive_review to closed

You are supposed to change the milestone to "duplicate/invalid/wontfix" then...

Note: See TracTickets for help on using tickets.