public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "opensource at artnaseef dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/18929] Profiling optimized code causes segfaults on ARM due to missing frames Date: Fri, 10 Dec 2004 18:40:00 -0000 [thread overview] Message-ID: <20041210184026.29772.qmail@sourceware.org> (raw) In-Reply-To: <20041210181625.18929.opensource@artnaseef.com> ------- Additional Comments From opensource at artnaseef dot com 2004-12-10 18:40 ------- Subject: Re: Profiling optimized code causes segfaults on ARM due to missing frames I have not tested it, but I don't see why not. The patch is fairly short and straight-forward, I believe. ---------- Original Message ------------- Subject: [Bug target/18929] Profiling optimized code causes segfaults on ARM due to missing frames Date: 10 Dec 2004 18:20:04 -0000 From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: opensource@artnaseef.com ------- Additional Comments From pinskia at gcc dot gnu dot org 2004-12-10 18:20 ------- Does this work in 3.4.? -- What |Removed |Added ---------------------------------------------------------------------------- Component|c |target http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18929 ------- You are receiving this mail because: ------- You reported the bug, or are watching the reporter. You are on the CC list for the bug, or are watching someone who is. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18929
next prev parent reply other threads:[~2004-12-10 18:40 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-12-10 18:16 [Bug c/18929] New: " opensource at artnaseef dot com 2004-12-10 18:19 ` [Bug c/18929] " opensource at artnaseef dot com 2004-12-10 18:20 ` [Bug target/18929] " pinskia at gcc dot gnu dot org 2004-12-10 18:40 ` opensource at artnaseef dot com [this message] 2004-12-13 11:44 ` rearnsha at gcc dot gnu dot org 2004-12-13 15:28 ` opensource at artnaseef dot com 2004-12-13 15:46 ` Richard Earnshaw 2004-12-13 15:36 ` pinskia at gcc dot gnu dot org 2004-12-13 15:43 ` rearnsha at gcc dot gnu dot org 2004-12-13 15:56 ` opensource at artnaseef 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=20041210184026.29772.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).