public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jv244 at cam dot ac dot uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/38113]  New: -Warray-temporaries output
Date: Fri, 14 Nov 2008 08:55:00 -0000	[thread overview]
Message-ID: <bug-38113-6642@http.gcc.gnu.org/bugzilla/> (raw)

The output of -Warray-temporaries could be enhanced:


      CALL fft_1dm ( fft_type, sign, .TRUE., n(2), mx2*mz2, abuf, bbuf, 1.0_lp
)
                                                                1
Warning: Creating array temporary at (1)


I.e. the (1) should maybe point to the variable instead of the ',' so that it
is clear if abuf or bbuf is the offender.


-- 
           Summary: -Warray-temporaries output
           Product: gcc
           Version: 4.4.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: jv244 at cam dot ac dot uk


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


             reply	other threads:[~2008-11-14  8:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-14  8:55 jv244 at cam dot ac dot uk [this message]
2008-11-28 21:14 ` [Bug fortran/38113] on warning/error: skip whitespaces, move position marker to actual variable name dfranke at gcc dot gnu dot org
2008-12-15 14:49 ` mikael at gcc dot gnu dot org
2008-12-21 15:48 ` mikael at gcc dot gnu dot org
2008-12-27 18:14 ` mikael at gcc dot gnu dot org
2009-01-20 20:00 ` mikael at gcc dot gnu dot org
2009-01-20 21:02 ` kargl at gcc dot gnu dot org
2009-01-20 22:37 ` mikael 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=bug-38113-6642@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: 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).