public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/55890] [4.7/4.8 Regression] calling a builtin func through a cast triggers an ICE
Date: Mon, 07 Jan 2013 09:54:00 -0000 [thread overview]
Message-ID: <bug-55890-4-Wlj6fc3Pk9@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55890-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55890
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Keywords| |ice-on-invalid-code
Last reconfirmed| |2013-01-07
Component|c |tree-optimization
AssignedTo|unassigned at gcc dot |rguenth at gcc dot gnu.org
|gnu.org |
Ever Confirmed|0 |1
Summary|calling a builtin func |[4.7/4.8 Regression]
|through a cast triggers an |calling a builtin func
|ICE |through a cast triggers an
| |ICE
Target Milestone|--- |4.7.3
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> 2013-01-07 09:53:24 UTC ---
Confirmed. Of course the testcase is somewhat "invalid". Since GCC 4.7
we preserve the original function type that is in effect for performing the
call but we are able to still propagate the actual function decl to the
call stmt. Code inspecting arguments based on the fact the called function
is a builtin decl needs additional verification now ...
Mine.
next prev parent reply other threads:[~2013-01-07 9:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-06 21:22 [Bug c/55890] New: " vapier at gentoo dot org
2013-01-07 9:54 ` rguenth at gcc dot gnu.org [this message]
2013-01-07 10:03 ` [Bug tree-optimization/55890] [4.7/4.8 Regression] " rguenth at gcc dot gnu.org
2013-01-07 11:22 ` rguenth at gcc dot gnu.org
2013-01-07 12:07 ` rguenth at gcc dot gnu.org
2013-01-07 15:35 ` rguenth at gcc dot gnu.org
2013-01-07 15:36 ` [Bug tree-optimization/55890] [4.7 " rguenth at gcc dot gnu.org
2013-01-07 15:56 ` rguenth at gcc dot gnu.org
2013-01-08 8:39 ` jakub at gcc dot gnu.org
2013-01-11 23:40 ` vries at gcc dot gnu.org
2013-02-04 12:05 ` rguenth at gcc dot gnu.org
2013-02-04 12:08 ` rguenth at gcc dot gnu.org
2013-02-04 15:50 ` rguenth at gcc dot gnu.org
2013-02-04 15:51 ` 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-55890-4-Wlj6fc3Pk9@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).