public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug d/103604] [12 Regression] trunk 20210506 fails to build in libphobos on mips64el-linux-gnu
Date: Wed, 15 Dec 2021 19:01:33 +0000	[thread overview]
Message-ID: <bug-103604-4-eckhCDvPdA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103604-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103604

--- Comment #21 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Iain Buclaw <ibuclaw@gcc.gnu.org>:

https://gcc.gnu.org/g:fd43568cc54e17c8b4a845677872c6282bc6dbb7

commit r12-6003-gfd43568cc54e17c8b4a845677872c6282bc6dbb7
Author: Iain Buclaw <ibuclaw@gdcproject.org>
Date:   Wed Dec 15 19:47:02 2021 +0100

    d: Merge upstream dmd 93108bb9e, druntime 6364e010, phobos 575b67a9b.

    D front-end changes:

        - Import dmd v2.098.1-beta.1.
        - Default extern(C++) compatibility to C++17.

    Druntime changes:

        - Import druntime v2.098.1-beta.1.
        - Fix definition of stat_t on MIPS64 (PR103604)

    Phobos changes:

        - Import phobos v2.098.1-beta.1.

    gcc/d/ChangeLog:

            * d-lang.cc (d_init_options): Set default -fextern-std= to C++17.
            * dmd/MERGE: Merge upstream dmd 93108bb9e.
            * gdc.texi (Runtime Options): Document the default for
-fextern-std=.

    libphobos/ChangeLog:

            PR d/103604
            * configure: Regenerate.
            * configure.ac (libtool_VERSION): Update to 3:0:0.
            * libdruntime/MERGE: Merge upstream druntime 6364e010.
            * src/MERGE: Merge upstream phobos 575b67a9b.
            * testsuite/libphobos.traits/all_satisfy.d: New test.
            * testsuite/libphobos.traits/traits.exp: New test.

  parent reply	other threads:[~2021-12-15 19:01 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-07 13:23 [Bug d/103604] New: " doko at debian dot org
2021-12-07 13:31 ` [Bug d/103604] " rguenth at gcc dot gnu.org
2021-12-07 13:41 ` marxin at gcc dot gnu.org
2021-12-13  1:56 ` syq at debian dot org
2021-12-13  7:56 ` syq at debian dot org
2021-12-13  8:02 ` syq at debian dot org
2021-12-13  8:16 ` ibuclaw at gcc dot gnu.org
2021-12-13 10:40 ` syq at debian dot org
2021-12-13 10:42 ` syq at debian dot org
2021-12-13 10:44 ` ibuclaw at gcc dot gnu.org
2021-12-13 11:01 ` syq at debian dot org
2021-12-13 16:25 ` ibuclaw at gdcproject dot org
2021-12-14  1:44 ` syq at debian dot org
2021-12-14  4:44 ` syq at debian dot org
2021-12-14  4:50 ` syq at debian dot org
2021-12-14 15:02 ` ibuclaw at gdcproject dot org
2021-12-14 15:06 ` ibuclaw at gdcproject dot org
2021-12-14 15:10 ` ibuclaw at gdcproject dot org
2021-12-14 15:28 ` syq at debian dot org
2021-12-14 15:58 ` ibuclaw at gdcproject dot org
2021-12-14 16:01 ` syq at debian dot org
2021-12-14 16:18 ` ibuclaw at gdcproject dot org
2021-12-15 19:01 ` cvs-commit at gcc dot gnu.org [this message]
2021-12-21 13:16 ` cvs-commit at gcc dot gnu.org
2021-12-21 13:17 ` cvs-commit at gcc dot gnu.org
2021-12-21 13:17 ` cvs-commit at gcc dot gnu.org
2021-12-21 13:19 ` ibuclaw at gdcproject dot org
2021-12-22  3:03 ` syq at debian dot org

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-103604-4-eckhCDvPdA@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.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).