public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/49091] ice in evaluate_conditions_for_known_args Date: Sat, 04 Jun 2011 13:57:00 -0000 [thread overview] Message-ID: <bug-49091-4-AiMCdn0X7j@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-49091-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49091 --- Comment #2 from Jan Hubicka <hubicka at gcc dot gnu.org> 2011-06-04 13:56:00 UTC --- OK, the problem is K&R style definition: int ssetup(in, out, port) int *in, *out; int *port; { struct hostent *hp; struct servent *sp; struct sockaddr_in myaddr_in; struct sockaddr_in peeraddr_in; later used as: int server_sock_setup(in, out) int *in, *out; { return(ssetup(in, out)); } that is bug, too. I assumed that here we won't inline because of our type check mismatch. edge->call_stmt_cannot_inline_p is 0. This is because gimple_check_call_args actually allows decl to have more arguments than caller. Well, will fortify this at ipa-analysis side. Honza
next prev parent reply other threads:[~2011-06-04 13:57 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-05-20 18:48 [Bug c/49091] New: " dcb314 at hotmail dot com 2011-05-27 5:10 ` [Bug c/49091] " hjl.tools at gmail dot com 2011-06-04 13:57 ` hubicka at gcc dot gnu.org [this message] 2011-06-04 18:02 ` hubicka at gcc dot gnu.org 2011-06-04 18:09 ` hubicka 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-49091-4-AiMCdn0X7j@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: 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).