public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mtewoodbury at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug preprocessor/58687] "#line __LINE__ ..." changes subsequent line numbers Date: Mon, 04 Nov 2013 14:14:00 -0000 [thread overview] Message-ID: <bug-58687-4-nhpTpeE7DD@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-58687-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58687 --- Comment #15 from Max TenEyck Woodbury <mtewoodbury at gmail dot com> --- Could you all give me some idea on how soon this might be applied?
next prev parent reply other threads:[~2013-11-04 14:14 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-10-11 3:47 [Bug preprocessor/58687] New: " mtewoodbury at gmail dot com 2013-10-23 7:16 ` [Bug preprocessor/58687] " mtewoodbury at gmail dot com 2013-10-25 19:01 ` mtewoodbury at gmail dot com 2013-10-25 22:56 ` mtewoodbury at gmail dot com 2013-10-26 13:39 ` mtewoodbury at gmail dot com 2013-10-26 21:15 ` pinskia at gcc dot gnu.org 2013-10-27 13:59 ` mtewoodbury at gmail dot com 2013-10-28 17:51 ` mtewoodbury at gmail dot com 2013-10-28 18:53 ` joseph at codesourcery dot com 2013-10-30 7:39 ` mtewoodbury at gmail dot com 2013-10-30 15:08 ` manu at gcc dot gnu.org 2013-10-30 17:59 ` mtewoodbury at gmail dot com 2013-10-30 18:13 ` joseph at codesourcery dot com 2013-10-30 19:43 ` mtewoodbury at gmail dot com 2013-10-31 18:00 ` mtewoodbury at gmail dot com 2013-11-04 14:14 ` mtewoodbury at gmail dot com [this message] 2013-11-04 18:18 ` joseph at codesourcery dot com 2013-11-19 16:08 ` mtewoodbury at gmail dot com 2013-11-19 16:37 ` joseph at codesourcery dot com 2013-11-28 22:52 ` jsm28 at gcc dot gnu.org 2013-11-29 4:52 ` mtewoodbury at gmail dot com 2013-11-29 16:57 ` joseph at codesourcery dot com 2013-11-29 22:49 ` mtewoodbury at gmail dot com 2013-11-30 0:04 ` joseph at codesourcery 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=bug-58687-4-nhpTpeE7DD@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).