public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/96058] ICE in c_getstr at gcc/fold-const.c:15475
Date: Tue, 07 Jul 2020 17:59:50 +0000 [thread overview]
Message-ID: <bug-96058-4-TmleE6hI4j@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96058-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96058
--- Comment #6 from Martin Sebor <msebor at gcc dot gnu.org> ---
The stack trace in comment #0:
during GIMPLE pass: strlen
../../chrome/browser/ui/views/sharing/sharing_icon_view.cc: In member function
‘GetVectorIconBadge’:
../../chrome/browser/ui/views/sharing/sharing_icon_view.cc:146: internal
compiler error: in tree_to_uhwi, at tree.h:4519
0x666aa8 tree_to_uhwi(tree_node const*)
../../gcc/tree.h:4519
0x666aa8 c_getstr(tree_node*, unsigned long*)
../../gcc/fold-const.c:15475
indicates that tree_to_uhwi() ICEs after a successful call to
tree_fits_uhwi_p():
if (!tree_fits_uhwi_p (mem_size))
return NULL;
/* STRING_LENGTH is the size of the string literal, including any
embedded NULs. STRING_SIZE is the size of the array the string
literal is stored in. */
unsigned HOST_WIDE_INT string_length = TREE_STRING_LENGTH (src);
unsigned HOST_WIDE_INT string_size = tree_to_uhwi (mem_size);
I don't see how that can ever happen. Am I misreading it? What's mem_size?
next prev parent reply other threads:[~2020-07-07 17:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-04 9:16 [Bug tree-optimization/96058] New: " marxin at gcc dot gnu.org
2020-07-04 9:19 ` [Bug tree-optimization/96058] " marxin at gcc dot gnu.org
2020-07-04 14:09 ` pinskia at gcc dot gnu.org
2020-07-04 16:33 ` marxin at gcc dot gnu.org
2020-07-06 7:19 ` rguenth at gcc dot gnu.org
2020-07-07 11:51 ` marxin at gcc dot gnu.org
2020-07-07 17:59 ` msebor at gcc dot gnu.org [this message]
2020-07-07 19:02 ` jakub at gcc dot gnu.org
2020-07-08 7:04 ` marxin at gcc dot gnu.org
2020-07-15 6:54 ` [Bug tree-optimization/96058] [10/11 Regression] " rguenth at gcc dot gnu.org
2020-07-23 6:51 ` rguenth at gcc dot gnu.org
2020-07-23 13:41 ` marxin at gcc dot gnu.org
2020-07-27 10:30 ` marxin at gcc dot gnu.org
2020-07-27 14:18 ` cvs-commit at gcc dot gnu.org
2020-07-27 14:22 ` [Bug tree-optimization/96058] [11 " marxin at gcc dot gnu.org
2020-07-28 10:37 ` cvs-commit at gcc dot gnu.org
2020-07-28 10:39 ` [Bug tree-optimization/96058] " marxin at gcc dot gnu.org
2020-08-18 6:47 ` asolokha at gmx dot com
2020-08-18 7:21 ` marxin at gcc dot gnu.org
2020-08-18 7:21 ` marxin 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-96058-4-TmleE6hI4j@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).