i;
(that should be semantically equivalent to the original program.)
extern does both give the behaviour that Simon expected, and fix
capi_value on Windows.
Thanks
Ian
___
Cvs-ghc mailing list
Cvs-ghc@haskell.org
http://www.haskell.org/mailman/listinfo
Ian Lynagh
Date: Sun May 27 15:04:21 2012 +0100
Go back to using 'const' in capi_value
>---
tests/ffi/should_run/capi_value_c.c |2 +-
tests/ffi/should_run/capi_value_c.h |2 +-
2 files changed, 2 insertions
t; Turning off -O makes it work.
> >
> > Maybe time to update our mingw gcc bundles?
>
> yes, it is a bug in that version of GCC/gcc. Does explicit use of 'extern'
> makes the bug go away? E.g.
>
> extern const int
On Tue, May 1, 2012 at 3:05 AM, Simon Marlow wrote:
> commit 832fa64008548c6be4190da0a79a2b6e339eb7bd
> Author: Simon Marlow
> Date: Mon Apr 30 12:26:49 2012 +0100
>
> Fix capi_value on Windows
>
> This appears to be a bug in the gcc that we're currently us
mon Marlow
Date: Mon Apr 30 12:26:49 2012 +0100
Fix capi_value on Windows
This appears to be a bug in the gcc that we're currently using.
Compiling this, with -O:
const int i;
int f(void) {return i;}
results in this assembly:
push
Ian
capi_value fails on windows under msys. seems ok on Linux.
Simon
cd ./ffi/should_run && ./capi_valuecapi_value.run.stdout
2>capi_value.run.stderr
Actual stdout output differs from expected:
--- ./ffi/should_run/capi_value.stdout 2012-03-02 19:51:45 +
+++ ./ffi
