"Julian Seward (Intl Vendor)" <[EMAIL PROTECTED]> writes:
>
> | > char fooble ( ... )
> | > {
> | >return 'z';
> | > }
> | >
> | > on an x86, 'z' will be returned at the lowest 8 bits in %eax. What I
>
> | > don't know is, is the C compiler obliged to clear the upper 24 bits
> of
> | > %e
At 2001-08-07 11:13, Carl R. Witty wrote:
>You can see that the code for f is:
> call g
> andl $255,%eax
> ret
>So gcc believes that a function which returns a value of type unsigned
>char is not responsible for clearing the high 3 bytes of %eax.
This is to be expected; in most
"Sigbjorn Finne" <[EMAIL PROTECTED]> writes:
> "Julian Seward (Intl Vendor)" <[EMAIL PROTECTED]> writes:
> >
> > Hmm, we're looking at this. However, I don't really know what
> > C is or is not supposed to do here. Given
> >
> > char fooble ( ... )
> > {
> >return 'z';
> > }
> >
> > on a
> In local.glasgow-haskell-users, you wrote:
> > Issue 1: should the maximum heap size be unbounded by default?
> > Currently the maximum heap size is bounded at 64M.
> Arguments for: this
> > stops programs with a space leak eating all your swap
> space. Arguments
> > against: it's annoying t
In local.glasgow-haskell-users, you wrote:
> Issue 1: should the maximum heap size be unbounded by default?
> Currently the maximum heap size is bounded at 64M. Arguments for: this
> stops programs with a space leak eating all your swap space. Arguments
> against: it's annoying to have to raise
> "Simon Marlow" <[EMAIL PROTECTED]> writes:
>
> > Ok, I've done the following:
>
> > - disabled the maximum heap
>
> > - RTS options are taken from the GHCRTS environment variable
> > in addition to the command line (the command line has
> precedence).
>
> (I haven't followed this d
"Simon Marlow" <[EMAIL PROTECTED]> writes:
> Ok, I've done the following:
> - disabled the maximum heap
> - RTS options are taken from the GHCRTS environment variable
> in addition to the command line (the command line has precedence).
(I haven't followed this debate closely, so I may
Mon, 06 Aug 2001 15:40:50 -0700, Thomas Hallgren <[EMAIL PROTECTED]> pisze:
> Regarding the maximum heap size, to avoid letting the heap grow too
> large, you could perhaps take into account the number of page faults
> that occur during garbage collection, or the ratio between CPU time and
> r
Ok, I've done the following:
- disabled the maximum heap size by default. It can still be
enabled with +RTS -M
- RTS options are taken from the GHCRTS environment variable
in addition to the command line (the command line has precedence).
- Compacting garbage collection is enabl
Sigbjorn
Am confused by your answer.
| > char fooble ( ... )
| > {
| >return 'z';
| > }
| >
| > on an x86, 'z' will be returned at the lowest 8 bits in %eax. What I
| > don't know is, is the C compiler obliged to clear the upper 24 bits
of
| > %eax, or does that onus fall on the callee?
I didn't realise I also had to put this on the line that works out the dependencies.
In hindsight it's obvious. Perhaps the documentation could be updated with a note? I'd
be happy to supply some text. Dominic.
[EMAIL PROTECTED] on 07/08/2001 10:07:00
To: Dominic Steinitz
glasgow-haskell
> I'm getting the following error using the instructions in
> 4.9.5.1 Dependency
> Generation.
>
> [dominic@r341-02 webldap]$ make depend
> ghc -M -cpp Add.hs EnvPassed.hs ParseError.hs Search.hs
> ASNv1.hs Counter.hs GetO
> pt.hs ParseExpr.hs StdTokenDef.hs Basev1.hs DecodeAll.hs
> Hello.hs P
I'm getting the following error using the instructions in 4.9.5.1 Dependency
Generation.
[dominic@r341-02 webldap]$ make depend
ghc -M -cpp Add.hs EnvPassed.hs ParseError.hs Search.hs ASNv1.hs Counter.hs GetO
pt.hs ParseExpr.hs StdTokenDef.hs Basev1.hs DecodeAll.hs Hello.hs ParseLib.hs Ta
gsv1.hs
I like the enviornment variable option, I would very much like to have
part of my log-in sequence parse the output of 'free' or some other real
memory reporting tool and set the limits as appropriate for the system I
happen to be on.
John
On Tue, Aug 07, 2001 at 08:54:25AM +0100, Marc van
S.D.Mechveliani ([EMAIL PROTECTED]) wrote:
: > Issue 1: should the maximum heap size be unbounded by default?
: > Currently the maximum heap size is bounded at 64M.
: > [..]
: > 1. remove the default limit altogether
: > 2. raise the default limit
: > 3. no change
:
: Put the defaul
Hello,
here are my votes on Simon Marlow's questions.
> Issue 1: should the maximum heap size be unbounded by default?
> Currently the maximum heap size is bounded at 64M.
> [..]
> 1. remove the default limit altogether
> 2. raise the default limit
> 3. no change
Put the def
16 matches
Mail list logo
