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/105544] gdc fails to compile d source from stdin
Date: Tue, 31 May 2022 16:32:59 +0000	[thread overview]
Message-ID: <bug-105544-4-8x9sutnbx8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105544-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #12 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:a0bc7fd42136f124726985b1ab4dcde739cd260e

commit r13-867-ga0bc7fd42136f124726985b1ab4dcde739cd260e
Author: Iain Buclaw <ibuclaw@gdcproject.org>
Date:   Tue May 31 14:45:02 2022 +0200

    d: Fix D lexer sometimes fails to compile code read from stdin

    As of gdc-12, the lexer expects there 4 bytes of zero padding at the end
    of the source buffer to mark the end of input.  Sometimes when reading
    from stdin, the data at the end of input is garbage rather than zeroes.
    Fix that by explicitly calling memset past the end of the buffer.

            PR d/105544

    gcc/d/ChangeLog:

            * d-lang.cc (d_parse_file): Zero padding past the end of the stdin
            buffer so the D lexer has a sentinel to stop parsing at.

  parent reply	other threads:[~2022-05-31 16:32 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-10  9:33 [Bug d/105544] New: " fabian@ritter-vogt.de
2022-05-10  9:34 ` [Bug d/105544] " fabian@ritter-vogt.de
2022-05-10  9:35 ` marxin at gcc dot gnu.org
2022-05-10 12:11 ` ibuclaw at gcc dot gnu.org
2022-05-10 12:14 ` marxin at gcc dot gnu.org
2022-05-11 22:06 ` ibuclaw at gcc dot gnu.org
2022-05-12  6:58 ` marxin at gcc dot gnu.org
2022-05-12  7:39 ` fabian@ritter-vogt.de
2022-05-12  7:47 ` marxin at gcc dot gnu.org
2022-05-12  9:32 ` ibuclaw at gcc dot gnu.org
2022-05-12  9:44 ` fabian@ritter-vogt.de
2022-05-12 12:58 ` ibuclaw at gcc dot gnu.org
2022-05-12 13:18 ` fabian@ritter-vogt.de
2022-05-31 16:32 ` cvs-commit at gcc dot gnu.org [this message]
2022-05-31 16:33 ` cvs-commit at gcc dot gnu.org
2022-05-31 16:37 ` 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-105544-4-8x9sutnbx8@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).