public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "george.thomas at atmel dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/54218] Debug info for function parameters is incorrect when compiled with -O0 Date: Mon, 07 Jan 2013 12:04:00 -0000 [thread overview] Message-ID: <bug-54218-4-z58rXmz6RE@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-54218-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54218 --- Comment #5 from George Thomas <george.thomas at atmel dot com> 2013-01-07 12:04:22 UTC --- Created attachment 29095 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=29095 Draft Patch for the fix of 54218 The issue is happening because stack space is allocated twice 1. assign_params_setup_stack and 2. expand_used_vars The proposed fix is to allocate the space only once in assign_params_stack by explicitly checking in expand_used_vars if the tree node is of type PARM_DECL. if its PARM_DECL, it would mean that it would already have been expanded and hence do not require further expansion. This fixes the issue and allows debugging to work properly. I would like to know if it would be an acceptable change.
next prev parent reply other threads:[~2013-01-07 12:04 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-08-10 8:37 [Bug middle-end/54218] New: " senthil_kumar.selvaraj at atmel dot com 2012-08-10 8:54 ` [Bug middle-end/54218] " rguenth at gcc dot gnu.org 2012-08-10 10:24 ` senthil_kumar.selvaraj at atmel dot com 2012-08-10 10:25 ` senthil_kumar.selvaraj at atmel dot com 2012-08-10 10:39 ` senthil_kumar.selvaraj at atmel dot com 2013-01-07 12:04 ` george.thomas at atmel dot com [this message] 2013-01-07 12:06 ` george.thomas at atmel 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=bug-54218-4-z58rXmz6RE@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).