public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vapier at gentoo dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/55890] New: calling a builtin func through a cast triggers an ICE Date: Sun, 06 Jan 2013 21:22:00 -0000 [thread overview] Message-ID: <bug-55890-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55890 Bug #: 55890 Summary: calling a builtin func through a cast triggers an ICE Classification: Unclassified Product: gcc Version: 4.7.3 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c AssignedTo: unassigned@gcc.gnu.org ReportedBy: vapier@gentoo.org Target: x86_64-linux-gnu $ cat test.i extern void *memmove(void *, void *, long unsigned int); typedef int (*_TEST_fun_) (); static _TEST_fun_ i = (_TEST_fun_) memmove; main() { i(); } $ gcc-4.7.2 -O1 -c test.i test.i: In function ‘main’: test.i:4:1: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate.
next reply other threads:[~2013-01-06 21:22 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-01-06 21:22 vapier at gentoo dot org [this message] 2013-01-07 9:54 ` [Bug tree-optimization/55890] [4.7/4.8 Regression] " rguenth at gcc dot gnu.org 2013-01-07 10:03 ` 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@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: linkBe 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).