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/98921] [11 regression] libphobos: junk in generated symbol
Date: Tue, 02 Feb 2021 01:56:12 +0000	[thread overview]
Message-ID: <bug-98921-4-FCQ9ppNXN1@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98921-4@http.gcc.gnu.org/bugzilla/>

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

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

https://gcc.gnu.org/g:38c2d9598b1b2f23b24f96fd8f58a89344b93609

commit r10-9334-g38c2d9598b1b2f23b24f96fd8f58a89344b93609
Author: Iain Buclaw <ibuclaw@gdcproject.org>
Date:   Tue Feb 2 00:52:49 2021 +0100

    d: Fix junk in generated symbol on powerpc64-*-* [PR98921]

    This adds a special formatter to OutBuffer to handle formatted printing
    of integers, a common case.  The replacement is faster and safer.

    In dmangle.c, it also gets rid of a number of problematic casts, as seen
    on powerpc64 targets.

    gcc/d/ChangeLog:

            PR d/98921
            * dmd/dmangle.c (Mangler::visit (TypeSArray *)): Use buf->print
              to format integer value.
            (Mangler::visit (TypeIdentifier *)): Likewise.
            (Mangler::toBuffer): Likewise.
            (Mangler::visit (IntegerExp *)): Likewise.
            (Mangler::visit (StringExp *)): Likewise.
            (Mangler::visit (ArrayLiteralExp *)): Likewise.
            (Mangler::visit (AssocArrayLiteralExp *)): Likewise.
            (Mangler::visit (StructLiteralExp *)): Likewise.
            * dmd/root/outbuffer.c (OutBuffer::print): New function.
            * dmd/root/outbuffer.h (OutBuffer::print): Declare.

    (cherry picked from commit 6a481021a65d6237b0c509a76fcd9c1f32c4558e)

  parent reply	other threads:[~2021-02-02  1:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-01 17:04 [Bug d/98921] New: " schwab@linux-m68k.org
2021-02-01 17:13 ` [Bug d/98921] " schwab@linux-m68k.org
2021-02-01 17:53 ` schwab@linux-m68k.org
2021-02-01 17:55 ` schwab@linux-m68k.org
2021-02-02  0:22 ` ibuclaw at gdcproject dot org
2021-02-02  1:18 ` cvs-commit at gcc dot gnu.org
2021-02-02  1:56 ` cvs-commit at gcc dot gnu.org [this message]
2021-02-02  1:56 ` cvs-commit at gcc dot gnu.org
2021-02-02  1:59 ` ibuclaw at gdcproject 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-98921-4-FCQ9ppNXN1@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).