unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Neil Jerram <neil@ossau.uklinux.net>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: request review: branch "wingo"
Date: Mon, 30 Mar 2009 22:39:07 +0100	[thread overview]
Message-ID: <874oxapu6c.fsf@arudy.ossau.uklinux.net> (raw)
In-Reply-To: <m3vdpsq27x.fsf@pobox.com> (Andy Wingo's message of "Sat\, 28 Mar 2009 23\:20\:50 -0700")

Andy Wingo <wingo@pobox.com> writes:

> Hey all,
>
> On Fri 27 Mar 2009 16:29, Andy Wingo <wingo@pobox.com> writes:
>
>> On the "wingo" branch in the main repository, you will find the
>> following patches:
>
> So, I really intended to wait for review, but it's irritating having
> `master' broken, so I went ahead and merged this in.

Here are my comments on the merged commits.

- allow building against uninstalled guile; move some things to meta/

Looks like a good idea.  Could be some gotchas lurking, but I don't
immediately see any.

- add getrlimit and setrlimit wrappers

Should scm_getrlimit code be surrounded by #ifdef HAVE_GETRLIMIT ?

What's the idea of the numerical args?  Should RLIMIT_XXX be defined
somewhere as Scheme-level integers?

Does it make sense to want to set the soft limit only?  I thought some
hard limits were only settable by root, so I would suspect yes.  If
yes, does the setrlimit implementation support this?

- getrlimit-based stack limits
- rely on getrlimit to DTRT, don't make stack calibration file

My inclination is that we should revert these; but I'm not sure, so
could be persuaded that I'm wrong.

My feeling is that what we had before is a stronger statement (than
using getrlimit) about the expected behaviour of typical Scheme
programs (and in particular those used during the build), and is
therefore worth keeping.  The getrlimit implementation just says "if a
program is running away, we'll generate a Scheme exception a little
bit before you'd otherwise get a core".

But maybe this isn't important enough to justify the hassle around
stack-limit calibration.  What do others think?

- fix check for guile-tools running uninstalled
- fix distcheck hopefully, by cleaning the vm-i-*.i files

Fine.

- fix "linking" of guile-config

I don't understand the problem here.  In what way was @bindir@ not
fully expanded?

- bugfix: don't dynamic link if we found a registered extension

Would be great to have a test for this, if feasible.

> I think the stack calibration stuff is correct, but perhaps more jarring
> in this commit is a move from ./pre-inst-guile to ./meta/guile, and
> ./pre-inst-guile-env to ./meta/uninstalled-env. I describe the rationale
> in 0b6d8fdc28ed8af56e93157179c305fef037e0a0. But then again, given that
> Neil invested so much time into the stack calibration stuff, that might
> be jarring too.

As above - the meta/ stuff looks fine to me, but I'm not sure about
the stack limit change.

Regards,
        Neil




  parent reply	other threads:[~2009-03-30 21:39 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-27 23:29 request review: branch "wingo" Andy Wingo
2009-03-29  6:20 ` Andy Wingo
2009-03-29 21:16   ` Neil Jerram
2009-03-30 21:39   ` Neil Jerram [this message]
2009-03-31  3:31     ` Andy Wingo
2009-03-31 23:25       ` Neil Jerram
2009-04-01  7:49         ` Ludovic Courtès
2009-04-01 13:46           ` Greg Troxel
2009-04-01 22:23           ` Neil Jerram
2009-04-03 17:24             ` Andy Wingo
2009-04-03 17:51         ` Andy Wingo
2009-04-12 13:00           ` Neil Jerram
2009-03-31 16:38   ` Ludovic Courtès
2009-03-31 19:11     ` Andy Wingo
2009-03-31 21:31       ` Ludovic Courtès
2009-03-31 22:47         ` Andy Wingo
2009-04-01  7:51           ` Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=874oxapu6c.fsf@arudy.ossau.uklinux.net \
    --to=neil@ossau.uklinux.net \
    --cc=guile-devel@gnu.org \
    --cc=wingo@pobox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).