From: dftxbs3e <dftxbs3e@free.fr>
To: 38459@debbugs.gnu.org
Subject: [bug#38459] [PATCH] gnu: (cross-gcc-arguments|gcc-boot0): Enable 128 bit long double for POWER9.
Date: Mon, 2 Dec 2019 21:03:06 +0100 [thread overview]
Message-ID: <0e9bb696-0165-82c8-799b-58ae72e382cc@free.fr> (raw)
In-Reply-To: <87h82its9y.fsf@nckx>
Yes, it should certainly be guarded by an if to avoid breaking other
platforms, even if it shouldnt hurt much.
Issue is I do not know Scheme enough to figure out the syntax for an
inline if like that. So I would appreciate if you could help me on that?
On 12/2/19 8:57 PM, Tobias Geerinckx-Rice via Guix-patches via wrote:
> dftxbs3e,
>
> dftxbs3e 写道:
>> This is to be applied against core-updates and fixes:
>>
>> $ guix build --target=powerpc64le-linux-gnu bootstrap-tarballs
>
> Thanks for sending this in! I'll be sure to merge it if no one else
> has objections.
>
> I'm really not familiar with this part of Guix, though. I'd naively
> expect this to be guarded with an (if …) so it only applies to POWER.
> (Why) is that not possible or desirable?
>
> Kind regards,
>
> T G-R
next prev parent reply other threads:[~2019-12-02 20:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-02 19:20 [bug#38459] [PATCH] gnu: (cross-gcc-arguments|gcc-boot0): Enable 128 bit long double for POWER9 dftxbs3e
2019-12-02 19:57 ` Tobias Geerinckx-Rice via Guix-patches via
2019-12-02 20:03 ` dftxbs3e [this message]
2019-12-07 19:28 ` dftxbs3e
2019-12-11 0:04 ` Tobias Geerinckx-Rice via Guix-patches via
2020-11-20 23:21 ` dftxbs3e
2020-11-26 22:28 ` bug#38459: " Ludovic Courtès
2020-11-20 23:30 ` [bug#38459] " dftxbs3e
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=0e9bb696-0165-82c8-799b-58ae72e382cc@free.fr \
--to=dftxbs3e@free.fr \
--cc=38459@debbugs.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.
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).