public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/42667] [4.4/4.5 Regression] internal compiler error: in insert_into_preds_of_block, at tree-ssa-pre.c:3146 Date: Sat, 09 Jan 2010 11:25:00 -0000 [thread overview] Message-ID: <20100109112500.22463.qmail@sourceware.org> (raw) In-Reply-To: <bug-42667-18650@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from rguenth at gcc dot gnu dot org 2010-01-09 11:25 ------- Confirmed. We arrive at PRE with OnDisplay (char * string) { int D.1959; <bb 2>: if (string_2(D) == 0B) goto <bb 5>; else goto <bb 3>; <bb 5>: goto <bb 4>; <bb 3>: <bb 4>: # string_1 = PHI <string_2(D)(3), &"(none)"[0](5)> D.1959_4 = strlen (string_1); WriteTextDots (D.1959_4); return; note the missing conversion on the strlen return value assignment which misses already from the original frontend trees. This is because the builtin strlen has a proper prototype which is overridden by the invalid prototype extern int strlen(const char *); The PRE assert might look overeager here, but really only the missing gimple type verification saves us (I guess I didn't add that just because of similar issues). -- rguenth at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|major |normal Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Keywords| |ice-on-invalid-code Known to fail| |4.4.2 4.5.0 Known to work| |4.3.4 Last reconfirmed|0000-00-00 00:00:00 |2010-01-09 11:25:00 date| | Summary|internal compiler error: in |[4.4/4.5 Regression] |insert_into_preds_of_block, |internal compiler error: in |at tree-ssa-pre.c:3146 |insert_into_preds_of_block, | |at tree-ssa-pre.c:3146 Target Milestone|--- |4.4.3 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42667
next prev parent reply other threads:[~2010-01-09 11:25 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-01-09 6:05 [Bug c/42667] New: " jerstlouis at gmail dot com 2010-01-09 6:08 ` [Bug c/42667] " jerstlouis at gmail dot com 2010-01-09 11:25 ` rguenth at gcc dot gnu dot org [this message] 2010-01-09 12:07 ` [Bug middle-end/42667] [4.4/4.5 Regression] " rguenth at gcc dot gnu dot org 2010-01-10 19:38 ` rguenth at gcc dot gnu dot org 2010-01-10 19:39 ` [Bug middle-end/42667] [4.4 " rguenth at gcc dot gnu dot org 2010-01-13 18:25 ` jakub at gcc dot gnu dot org 2010-01-14 9:46 ` jakub at gcc dot gnu dot org 2010-01-14 12:09 ` jakub at gcc dot gnu 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=20100109112500.22463.qmail@sourceware.org \ --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: linkBe 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).