public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug preprocessor/20907] [4.0/4.1 Regression] long comments throw off line numbers Date: Thu, 21 Apr 2005 18:40:00 -0000 [thread overview] Message-ID: <20050421184029.983.qmail@sourceware.org> (raw) In-Reply-To: <20050408191241.20907.dpatel@apple.com> ------- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-04-21 18:40 ------- Subject: Bug 20907 CVSROOT: /cvs/gcc Module name: gcc Branch: apple-local-200502-branch Changes by: dpatel@gcc.gnu.org 2005-04-21 18:40:08 Modified files: libcpp : line-map.c ChangeLog.apple-ppc gcc/testsuite : ChangeLog.apple-ppc Added files: gcc/testsuite/gcc.apple: very-long-comment.c Log message: Radar 4058553 Backport from FSF Mainline. 2005-04-19 Per Bothner <per@bothner.com> PR preprocessor/20907 * line-map.c (linemap_line_start): Fix bug when we need to increse column_bits but can re-use the current line_map. * gcc.apple/very-long-comment.c: New. Patches: http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libcpp/line-map.c.diff?cvsroot=gcc&only_with_tag=apple-local-200502-branch&r1=1.1&r2=1.1.52.1 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/libcpp/ChangeLog.apple-ppc.diff?cvsroot=gcc&only_with_tag=apple-local-200502-branch&r1=1.1.4.4&r2=1.1.4.5 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/gcc.apple/very-long-comment.c.diff?cvsroot=gcc&only_with_tag=apple-local-200502-branch&r1=NONE&r2=1.1.2.1 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/testsuite/ChangeLog.apple-ppc.diff?cvsroot=gcc&only_with_tag=apple-local-200502-branch&r1=1.1.4.22&r2=1.1.4.23 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20907
next prev parent reply other threads:[~2005-04-21 18:40 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-04-08 19:12 [Bug preprocessor/20907] New: " dpatel at apple dot com 2005-04-08 20:30 ` [Bug preprocessor/20907] [4.0/4.1 Regression] " pinskia at gcc dot gnu dot org 2005-04-08 20:34 ` pinskia at gcc dot gnu dot org 2005-04-08 20:37 ` pinskia at gcc dot gnu dot org 2005-04-19 21:30 ` bothner at gcc dot gnu dot org 2005-04-21 17:09 ` cvs-commit at gcc dot gnu dot org 2005-04-21 17:22 ` bothner at gcc dot gnu dot org 2005-04-21 17:27 ` dpatel at apple dot com 2005-04-21 18:40 ` cvs-commit at gcc dot gnu dot org [this message] 2005-04-24 20:05 ` [Bug preprocessor/20907] [4.0 " cvs-commit at gcc dot gnu dot org 2005-04-24 20:32 ` cvs-commit at gcc dot gnu dot org 2005-04-24 20:37 ` cvs-commit at gcc dot gnu dot org 2005-04-24 20:44 ` pinskia at gcc dot gnu dot 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=20050421184029.983.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).