public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "krebbel at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/42874] New: Error on correct code Date: Tue, 26 Jan 2010 15:58:00 -0000 [thread overview] Message-ID: <bug-42874-11173@http.gcc.gnu.org/bugzilla/> (raw) [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain, Size: 1018 bytes --] The following testcase fails with: sorry, unimplemented: function foo can never be copied because it uses variable sized variables When compiled with at least -O1. It works fine with GCC 4.4.3. void __attribute__ ((always_inline)) foo (const unsigned long *addr, unsigned long size) { typedef struct { long x[size]; } addrtype; addrtype *a = (void *) addr; } Unfortunately these patterns are quite common in the Linux kernel - at least for S/390. They always used to compile but mainline currently is not able to build the kernel. -- Summary: Error on correct code Product: gcc Version: 4.5.0 Status: UNCONFIRMED Severity: major Priority: P3 Component: c AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: krebbel at gcc dot gnu dot org GCC build triplet: s390x-ibm-linux GCC host triplet: s390x-ibm-linux GCC target triplet: s390x-ibm-linux http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42874
next reply other threads:[~2010-01-26 15:58 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-01-26 15:58 krebbel at gcc dot gnu dot org [this message] 2010-01-26 22:32 ` [Bug middle-end/42874] [4.5 Regression] Error on correct code: sorry, unimplemented: function foo can never be copied because it uses rguenth at gcc dot gnu dot org 2010-01-27 8:39 ` jakub at gcc dot gnu dot org 2010-01-27 8:43 ` pinskia at gcc dot gnu dot org 2010-01-27 8:51 ` jakub at gcc dot gnu dot org 2010-01-27 9:08 ` jakub at gcc dot gnu dot org 2010-01-27 10:24 ` rguenth at gcc dot gnu dot org 2010-01-27 15:10 ` jakub at gcc dot gnu dot org 2010-01-27 15:21 ` jakub at gcc dot gnu dot org 2010-02-07 4:46 ` hjl 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-42874-11173@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).