public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aldyh at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/40660] [4.5 Regression] Weird break points with 4.5, works with 4.4
Date: Tue, 25 Aug 2009 00:28:00 -0000	[thread overview]
Message-ID: <20090825002817.5671.qmail@sourceware.org> (raw)
In-Reply-To: <bug-40660-13404@http.gcc.gnu.org/bugzilla/>



------- Comment #11 from aldyh at gcc dot gnu dot org  2009-08-25 00:28 -------
Subject: Bug 40660

Author: aldyh
Date: Tue Aug 25 00:27:52 2009
New Revision: 151069

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=151069
Log:
fortran/
        PR fortran/40660
        * trans-io.c (build_dt): Pass UNKNOWN_LOCATION to build_call_expr_loc.
        (transfer_array_desc): Same.


Added:
    trunk/gcc/testsuite/gfortran.dg/PR40660.f90
Modified:
    trunk/gcc/fortran/ChangeLog
    trunk/gcc/fortran/trans-io.c


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40660


  parent reply	other threads:[~2009-08-25  0:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-06 16:10 [Bug debug/40660] New: [4.5 Regression] Wierd " burnus at gcc dot gnu dot org
2009-07-15  7:28 ` [Bug debug/40660] " steven at gcc dot gnu dot org
2009-07-15  7:28 ` steven at gcc dot gnu dot org
2009-07-29 22:52 ` jsm28 at gcc dot gnu dot org
2009-08-07 14:41 ` burnus at gcc dot gnu dot org
2009-08-07 17:28 ` jv244 at cam dot ac dot uk
2009-08-14 13:36 ` burnus at gcc dot gnu dot org
2009-08-21 18:04 ` burnus at gcc dot gnu dot org
2009-08-21 18:34 ` burnus at gcc dot gnu dot org
2009-08-21 21:11 ` aldyh at gcc dot gnu dot org
2009-08-22  9:38 ` burnus at gcc dot gnu dot org
2009-08-24 18:34 ` [Bug debug/40660] [4.5 Regression] Weird " aldyh at gcc dot gnu dot org
2009-08-24 19:05 ` jv244 at cam dot ac dot uk
2009-08-25  0:28 ` aldyh at gcc dot gnu dot org [this message]
2009-09-03  6:50 ` jv244 at cam dot ac dot uk

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=20090825002817.5671.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: link
Be 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).