From: Jan Nieuwenhuizen <janneke@gnu.org>
To: "Gábor Boskovits" <boskovits@gmail.com>
Cc: um@mutluit.com, gcc-help@gcc.gnu.org, Guix-devel <guix-devel@gnu.org>
Subject: Re: gcc-4.7.4: libgcc2.h:157: error: unable to emulate 'TF'
Date: Tue, 10 Jul 2018 17:07:36 +0200 [thread overview]
Message-ID: <87sh4rm8nb.fsf@gnu.org> (raw)
In-Reply-To: <CAE4v=piZcS7d5=wu8j0i-yhdd+9go6bLo3pg-wN7WWXon2KhMA@mail.gmail.com> ("Gábor Boskovits"'s message of "Tue, 10 Jul 2018 09:31:53 +0200")
Gábor Boskovits writes:
> It seems that the errors you were getting are related to 128 bit
> floating point support. It also seems that 128 bit floating point
> support is enabled on 64 bits. I'm not sure about the 32 bit case
> though, do you get the same error there?
Ah! That makes me even more supicious... I was wondering about this
command
i386-unknown-linux-gcc ... -DIN_GCC -o _muldi3.o -c ../.././libgcc/libgcc2.c
this i386-unknown-linux-gcc compiler is the bootstrap compiler,
gcc-4.1.0 (or we may be able to use 2.95.3); is that OK? Shouldn't the
new `xgcc' compiler be used to compile libgcc2?
janneke
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com
next prev parent reply other threads:[~2018-07-10 15:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-09 16:57 gcc-4.7.4: libgcc2.h:157: error: unable to emulate 'TF' Jan Nieuwenhuizen
2018-07-09 18:28 ` U.Mutlu
2018-07-09 19:40 ` Jan Nieuwenhuizen
2018-07-10 3:52 ` U.Mutlu
2018-07-10 7:31 ` Gábor Boskovits
2018-07-10 15:07 ` Jan Nieuwenhuizen [this message]
2018-07-10 19:51 ` Jan Nieuwenhuizen
2018-07-10 20:19 ` Jonathan Wakely
[not found] ` <5B452C86.6090003@mutluit.com>
2018-07-11 17:01 ` SOLVED: " Jan Nieuwenhuizen
2018-07-11 18:06 ` U.Mutlu
2018-07-11 19:23 ` Jan Nieuwenhuizen
2018-07-10 15:02 ` Jan Nieuwenhuizen
2018-07-10 15:54 ` Danny Milosavljevic
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sh4rm8nb.fsf@gnu.org \
--to=janneke@gnu.org \
--cc=boskovits@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=guix-devel@gnu.org \
--cc=um@mutluit.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).