public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/56094] Invalid line number info generated with tree-level ivopts Date: Thu, 24 Jan 2013 18:30:00 -0000 [thread overview] Message-ID: <bug-56094-4-4rNTB2n74c@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-56094-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56094 Manuel López-Ibáñez <manu at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |manu at gcc dot gnu.org --- Comment #7 from Manuel López-Ibáñez <manu at gcc dot gnu.org> 2013-01-24 18:29:44 UTC --- Don't we have a EXPR_LOC_OR_UNKNOWN? That seems far nicer than overriding a global variable and restoring it back afterwards without known what else may be touching it or relying on it.
next prev parent reply other threads:[~2013-01-24 18:30 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-01-24 4:03 [Bug tree-optimization/56094] New: " josh.m.conner at gmail dot com 2013-01-24 4:04 ` [Bug tree-optimization/56094] " josh.m.conner at gmail dot com 2013-01-24 4:05 ` josh.m.conner at gmail dot com 2013-01-24 12:17 ` rguenth at gcc dot gnu.org 2013-01-24 14:19 ` jakub at gcc dot gnu.org 2013-01-24 15:06 ` jakub at gcc dot gnu.org 2013-01-24 17:27 ` jakub at gcc dot gnu.org 2013-01-24 18:30 ` manu at gcc dot gnu.org [this message] 2013-01-24 18:38 ` rguenther at suse dot de 2013-01-24 18:40 ` manu at gcc dot gnu.org 2013-01-24 19:31 ` rguenther at suse dot de 2013-01-24 20:50 ` manu at gcc dot gnu.org 2013-01-25 11:29 ` jakub at gcc dot gnu.org 2013-01-25 11:43 ` manu at gcc dot gnu.org 2013-01-25 12:05 ` jakub at gcc dot gnu.org 2013-01-28 8:56 ` rguenth at gcc dot gnu.org 2013-01-28 14:06 ` jakub at gcc dot gnu.org 2013-01-28 14:33 ` 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-56094-4-4rNTB2n74c@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).