Opened 7 years ago

Closed 7 years ago

Last modified 7 years ago

#5903 closed bug (fixed)

GHC 7.4.1 32 bit: LLVM backend fails on OSX 64bit

Reported by: dterei Owned by: dterei
Priority: normal Milestone:
Component: Compiler (LLVM) Version: 7.4.1
Keywords: Cc:
Operating System: MacOS X Architecture: x86_64 (amd64)
Type of failure: Compile-time crash Test Case:
Blocked By: Blocking:
Related Tickets: Differential Rev(s):
Wiki Page:

Description

If running:

  • GHC: 7.4.1, 32bit
  • OSX: 64 bit
  • LLVM: 3.0

Things fail because the correct 32bit mode flag isn't being passed to the clang compiler used by the LLVM backend as the assembler.

Work around for now is to compile using:

$ ghc -opta-m32 -fllvm

But need to fix for 7.4.2

Change History (7)

comment:1 Changed 7 years ago by dterei

Ian could you raise the priority of this to high please? I don't want it to be forgotten about for the 7.4.2 release.

comment:2 Changed 7 years ago by davidterei@…

commit 5e383469a9cb1fc17af3882f6217e5382a80fc67

Author: David Terei <davidterei@gmail.com>
Date:   Sun Mar 4 23:53:37 2012 -0500

    Get correct options when calling 'clang' inplace of 'as' (#5903)

 compiler/main/DriverPipeline.hs |   13 ++++++++-----
 1 files changed, 8 insertions(+), 5 deletions(-)

comment:3 Changed 7 years ago by dterei

Resolution: fixed
Status: newclosed

Fixed. Please merge into a 7.4.2 release if there is one Ian.

comment:4 Changed 7 years ago by igloo

difficulty: Unknown
Status: closedmerge

comment:5 Changed 7 years ago by dterei

Status: mergeclosed

OK I merged into branch ghc-7.4 as that seems to be the style.

comment:6 in reply to:  5 Changed 7 years ago by simonmar

Replying to dterei:

OK I merged into branch ghc-7.4 as that seems to be the style.

FYI: you can just put the ticket into the merge state and igloo will handle the merging.

comment:7 Changed 7 years ago by dterei

That's what I normally do but people other than igloo seemed to be pushing patches into 7.4 branch... I'll stick with letting igloo handle from now on.

Note: See TracTickets for help on using tickets.