Bugs item #586934, was opened at 2002-07-26 10:32
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=108032&aid=586934&group_id=8032

Category: Compiler
Group: 5.04
Status: Open
Resolution: None
Priority: 5
Submitted By: geoff (snailtalk)
Assigned to: Simon Marlow (simonmar)
Summary: ghc fail build with gcc 3.1

Initial Comment:
ghc will fail to build with newer gcc if -O is given to
ghc. Comfirmed with gcc 3.1, and most probably the
upcoming 3.2 as well.


Prologue junk?: .globl __stginit_Main
__stginit_Main:
        pushl   %ebp
        movl    %esp, %ebp
        
is the ghc complaint (looks like a function prologue in
ASM). Temporary fix is to compile with -O -fasm.

Note that this also means that you will be unable to
bootstrap ghc from source if you have a newer gcc
installed on your system.

Verified on Linux/x86 only.


----------------------------------------------------------------------

>Comment By: Simon Marlow (simonmar)
Date: 2002-09-18 09:47

Message:
Logged In: YES 
user_id=48280

The original reporter was building 5.02.3; there were several 
GCC 3.x related fixes that went into 5.04, so I suggest 
upgrading.

I'll take a look at GCC 3.2 and investigate the new warnings.


----------------------------------------------------------------------

Comment By: Matthew Walton (matthewwalton)
Date: 2002-09-18 08:49

Message:
Logged In: YES 
user_id=110768

This is happening to me. Gentoo Linux (on x86) built with
GCC 3.2 (but not the official 1.4 release using GCC 3.2, I
hacked this one together myself), building GHC with GCC 3.2
using the ebuild scripts from Portage.

As well as the GHC complaint here, I also see lots of
messages from GCC itself apparently complaining about the
validity of the HC files I'm bootstrapping from. For example:

CTypesISO.hc:20090: warning: (near initialization for
`CTypesISO_zdfIntegralCPtrdiff_closure.payload')
CTypesISO.hc:20090: warning: excess elements in array
initializer

I assume this has something to do with GCC 3.2 having
differing ideas about what constitutes valid C. I know
they're not errors, but they're worth noting, as well as
some warnings about excess tokens at the end of #endif.

----------------------------------------------------------------------

Comment By: geoff (snailtalk)
Date: 2002-09-07 06:53

Message:
Logged In: YES 
user_id=20846

Linux version is 2.4.18 kernel, Mandrake cooker.
(development distribution).
gcc installed is gcc 3.2 from Mandrake cooker.

ghc is 5.02.3.

Note that it appears not to happen under Debian unstable
with their gcc3.2.



----------------------------------------------------------------------

Comment By: Simon Marlow (simonmar)
Date: 2002-09-02 14:43

Message:
Logged In: YES 
user_id=48280

I've tried to reproduce this and can't.  Could you describe 
*exactly* what you did to cause the error, including:

 - Linux flavour/version
 - what version(s) of gcc are installed, under which names
 - similarly for GHC

Thanks.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=108032&aid=586934&group_id=8032
_______________________________________________
Glasgow-haskell-bugs mailing list
[EMAIL PROTECTED]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs

Reply via email to