Opened 11 years ago

Closed 11 years ago

#38792 closed defect (fixed)

atlas +mpclang33 build fails

Reported by: ryandesign (Ryan Carsten Schmidt) Owned by: Veence (Vincent)
Priority: Normal Milestone:
Component: ports Version: 2.1.3
Keywords: Cc: cooljeanius (Eric Gallager), mf2k (Frank Schima)
Port: atlas

Description

Following the fixes to the compiler checking, I tried to build atlas +mpclang33 but it failed; see log; I'm not sure what the relevant part is but I do see these errors:

cc1: error: unrecognized command line option "-fvectorize"
cc1: error: unrecognized command line option "-fslp-vectorize"

Attachments (2)

main.log.bz2 (78.5 KB) - added by ryandesign (Ryan Carsten Schmidt) 11 years ago.
main.log (208.5 KB) - added by mf2k (Frank Schima) 11 years ago.

Download all attachments as: .zip

Change History (20)

Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)

Attachment: main.log.bz2 added

comment:1 Changed 11 years ago by cooljeanius (Eric Gallager)

Cc: egall@… added

Cc Me!

comment:2 Changed 11 years ago by Veence (Vincent)

That should be fixed in r105258. Please try again, sorry for the inconvenience. Ryan, on what system did you compile? CPU? Thanks! Vincent

comment:3 Changed 11 years ago by Veence (Vincent)

r105311 should have fixed all bugs (I hope). Please try again.

comment:4 Changed 11 years ago by mf2k (Frank Schima)

It still fails for me with the same error on an iMac late 2009 with Core 2 Duo processor. Mac OS X 10.8.3. Xcode 4.6.2. Note also that I had to install gcc47 for a fortran compiler.

Last edited 11 years ago by mf2k (Frank Schima) (previous) (diff)

comment:5 Changed 11 years ago by mf2k (Frank Schima)

Cc: macsforever2000@… added

Cc Me!

comment:6 Changed 11 years ago by Veence (Vincent)

Could you please post your log? Thanks!

Changed 11 years ago by mf2k (Frank Schima)

Attachment: main.log added

comment:7 Changed 11 years ago by mf2k (Frank Schima)

@vince: My main.log is attached.

comment:8 in reply to:  2 ; Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)

Replying to vince@…:

Ryan, on what system did you compile? CPU?

MacBook Pro with 15" Retina Display 4 × 2.6GHz Core i7.

comment:9 in reply to:  8 Changed 11 years ago by Veence (Vincent)

Replying to ryandesign@…:

Replying to vince@…:

Ryan, on what system did you compile? CPU?

MacBook Pro with 15" Retina Display 4 × 2.6GHz Core i7.

Thanks Ryan. I hope your LCD is fine ;)

comment:10 in reply to:  7 Changed 11 years ago by Veence (Vincent)

Replying to macsforever2000@…:

@vince: My main.log is attached.

Thanks Franck. You hit the same clang/llvm bug as #38820. I’ve committed a patch that should solve it (workaround).

comment:11 Changed 11 years ago by mf2k (Frank Schima)

Note that it's still building after a number of hours. So you must have fixed that issue. I'll let you know when it finishes. Probably tomorrow.

comment:12 Changed 11 years ago by mf2k (Frank Schima)

FYI, atlas did finally build successfully for me! This bug is fixed for me.

comment:13 Changed 11 years ago by Veence (Vincent)

Franck, you were lucky. What version of clang are you using?

comment:14 Changed 11 years ago by mf2k (Frank Schima)

$ port installed clang-3.3
The following ports are currently installed:
  clang-3.3 @3.3-r179575_2+analyzer+assertions+python27 (active)

comment:15 Changed 11 years ago by Veence (Vincent)

That’s the latest revision I suppose. Well, the bug some encountered despite the workaround does not seem to be triggered in your case. But you have a Core2Duo machine, haven’t you?

comment:16 Changed 11 years ago by mf2k (Frank Schima)

Yes, the machine where it built was the Core2Duo iMac I specified in comment:4. Note that I was careful to build cctools and ld64 with llvm 3.3.

$ port installed cctools ld64
The following ports are currently installed:
  cctools @836_0+llvm33 (active)
  ld64 @134.9_1+llvm33 (active)
Last edited 11 years ago by mf2k (Frank Schima) (previous) (diff)

comment:17 Changed 11 years ago by Veence (Vincent)

I don’t think it is related to cctools and ld64. The bug Ryan and other stumbled on seems to be linked to an AVX specific vectorization.

Ryan, you confirm you hit the same bug?

comment:18 Changed 11 years ago by Veence (Vincent)

Resolution: fixed
Status: newclosed

No more relevant since the removal of clang variants. Fixed for the time being.

Note: See TracTickets for help on using tickets.