public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/97956] [11 Regression] ICE in build2, at tree.c:4872 since r11-2709-g866626efd749ed3e
Date: Tue, 28 Feb 2023 17:09:23 +0000	[thread overview]
Message-ID: <bug-97956-4-LB6IvL1HR1@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97956-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to G. Steinmetz from comment #0)
> typedef __INT8_TYPE__ int8_t;
> typedef __INT32_TYPE__ int32_t;
> extern void* memchr (const void*, int, long);

For the record, the signature above is wrong (the third parameter should be
size_t not long), and that's what caused the ICE.

(So I think this should really be ice-on-invalid-code since it has a bad
declaration of memchr).

  parent reply	other threads:[~2023-02-28 17:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-23 16:38 [Bug c/97956] New: [11 Regression] ICE in build2, at tree.c:4872 gscfq@t-online.de
2020-11-23 18:24 ` [Bug tree-optimization/97956] [11 Regression] ICE in build2, at tree.c:4872 since r11-2709-g866626efd749ed3e marxin at gcc dot gnu.org
2020-11-24 20:23 ` msebor at gcc dot gnu.org
2020-11-25  0:46 ` msebor at gcc dot gnu.org
2020-11-25 18:02 ` cvs-commit at gcc dot gnu.org
2020-11-25 18:04 ` msebor at gcc dot gnu.org
2023-02-28 17:09 ` redi at gcc dot gnu.org [this message]
2023-03-02 13:42 ` cvs-commit 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-97956-4-LB6IvL1HR1@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).