public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/17994] avr-gcc does not output a dwarf2 .debug_frame section Date: Wed, 16 Feb 2011 18:16:00 -0000 [thread overview] Message-ID: <bug-17994-4-6E5VE3kyUm@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-17994-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17994 --- Comment #9 from Richard Henderson <rth at gcc dot gnu.org> 2011-02-16 18:04:08 UTC --- > Going by the internals document, INCOMING_FRAME_SP_OFFSET is already defined > but it is not used anywhere (in my patch). Certainly it's going to be used by the generic code in dwarf2out_frame_init, and if that's wrong everything that follows will be off as well. > INCOMING_RETURN_ADDR_RTX per se is not using POST_DEC. But once they are > defined to some values, during the libgcc build, an ICE is hit in > dwarf2out_frame_debug_expr(). If POST_DEC mode is defined, ICE disappears. I am > yet to understand the relation between the POST_DEC and ICE and why it appears > when only CFI is being emitted. Ah, I see. Nothing to do with the initial frame setup, but the rest of the unwind info, since AVR uses POST_DEC for pushes. See http://gcc.gnu.org/ml/gcc-patches/2011-02/msg01059.html for my proposed patch for this. Note that the message contains both gas and gcc patches.
next prev parent reply other threads:[~2011-02-16 18:04 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-17994-4@http.gcc.gnu.org/bugzilla/> 2010-12-29 7:05 ` anitha.boyapati at atmel dot com 2010-12-29 7:08 ` anitha.boyapati at atmel dot com 2010-12-29 13:35 ` anitha.boyapati at atmel dot com 2011-02-15 19:39 ` rth at gcc dot gnu.org 2011-02-16 8:28 ` anitha.boyapati at atmel dot com 2011-02-16 18:16 ` rth at gcc dot gnu.org [this message] 2011-08-02 20:46 ` Torleif.Sandnes at atmel dot com 2011-08-02 20:50 ` rth at gcc dot gnu.org [not found] <bug-17994-9466@http.gcc.gnu.org/bugzilla/> 2009-08-20 22:40 ` eric dot weddington at atmel dot com 2009-10-23 11:41 ` tsandnes at atmel dot com 2004-10-14 8:22 [Bug debug/17994] New: " tsandnes at atmel dot com 2004-10-14 13:24 ` [Bug target/17994] " pinskia at gcc dot gnu dot org 2004-10-14 13:24 ` pinskia at gcc dot gnu dot org 2004-10-14 16:39 ` ericw at evcohs dot com 2004-11-13 16:17 ` berndtrog at yahoo dot com 2005-02-11 23:09 ` ericw at evcohs dot com 2005-03-16 16:54 ` ericw at evcohs dot com 2005-05-06 13:59 ` bjoern dot m dot haase at web dot de 2005-07-27 23:37 ` giovannibajo at libero dot it
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-17994-4-6E5VE3kyUm@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).