public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tromey 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: Thu, 05 Jun 2014 03:09:00 -0000	[thread overview]
Message-ID: <bug-56724-4-R5VjxdrSMo@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 #12 from Tom Tromey <tromey at gcc dot gnu.org> ---
I noticed this patch today and tried it out on my current
test case, which uses -Wc++-compat... unfortunately it
still fails.

Test code:

extern void xfer (int, int, unsigned char *);

void call (int x, int y, void *arg)
{
  xfer (x, y, arg);
}


barimba. gcc --syntax-only -Wc++-compat /tmp/r.c
/tmp/r.c: In function ‘call’:
/tmp/r.c:5:3: warning: request for implicit conversion from ‘void *’ to
‘unsigned char *’ not permitted in C++ [-Wc++-compat]
   xfer (x, y, arg);
   ^


I think perhaps the problem is that the warning_at call in
convert_for_assignment that emits this warning should use
expr_loc rather than 'location'.  I haven't tested this theory.
>From gcc-bugs-return-453247-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jun 05 03:32:46 2014
Return-Path: <gcc-bugs-return-453247-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 27348 invoked by alias); 5 Jun 2014 03:32:45 -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 27292 invoked by uid 48); 5 Jun 2014 03:32:39 -0000
From: "amker.cheng at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/61411] [NEON] ICE in reload_cse_simplify_operands, at postreload.c:411
Date: Thu, 05 Jun 2014 03:32: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: 4.9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: amker.cheng at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-61411-4-dLCWOHBm5K@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61411-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61411-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-06/txt/msg00329.txt.bz2
Content-length: 912

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

bin.cheng <amker.cheng at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |amker.cheng at gmail dot com,
                   |                            |mshawcroft at gcc dot gnu.org,
                   |                            |vmakarov at gcc dot gnu.org

--- Comment #1 from bin.cheng <amker.cheng at gmail dot com> ---
The patch can fix the issue, but problem is why GCC/lra generated
register-indexing ([reg+reg]) addressing mode for V8HImode in the first place.
Since without this patch, the address expression is illegal and shouldn't be
generated.  I didn't look into LRA's code and am not very sure whether this
patch is covering the problem.

Also added Marcus and Vlad to the CC list.


  parent reply	other threads:[~2014-06-05  3:09 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
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 [this message]
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-R5VjxdrSMo@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).