public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/45186] [4.6 Regression] Gfortran 4.5.0 emits wrong linenumbers Date: Wed, 29 Sep 2010 10:18:00 -0000 [thread overview] Message-ID: <20100929101800.sJuEOi9zunRTpEiI06op0S3TRYA4CLrQOSVLJllt2gA@z> (raw) In-Reply-To: <bug-45186-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45186 Tobias Burnus <burnus at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |burnus at gcc dot gnu.org --- Comment #22 from Tobias Burnus <burnus at gcc dot gnu.org> 2010-09-28 20:43:57 UTC --- Another case of off-by-one line numbers: http://gcc.gnu.org/ml/fortran/2010-09/msg00500.html For if (Gridded_resid_mask(4,4)) then ! Line 5 write(*,*) 'Boo' ! Line 6 The "if" is in the wrong line (6 instead of 5) - while the condition itself is in the correct line; i.e.: [ghghjh.f90 : 6] if ([ghghjh.f90 : 5] (*gridded_resid_mask)[[ghghjh.f90 : 5] (stride.2 + 1) * 4 + offset.3]) { [...] [ghghjh.f90 : 6] _gfortran_transfer_character ([ghghjh.f90 : 6] &dt_parm.7, [ghghjh.f90 : 6] &[ghghjh.f90 : 6] "Boo"[1]{lb: 1 sz: 1}, 3);
next parent reply other threads:[~2010-09-28 20:44 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-45186-4@http.gcc.gnu.org/bugzilla/> 2010-09-29 10:18 ` burnus at gcc dot gnu.org [this message] 2010-10-15 12:43 ` burnus at gcc dot gnu.org 2010-10-15 12:46 ` burnus at gcc dot gnu.org 2010-08-04 21:02 [Bug fortran/45186] New: " nikolay at totalviewtech dot com 2010-08-17 9:26 ` [Bug fortran/45186] [4.6 Regression] " jakub at gcc dot gnu dot org 2010-08-17 14:59 ` jv244 at cam dot ac dot uk 2010-09-02 11:15 ` rguenth at gcc dot gnu dot org 2010-09-02 14:04 ` burnus at gcc dot gnu dot org 2010-09-03 19:41 ` burnus at gcc dot gnu dot org 2010-09-05 18:10 ` burnus at gcc dot gnu dot org 2010-09-07 11:38 ` burnus at gcc dot gnu dot org 2010-09-07 15:32 ` burnus at gcc dot gnu dot org 2010-09-07 19:04 ` burnus at gcc dot gnu dot org 2010-09-09 19:33 ` burnus at gcc dot gnu dot org 2010-09-10 6:02 ` burnus at gcc dot gnu dot org 2010-09-10 6:36 ` jv244 at cam dot ac dot uk 2010-09-10 7:25 ` burnus 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=20100929101800.sJuEOi9zunRTpEiI06op0S3TRYA4CLrQOSVLJllt2gA@z \ --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).