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/56724] sub-optimal location in error
Date: Mon, 19 May 2014 18:47:00 -0000	[thread overview]
Message-ID: <bug-56724-4-EPQnl5PIVF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56724-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56724

--- Comment #9 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
(In reply to Tom Tromey from comment #5)
> I tried this today with a recent-ish gcc trunk build, and
> there's been a regression.
> 
> Now:
> 
> barimba. gcc --syntax-only r.c
> r.c: In function ‘docall’:
> r.c:7:10: warning: passing argument 3 of ‘callf’ from incompatible pointer
> type
>    return callf (23, 72,
>           ^
> r.c:3:5: note: expected ‘int (*)(double *)’ but argument is of type ‘int
> (*)(int *)’
>  int callf (int, int, int (*)(double *));
>      ^
> 
> 
> Note how the first warning now points to "callf", whereas
> in comment #0 it pointed to the actual argument causing the diagnostic.
> 
> The new situation is much worse for me as it prevents automated
> rewriting...

That is not a regression; previously it didn't point to the actual argument,
but it used input_location, so it pointed to the start of the line.  In the
previous testcase it only looks like it's pointing to the last argument.  E.g.
on this
int f (int *);

int callf (int, int, int (*)(double *));

int docall(void)
{
  return callf (23,
  72, f);
}

it will point to "72".

I hope I will have the cycles to look into this this week.
>From gcc-bugs-return-451957-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 19 18:52:01 2014
Return-Path: <gcc-bugs-return-451957-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 6582 invoked by alias); 19 May 2014 18:52:01 -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 6531 invoked by uid 48); 19 May 2014 18:51:56 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/61220] [4.10 Regression] ICE on valid code at -O2 on x86_64-linux-gnu in maybe_record_trace_start, at dwarf2cfi.c:2239
Date: Mon, 19 May 2014 18:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 4.10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 4.10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc short_desc
Message-ID: <bug-61220-4-Mu6diXChXD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61220-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61220-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: 2014-05/txt/msg01649.txt.bz2
Content-length: 828

https://gcc.gnu.org/bugzilla/show_bug.cgi?ida220

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org,
                   |                            |zqchen at gcc dot gnu.org
            Summary|ICE on valid code at -O2 on |[4.10 Regression] ICE on
                   |x86_64-linux-gnu in         |valid code at -O2 on
                   |maybe_record_trace_start,   |x86_64-linux-gnu in
                   |at dwarf2cfi.c:2239         |maybe_record_trace_start,
                   |                            |at dwarf2cfi.c:2239

--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Caused by r210457.


  parent reply	other threads:[~2014-05-19 18:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-56724-4@http.gcc.gnu.org/bugzilla/>
2013-03-25 18:45 ` pinskia at gcc dot gnu.org
2013-03-25 18:46 ` tromey at gcc dot gnu.org
2014-03-26  7:25 ` mpolacek at gcc dot gnu.org
2014-05-15 15:50 ` tromey at gcc dot gnu.org
2014-05-15 15:59 ` tromey at gcc dot gnu.org
2014-05-16 18:53 ` manu at gcc dot gnu.org
2014-05-19 18:47 ` mpolacek at gcc dot gnu.org [this message]
2014-05-25 15:40 ` mpolacek at gcc dot gnu.org
2014-05-27 20:15 ` mpolacek at gcc dot gnu.org
2014-06-05  3:09 ` tromey at gcc dot gnu.org
2014-06-05  5:41 ` mpolacek at gcc dot gnu.org
2014-06-05  9:35 ` mpolacek at gcc dot gnu.org
2014-09-11 14:36 ` mpolacek at gcc dot gnu.org
2015-04-22 12:01 ` jakub at gcc dot gnu.org
2015-07-16  9:15 ` rguenth 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-56724-4-EPQnl5PIVF@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).