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 target/34982] [4.3 regression] calling a function with undefined parameters causes segmentation fault at -O1 or higher Date: Sat, 26 Jan 2008 19:36:00 -0000 [thread overview] Message-ID: <20080126192347.28479.qmail@sourceware.org> (raw) In-Reply-To: <bug-34982-5606@http.gcc.gnu.org/bugzilla/> ------- Comment #4 from rguenth at gcc dot gnu dot org 2008-01-26 19:23 ------- So we use the local info before it is available and thus the following will ICE: Index: config/i386/i386.c =================================================================== --- config/i386/i386.c (revision 131861) +++ config/i386/i386.c (working copy) @@ -3199,6 +3199,7 @@ ix86_function_regparm (const_tree type, { /* FIXME: remove this CONST_CAST when cgraph.[ch] is constified. */ struct cgraph_local_info *i = cgraph_local_info (CONST_CAST_TREE(decl)); + gcc_assert (cgraph_node (CONST_CAST_TREE(decl))->analyzed); if (i && i->local) { int local_regparm, globals = 0, regno; and if it is just not available (i == NULL) might give inconsistent answers. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34982
next prev parent reply other threads:[~2008-01-26 19:24 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-01-26 17:41 [Bug c/34982] New: " bero at arklinux dot org 2008-01-26 19:05 ` [Bug target/34982] " rguenth at gcc dot gnu dot org 2008-01-26 19:20 ` rguenth at gcc dot gnu dot org 2008-01-26 19:22 ` rguenth at gcc dot gnu dot org 2008-01-26 19:36 ` rguenth at gcc dot gnu dot org [this message] 2008-01-26 21:56 ` hubicka at ucw dot cz 2008-01-27 15:35 ` hubicka at ucw dot cz 2008-01-27 17:21 ` rguenth at gcc dot gnu dot org 2008-01-27 18:20 ` hubicka at ucw dot cz 2008-01-27 19:40 ` hubicka at ucw dot cz 2008-01-27 19:57 ` bero at arklinux dot org 2008-01-29 19:46 ` hubicka at ucw dot cz 2008-01-29 23:22 ` jakub at gcc dot gnu dot org 2008-01-30 5:06 ` tromey at gcc dot gnu dot org 2008-01-30 15:06 ` steven at gcc dot gnu dot org 2008-01-30 16:05 ` hubicka at gcc dot gnu dot org 2008-01-30 16:12 ` hubicka at gcc dot gnu dot org 2008-01-30 16:22 ` hubicka at ucw dot cz 2008-01-30 23:19 ` dominiq at lps dot ens dot fr 2008-01-30 23:20 ` dominiq at lps dot ens dot fr 2008-01-30 23:21 ` pinskia at gcc dot gnu dot org 2008-01-31 0:06 ` dominiq at lps dot ens dot fr 2008-01-31 0:26 ` pinskia at gcc dot gnu dot org 2008-01-31 1:30 ` hubicka at ucw dot cz 2008-01-31 9:39 ` ubizjak at gmail 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=20080126192347.28479.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).