public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/94131] [10 Regression] ICE: tree check: expected integer_cst, have plus_expr in get_len, at tree.h:5927 since r10-2814-g22fca489eaf98f26
Date: Wed, 11 Mar 2020 16:15:33 +0000	[thread overview]
Message-ID: <bug-94131-4-EOKtzhwki6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94131-4@http.gcc.gnu.org/bugzilla/>

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org

--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Slightly adjusted testcase that still ICEs the same way, without warnings:

void
foo (int x)
{
  char a[x];
  int b = (int) (__INTPTR_TYPE__) &a[0];

  __builtin_memset (a, '\0', sizeof (a));
  __builtin_printf ("%s", b ? &a[0] : "");
}

  parent reply	other threads:[~2020-03-11 16:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-11  2:35 [Bug tree-optimization/94131] New: [10 Regression] ICE: tree check: expected integer_cst, have plus_expr in get_len, at tree.h:5927 asolokha at gmx dot com
2020-03-11  8:01 ` [Bug tree-optimization/94131] " rguenth at gcc dot gnu.org
2020-03-11  9:34 ` [Bug tree-optimization/94131] [10 Regression] ICE: tree check: expected integer_cst, have plus_expr in get_len, at tree.h:5927 since r10-2814-g22fca489eaf98f26 marxin at gcc dot gnu.org
2020-03-11 16:15 ` jakub at gcc dot gnu.org [this message]
2020-03-11 16:47 ` jakub at gcc dot gnu.org
2020-03-11 21:40 ` msebor at gcc dot gnu.org
2020-03-18 20:55 ` msebor at gcc dot gnu.org
2020-03-25 15:40 ` cvs-commit at gcc dot gnu.org
2020-03-25 15:41 ` law at redhat dot com

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-94131-4-EOKtzhwki6@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).