public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ibuclaw at gdcproject dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/111537] ICE: in set_cell_span, at text-art/table.cc:148 with D front-end and -fanalyzer
Date: Fri, 13 Oct 2023 16:25:36 +0000 [thread overview]
Message-ID: <bug-111537-4-wXhc5WstmA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111537-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111537
--- Comment #9 from Iain Buclaw <ibuclaw at gdcproject dot org> ---
(In reply to Iain Buclaw from comment #8)
> I see in the olden days when D sat outside of GCC, this is what was done too.
>
> https://github.com/D-Programming-GDC/gdc/commit/
> b9d36fc9d71ec4122d1c986599d87c6cb91ca55c
Although thinking it over, that did not take into consideration wide character
literals. The number of 0's at the end of the raw string in STRING_CST nodes
would need to be the same as the width of the type it's representing - one,
two, or four 0's for char, wchar and dchar respectively.
next prev parent reply other threads:[~2023-10-13 16:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-22 10:31 [Bug analyzer/111537] New: " ibuclaw at gdcproject dot org
2023-10-10 21:51 ` [Bug analyzer/111537] " dmalcolm at gcc dot gnu.org
2023-10-11 16:33 ` ibuclaw at gdcproject dot org
2023-10-11 17:47 ` dmalcolm at gcc dot gnu.org
2023-10-11 17:48 ` dmalcolm at gcc dot gnu.org
2023-10-11 18:27 ` dmalcolm at gcc dot gnu.org
2023-10-11 18:29 ` dmalcolm at gcc dot gnu.org
2023-10-11 20:05 ` ibuclaw at gdcproject dot org
2023-10-11 20:49 ` ibuclaw at gdcproject dot org
2023-10-13 16:25 ` ibuclaw at gdcproject dot org [this message]
2023-10-13 16:43 ` [Bug d/111537] " ibuclaw at gcc dot gnu.org
2023-10-14 12:22 ` cvs-commit at gcc dot gnu.org
2023-10-14 12:27 ` ibuclaw at gcc dot gnu.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-111537-4-wXhc5WstmA@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).