unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: Marco Maggi <marco.maggi-ipsu@poste.it>
Cc: bug-guile@gnu.org
Subject: Re: guile-2.0.0 fails to build without threads
Date: Mon, 20 Jun 2011 10:06:37 +0200	[thread overview]
Message-ID: <87sjr5lyeq.fsf@pobox.com> (raw)
In-Reply-To: <878vt092m3.fsf@pobox.com> (Andy Wingo's message of "Fri, 17 Jun 2011 12:25:08 +0200")

On Fri 17 Jun 2011 12:25, Andy Wingo <wingo@pobox.com> writes:

> On Sat 21 May 2011 15:51, Marco Maggi <marco.maggi-ipsu@poste.it> writes:
>
>> Andy Wingo wrote:
>>> Thanks.  You  seem to  be running on  system in  which the
>>> stack    grows   up.    Is    that   the    case?    Check
>>> libguile/scmconfig.h and config.log.
>>
>> Yes, I have:
>>
>> #define SCM_STACK_GROWS_UP 1 /* 0 or 1 */
>>
>> maybe the problem  is that GCC 4.6.0 with  -O3 optimises the
>> program in such a way that the test is invalidated.
>
> This bug is also present in Autoconf, where this test comes from
> originally.  I have reported it there.  I have no idea what kind of test
> can defeat such an omniscient inliner.

Fixed in git, for the time being.  It's an arms race with the compiler,
and clearly code clarity is losing:

  int
  find_stack_direction (int *addr, int depth)
  {
    int dir, dummy = 0;
    if (! addr)
      addr = &dummy;
    *addr = addr < &dummy ? 1 : addr == &dummy ? 0 : -1;
    dir = depth ? find_stack_direction (addr, depth - 1) : 0;
    return dir + dummy;
  }

  int
  main (int argc, char **argv)
  {
    return find_stack_direction (0, argc + !argv + 20) < 0;
  }

See
http://lists.gnu.org/archive/html/bug-autoconf/2011-06/msg00032.html.

Andy
-- 
http://wingolog.org/



  reply	other threads:[~2011-06-20  8:06 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-07 14:47 guile-2.0.0 fails to build without threads Marijn
2011-04-11 16:19 ` Andy Wingo
2011-04-12  7:26   ` Marijn
2011-04-13 10:05     ` Andy Wingo
2011-04-13 13:44       ` Marijn
2011-04-13 14:09         ` Andy Wingo
2011-04-13 14:27           ` Marijn
2011-04-13 15:22             ` Andy Wingo
2011-04-14 13:25               ` Marijn
2011-04-28 11:17                 ` Andy Wingo
2011-04-28 13:08                   ` Ludovic Courtès
2011-04-28 13:15                     ` Andy Wingo
2011-04-28 15:09                       ` Ludovic Courtès
2011-05-03 14:58                         ` Marijn
2011-05-04 12:19                           ` Ludovic Courtès
2011-05-05  8:04                             ` Marijn
2011-05-05 12:08                               ` Ludovic Courtès
2011-05-05 13:59                                 ` Marijn
2011-05-05 14:25                                   ` Ludovic Courtès
2011-05-06  8:16                                     ` Marijn
2011-05-06  9:52                                       ` Ludovic Courtès
2011-05-06 12:49                                         ` Marijn
2011-05-10  7:43                                         ` Marijn
2011-05-03 14:55                     ` Marijn
2011-04-12  6:49 ` Marco Maggi
2011-04-13  9:04   ` Marco Maggi
2011-04-13 11:42     ` Marco Maggi
2011-04-13 12:26       ` Andy Wingo
2011-04-13 13:56         ` Marco Maggi
2011-04-28 11:21           ` Andy Wingo
2011-05-02  6:20             ` Marco Maggi
2011-05-20  9:37               ` Andy Wingo
2011-05-20 18:41                 ` Marco Maggi
2011-05-21  2:23                   ` Mark H Weaver
2011-05-21  8:45                   ` Andy Wingo
2011-05-21 13:51                     ` Marco Maggi
2011-05-21 14:29                       ` Neil Jerram
2011-06-17 10:25                       ` Andy Wingo
2011-06-20  8:06                         ` Andy Wingo [this message]
2011-06-22 21:39                           ` Neil Jerram
2011-04-13  9:55   ` Andy Wingo
2011-04-13 14:19     ` Marco Maggi
2011-04-13 21:57   ` 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=87sjr5lyeq.fsf@pobox.com \
    --to=wingo@pobox.com \
    --cc=bug-guile@gnu.org \
    --cc=marco.maggi-ipsu@poste.it \
    /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).