unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: "Gábor Boskovits" <boskovits@gmail.com>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: gcc-ddc
Date: Mon, 29 Jan 2018 15:14:13 +0100	[thread overview]
Message-ID: <87vafkn45m.fsf@gnu.org> (raw)
In-Reply-To: <CAE4v=pgPZbW52X-TW0DcHAVnUP9_wuqkAiJy2GH3DvL4Fv0mGg@mail.gmail.com> ("Gábor Boskovits"'s message of "Mon, 29 Jan 2018 09:46:31 +0100")

Hello!

Gábor Boskovits <boskovits@gmail.com> skribis:

> Before FOSDEM I decided to take another look at this.
> I have really good news, gcc 4.7.4 ddc on x86_64 is now reproducible using
> clang.
> Code can be found at: https://github.com/Boskovits/guix/tree/gcc-ddc.

Woow, quite an achievement!

To be clear, this provides packages to perform DDC of GCC 4.7, right?

Did you choose 4.7 due to the fact that it’s the last C-only version?

> How could we go on with this?
>
> Now it is very experimental, and not conforming to policies.
> It is also architecture dependent.
>
> I don't think that this should go into upstream guix, because I don't
> believe it is useful for the general public. How should we get it into a
> place more generally available?

Perhaps there are pieces that (reproducibility fixes, etc.) that are
generally useful and could be merged directly.

As for the DDC packages, I don’t know.  It would probably require some
cleanup and discussion, but I think it would make sense to add it in
Guix proper.  That would allow Guix users to test their compiler through
DDC, which is not negligible.

Thanks,
Ludo’.

  reply	other threads:[~2018-01-29 14:14 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAE4v=phLKD_nOD2CeBB26H2wDcJuwQsg1Y09BprjMg_YQq2ahw@mail.gmail.com>
2017-11-20 18:24 ` gcc-ddc Jan Nieuwenhuizen
2017-11-20 22:14   ` gcc-ddc Ricardo Wurmus
2017-11-20 23:16     ` gcc-ddc Gábor Boskovits
2017-11-21 16:36       ` gcc-ddc Gábor Boskovits
2017-11-21 16:48       ` gcc-ddc Gábor Boskovits
2017-11-21 22:01         ` gcc-ddc Jan Nieuwenhuizen
2017-11-22 14:42         ` gcc-ddc Gábor Boskovits
2017-11-23  4:11           ` gcc-ddc Jan Nieuwenhuizen
2017-11-23  7:14           ` gcc-ddc Ricardo Wurmus
2017-11-23 11:23             ` gcc-ddc Gábor Boskovits
2017-11-29  9:43               ` gcc-ddc Gábor Boskovits
2017-11-29 12:26                 ` gcc-ddc Gábor Boskovits
2017-11-29 15:57                 ` gcc-ddc Jan Nieuwenhuizen
2017-11-30 14:32                   ` gcc-ddc Gábor Boskovits
2017-12-01 15:44                     ` gcc-ddc Gábor Boskovits
2017-12-02 14:48                       ` gcc-ddc Jan Nieuwenhuizen
2017-12-02 14:53                         ` gcc-ddc Gábor Boskovits
2017-12-02 22:44                         ` gcc-ddc Ricardo Wurmus
2018-01-29  8:46                           ` gcc-ddc Gábor Boskovits
2018-01-29 14:14                             ` Ludovic Courtès [this message]
2018-01-29 14:25                               ` gcc-ddc Ricardo Wurmus

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=87vafkn45m.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=boskovits@gmail.com \
    --cc=guix-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.
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).