public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/62059] signed integer overflow in diagnostic.c adjust_line Date: Sun, 17 Aug 2014 16:20:00 -0000 [thread overview] Message-ID: <bug-62059-4-TWXp8F9yWv@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-62059-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62059 --- Comment #2 from Marek Polacek <mpolacek at gcc dot gnu.org> --- Author: mpolacek Date: Sun Aug 17 16:19:43 2014 New Revision: 214074 URL: https://gcc.gnu.org/viewcvs?rev=214074&root=gcc&view=rev Log: PR c/62059 * diagnostic.c (adjust_line): Add gcc_checking_assert. (diagnostic_show_locus): Don't print caret diagnostic if a column is larger than the line_width. Modified: trunk/gcc/ChangeLog trunk/gcc/diagnostic.c
next prev parent reply other threads:[~2014-08-17 16:20 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-08-08 8:10 [Bug c/62059] New: " zeccav at gmail dot com 2014-08-17 16:20 ` mpolacek at gcc dot gnu.org [this message] 2014-08-17 16:21 ` [Bug c/62059] " mpolacek 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-62059-4-TWXp8F9yWv@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).