public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/54793] the location of a formal_parameter is not started from a function entry with -mfentry Date: Fri, 25 Jan 2013 09:08:00 -0000 [thread overview] Message-ID: <bug-54793-4-LJLCsDyKWc@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-54793-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54793 --- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> 2013-01-25 09:08:14 UTC --- Well, we can also just use the first NOTE_INSN_BASIC_BLOCK resp. NOTE_INSN_FUNCTION_BEG, whichever comes first. The bigger problem with that ia64, pa and a few other targets use both PROLOGUE_BEFORE_EPILOGUE and non-default function_prologue hook, which emits some assembly stuff (even when they HAVE_prologue). Perhaps for those targets we'd need to emit the profiler code right away, and only postpone it until the first NOTE_INSN_BASIC_BLOCK/NOTE_INSN_FUNCTION_BEG if function_prologue hook is the default.
next prev parent reply other threads:[~2013-01-25 9:08 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-10-03 13:10 [Bug debug/54793] New: " masami.hiramatsu.pt at hitachi dot com 2012-10-03 13:49 ` [Bug debug/54793] " jakub at gcc dot gnu.org 2012-10-03 14:12 ` jakub at gcc dot gnu.org 2013-01-18 16:02 ` fche at redhat dot com 2013-01-24 19:12 ` aoliva at gcc dot gnu.org 2013-01-25 9:08 ` jakub at gcc dot gnu.org [this message] 2013-01-25 9:35 ` jakub at gcc dot gnu.org 2013-02-01 16:55 ` jakub at gcc dot gnu.org 2013-12-21 17:06 ` jakub 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-54793-4-LJLCsDyKWc@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).