public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/25328] [4.0/4.1 regression] ICE in get_indirect_ref_operands, at tree-ssa-operands.c:1453 Date: Wed, 21 Dec 2005 04:44:00 -0000 [thread overview] Message-ID: <20051221044431.14334.qmail@sourceware.org> (raw) In-Reply-To: <bug-25328-5724@http.gcc.gnu.org/bugzilla/> ------- Comment #6 from law at redhat dot com 2005-12-21 04:44 ------- Definitely a type problem. The Obj-C front-end is playing it too lose with types. main (argc, argv) { char msg[100]; int status; const unsigned char D.1189; char * msg.0; # BLOCK 0 # PRED: ENTRY (fallthru) # msg_3 = V_MUST_DEF <msg_2>; msg = ""; msg.0_4 = &msg; /* Mis-matched types here */ # VUSE <msg_3>; D.1189_5 = *msg.0_4; /* And again here. */ return; # SUCC: EXIT } I *think* the right code is that msg.0 should have type const unsigned char *. In the assignment to msg.0_4 the RHS should be casted to const unsigned char * This is a front-end problem as far as I can tell. Jeff -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25328
next prev parent reply other threads:[~2005-12-21 4:44 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-12-09 16:30 [Bug objc/25328] New: " debian-gcc at lists dot debian dot org 2005-12-09 17:00 ` [Bug middle-end/25328] " pinskia at gcc dot gnu dot org 2005-12-09 17:16 ` pinskia at gcc dot gnu dot org 2005-12-19 19:24 ` mmitchel at gcc dot gnu dot org 2005-12-20 21:33 ` law at redhat dot com 2005-12-21 4:33 ` law at redhat dot com 2005-12-21 4:44 ` law at redhat dot com [this message] 2005-12-22 9:33 ` jakub at gcc dot gnu dot org 2005-12-22 13:03 ` [Bug objc/25328] " jakub at gcc dot gnu dot org 2005-12-22 23:05 ` [Bug objc/25328] [4.0 " jakub at gcc dot gnu dot org 2005-12-22 23:07 ` jakub at gcc dot gnu dot org 2005-12-22 23:09 ` jakub at gcc dot gnu dot org 2005-12-22 23:10 ` 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=20051221044431.14334.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).