unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: guile-devel@gnu.org
Subject: Re: Regression on 32-bit big-endian targets
Date: Sat, 12 Dec 2020 19:55:28 +0100	[thread overview]
Message-ID: <4ea37906-fddc-bad6-b29e-3ca1bf9b0c77@physik.fu-berlin.de> (raw)
In-Reply-To: <9a864c2b-2076-5849-2af2-e52f267cdb70@physik.fu-berlin.de>

On 12/11/20 12:41 PM, John Paul Adrian Glaubitz wrote:
> I'm currently bisecting the problem on a fast POWER server running a 32-bit Debian
> powerpc installation and will hopefully report back soonish.

Bisecting lead me to this change which is probably just hiding the real
problem:

(sid_powerpc-dchroot)glaubitz@perotto:~/guile-git$ git bisect good
a68c80c747a2a8ec92fa84684ebd60b4ecb7ffa0 is the first bad commit
commit a68c80c747a2a8ec92fa84684ebd60b4ecb7ffa0
Author: Andy Wingo <wingo@pobox.com>
Date:   Mon May 11 15:22:29 2020 +0200

    Switch to baseline compiler for bootstrap/

    * bootstrap/Makefile.am (GUILE_OPTIMIZATIONS): Add -Ono-cps so that we
      use the baseline compiler when bootstrapping.

 bootstrap/Makefile.am | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
(sid_powerpc-dchroot)glaubitz@perotto:~/guile-git$

I'll try to bisect again with "-Ono-cps" removed after it is introduced.

FWIW, there is a big-endian PowerPC machine available in the gcc compile
farm if anyone wants to help track down this issue [1].

Adrian

> [1] https://gcc.gnu.org/wiki/CompileFarm

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaubitz@debian.org
`. `'   Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913




  reply	other threads:[~2020-12-12 18:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-11 11:41 Regression on 32-bit big-endian targets John Paul Adrian Glaubitz
2020-12-12 18:55 ` John Paul Adrian Glaubitz [this message]
2020-12-12 20:25 ` John Paul Adrian Glaubitz
2020-12-12 20:36   ` John Paul Adrian Glaubitz

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=4ea37906-fddc-bad6-b29e-3ca1bf9b0c77@physik.fu-berlin.de \
    --to=glaubitz@physik.fu-berlin.de \
    --cc=guile-devel@gnu.org \
    /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).