New installer available that includes all STABLE changes up
until 20:00 UTC today:
http://www.haskell.org/ghc/dist/stable/dist/ghc-6-4-20050304.msi
( md5.sig: 022bfcaae335b718bdc59014d58b39a0 )
--sigbjorn
- Original Message -
From: "Sigbjorn Finne" <[EMAIL PROTECTED]>
simonmar:
> On 04 March 2005 16:59, John Goerzen wrote:
>
> > On Fri, Mar 04, 2005 at 04:57:04PM -, Simon Marlow wrote:
> >> On 04 March 2005 14:04, John Goerzen wrote:
> My amd64 hardware arrived yesterday, shouldn't be too long before
> we have a registerised port of GHC, and possi
Further to my last point, what if the top level module is Main...
ghci Main.hs
and that includes a main function, and pragmas, so that main runs
when ghci is finished loading (automatically).
If main runs automatically then the context of ghci must be the
Main module, so why would the options pragm
On 4-Mar-05, at 11:57 AM, Simon Marlow wrote:
Don't hold your breath, I have some bad news. It seems that gcc is
still generating incorrect code for register variables (or maybe it's
broken again?).
So maybe this will be the first NCG-only port of GHC :-).
Death to the Mangler!
Cheers,
Wolfgang
__
On 4-Mar-05, at 11:35 AM, Malcolm Wallace wrote:
Wolfgang Thaller <[EMAIL PROTECTED]> wrote:
I've uploaded a Mac OS X installer based on the stable tree from March
2nd + the patches I committed yesterday at:
http://opeongo.cas.mcmaster.ca/~wolfgang/GHC-6.4.20050302.pkg.zip
$ ghc --version
d
On 04 March 2005 16:59, John Goerzen wrote:
> On Fri, Mar 04, 2005 at 04:57:04PM -, Simon Marlow wrote:
>> On 04 March 2005 14:04, John Goerzen wrote:
My amd64 hardware arrived yesterday, shouldn't be too long before
we have a registerised port of GHC, and possibly a native code
Wolfgang Thaller <[EMAIL PROTECTED]> wrote:
> I've uploaded a Mac OS X installer based on the stable tree from March
> 2nd + the patches I committed yesterday at:
>
> http://opeongo.cas.mcmaster.ca/~wolfgang/GHC-6.4.20050302.pkg.zip
$ ghc --version
dyld: /usr/local/lib/ghc-6.4/ghc-6.4 c
On Fri, Mar 04, 2005 at 04:57:04PM -, Simon Marlow wrote:
> On 04 March 2005 14:04, John Goerzen wrote:
> >> My amd64 hardware arrived yesterday, shouldn't be too long before we
> >> have a registerised port of GHC, and possibly a native code
> >> generator...
> >
> > excellent
>
> Don't h
On 04 March 2005 14:04, John Goerzen wrote:
> On Fri, Mar 04, 2005 at 09:38:47AM -, Simon Marlow wrote:
>>> Even if you're not running Debian, there are tools available to
>>> convert a .deb to a RPM or tgz package. Or, you can easily unpack a
>>> deb using only ar(1) and tar(1).
>>
>> My am
I've uploaded a Mac OS X installer based on the stable tree from March
2nd + the patches I committed yesterday at:
http://opeongo.cas.mcmaster.ca/~wolfgang/GHC-6.4.20050302.pkg.zip
This package is built with support for dynamic libraries (some human
intervention was required to build it).
Mac u
Simon Marlow wrote:
On 04 March 2005 12:58, Keean Schupke wrote:
There can only be one top level module in ghci (there can only
be one module name before the '>' prompt - that modules options
should be in effect.
No, you can have multiple top-level module scopes in effect. See the
GHCi doc
On Fri, Mar 04, 2005 at 09:38:47AM -, Simon Marlow wrote:
> > Even if you're not running Debian, there are tools available to
> > convert a .deb to a RPM or tgz package. Or, you can easily unpack a
> > deb using only ar(1) and tar(1).
>
> My amd64 hardware arrived yesterday, shouldn't be too
On 02 March 2005 05:08, Brian Strand wrote:
> Donald Bruce Stewart wrote:
>> bstrand:
>>
>>> Donald Bruce Stewart wrote:
>>>
bstrand:
> Simon Marlow wrote:
>
>
>> Just to let you know, there are a number of open bug reports for
>> GHC on the x86_64 platform
> My amd64 hardware arrived yesterday, shouldn't be too long before we
> have a registerised port of GHC, and possibly a native code generator...
That would be great! I just assembled an amd64 box and I am mssing ghci
badly. Let me know if I can be of any help (testing ..).
Cheers, Ralf
_
On 04 March 2005 12:58, Keean Schupke wrote:
> There can only be one top level module in ghci (there can only
> be one module name before the '>' prompt - that modules options
> should be in effect.
No, you can have multiple top-level module scopes in effect. See the
GHCi documentation.
> Simon
There can only be one top level module in ghci (there can only
be one module name before the '>' prompt - that modules options
should be in effect.
The whole point of putting options at the top of the source file
is so that the user/compiler of the code does not need to know
which specific options
Simon Marlow ([EMAIL PROTECTED]) wrote:
> My amd64 hardware arrived yesterday, shouldn't be too long before we
> have a registerised port of GHC, and possibly a native code generator...
:-
As soon as you have some pre-alpha release, I'm ready to test ;)
Sincerely,
Gour
--
Registered Linux
Just ahead of the 6.4 release, we've put together a GHC user survey.
The idea is to help us get a better understanding of who uses GHC, what
for, what aspects of GHC they consider most valuable, and what they
would most like to see improved. The survey is anonymous (if you wish),
and should take a
I think GHC's behaviour is right here. To use the flag settings from
the source module on the command-line would be wrong: for example, when
the module is compiled, its implementation (and therefore flag settings)
must be hidden.
Also, as Simon pointed out, there might be multiple modules in scop
On 02 March 2005 14:15, John Goerzen wrote:
> Kip Macy gmail.com> writes:
>
>> I've followed the instructions to the letter.
>
> Debian has had a working amd64 package of ghc for some time now. It
> is built out of the standard source base for it. You can find that
> at:
>
> http://ftp.debi
Feature Requests item #1155875, was opened at 2005-03-03 16:36
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=358032&aid=1155875&group_id=8032
Category: None
Group: None
Status: Open
Prior
Hi Sigbjorn.
I wrote:
> I built CVS head GHC with this package and mucked around a little
bit. > The
> only problem I've come across so far is that an objectio library
>application
> I have crashes on take-off when built with this compiler (not
necessarily to
> do with objectio of course). It
22 matches
Mail list logo
