public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jan.kratochvil at redhat dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/51695] [4.7 Regression] ICE while compiling argyllcms package Date: Wed, 04 Jan 2012 14:21:00 -0000 [thread overview] Message-ID: <bug-51695-4-PWfvnA69Ym@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-51695-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51695 --- Comment #5 from Jan Kratochvil <jan.kratochvil at redhat dot com> 2012-01-04 14:20:29 UTC --- (In reply to comment #4) > they could have unwanted > side-effects (reading uninitialized memory, division by zero, producing NaNs > etc.) that the debugger might complain about loudly. GDB will complain. > create a DW_TAG_dwarf_procedure for them and just replace those subexpressions > with DW_OP_call* to that procedure. DW_OP_call{2,4} is supported by GDB now. DW_TAG_dwarf_procedure is unsupported now but it looks like a "oneliner" patch, ping me for DW_TAG_dwarf_procedure implementation, please.
next prev parent reply other threads:[~2012-01-04 14:21 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-12-28 11:36 [Bug tree-optimization/51695] New: " jakub at gcc dot gnu.org 2011-12-28 11:30 ` [Bug debug/51695] " jakub at gcc dot gnu.org 2011-12-28 12:21 ` jakub at gcc dot gnu.org 2011-12-30 23:42 ` pinskia at gcc dot gnu.org 2012-01-04 11:05 ` jakub at gcc dot gnu.org 2012-01-04 11:26 ` jakub at gcc dot gnu.org 2012-01-04 13:53 ` rguenth at gcc dot gnu.org 2012-01-04 14:21 ` jan.kratochvil at redhat dot com [this message] 2012-01-04 19:58 ` jakub at gcc dot gnu.org 2012-01-05 6:50 ` [Bug debug/51695] NOTE_INSN_VAR_LOCATION notes are sometimes too large jakub at gcc dot gnu.org 2012-01-19 5:57 ` pinskia at gcc dot gnu.org 2012-02-09 17:19 ` jakub at gcc dot gnu.org 2012-03-22 9:01 ` rguenth at gcc dot gnu.org 2012-07-02 13:01 ` rguenth 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-51695-4-PWfvnA69Ym@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).