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 debug/67192] [6 Regression] Backward-goto in loop can get wrong line number Date: Fri, 09 Oct 2015 10:58:00 -0000 [thread overview] Message-ID: <bug-67192-4-XoDDR0B2fX@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-67192-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67192 --- Comment #17 from Manuel López-Ibáñez <manu at gcc dot gnu.org> --- (In reply to Andreas Arnez from comment #16) > Well, I'm rather a GDB- than a GCC developer. My interest in this is to > ensure that GDB doesn't become completely useless ;-) > Also, I thought that David was a better candidate for fixing this because > his patch introduced the regression. I cannot force anyone to do anything, I was just pointing out what would be a good strategy to get the result that you want. > Anyway, if it helps speeding this up, and if nobody objects, I could give it > a try. In this case I actually lean towards your suggestion from comment Nobody will ever object to people fixing bugs ;) > #13, to pass an explicit location to c_finish_loop. Somehow I don't like > adding a function like c_parser_peek_token_keep_input_location and then > using it only for this fix, just to get rid of it in the long run. (Right?) Sure, I haven't looked at implications of both solutions in detail. The thing to remember is that the only people you need to convince are the MAINTAINERS of C FE. If you have never contributed to GCC, this may be useful: https://gcc.gnu.org/wiki/GettingStarted#Basics:_Contributing_to_GCC_in_10_easy_steps You may also send a WIP patch to gcc-patches@ and CC the C FE maintainers, just to get some early feedback. >From gcc-bugs-return-499085-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Oct 09 10:59:11 2015 Return-Path: <gcc-bugs-return-499085-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 31203 invoked by alias); 9 Oct 2015 10:59:11 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: <gcc-bugs.gcc.gnu.org> List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/> List-Post: <mailto:gcc-bugs@gcc.gnu.org> List-Help: <mailto:gcc-bugs-help@gcc.gnu.org> Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 31155 invoked by uid 48); 9 Oct 2015 10:59:07 -0000 From: "ramana at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/67366] Poor assembly generation for unaligned memory accesses on ARM v6 & v7 cpus Date: Fri, 09 Oct 2015 10:59:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 6.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: ramana at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 6.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution target_milestone Message-ID: <bug-67366-4-Z67BhP3OSt@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-67366-4@http.gcc.gnu.org/bugzilla/> References: <bug-67366-4@http.gcc.gnu.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2015-10/txt/msg00640.txt.bz2 Content-length: 535 https://gcc.gnu.org/bugzilla/show_bug.cgi?idg366 Ramana Radhakrishnan <ramana at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED Target Milestone|--- |6.0 --- Comment #14 from Ramana Radhakrishnan <ramana at gcc dot gnu.org> --- Fixed on trunk - Yann please try and let us know.
next prev parent reply other threads:[~2015-10-09 10:58 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-08-12 14:56 [Bug debug/67192] New: " arnez at linux dot vnet.ibm.com 2015-08-17 15:30 ` [Bug debug/67192] " arnez at linux dot vnet.ibm.com 2015-08-18 15:23 ` dmalcolm at gcc dot gnu.org 2015-08-18 15:52 ` dmalcolm at gcc dot gnu.org 2015-08-18 16:05 ` dmalcolm at gcc dot gnu.org 2015-08-18 16:11 ` dmalcolm at gcc dot gnu.org 2015-08-18 16:23 ` dmalcolm at gcc dot gnu.org 2015-08-18 17:16 ` arnez at linux dot vnet.ibm.com 2015-08-18 19:56 ` manu at gcc dot gnu.org 2015-08-18 20:07 ` ppalka at gcc dot gnu.org 2015-09-11 18:17 ` arnez at linux dot vnet.ibm.com 2015-09-23 1:31 ` ppalka at gcc dot gnu.org 2015-09-23 7:02 ` manu at gcc dot gnu.org 2015-10-08 16:40 ` [Bug debug/67192] [6 Regression] " manu at gcc dot gnu.org 2015-10-09 10:49 ` arnez at linux dot vnet.ibm.com 2015-10-09 10:58 ` manu at gcc dot gnu.org [this message] 2015-10-09 11:11 ` manu at gcc dot gnu.org 2015-10-12 14:32 ` arnez at linux dot vnet.ibm.com 2015-10-23 15:32 ` arnez at linux dot vnet.ibm.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-67192-4-XoDDR0B2fX@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).