public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "Denis dot Excoffier at airbus dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/29826] New: __attribute__ dllimport makes optimization crash on cygwin Date: Tue, 14 Nov 2006 09:03:00 -0000 [thread overview] Message-ID: <bug-29826-12787@http.gcc.gnu.org/bugzilla/> (raw) the exact version of GCC is 4.1.1 the system type is i686-pc-cygwin the options given when GCC was configured/built: --prefix=/tmp/local/unixutil/gcc-4.1.1 --with-local-prefix=/usr/local/myCompanyName ("myCompanyName" is not the exact wording) (also, there is a symlink /tmp/local/unixutil/gcc -> gcc-4.1.1) the complete command line that triggers the bug: /tmp/local/unixutil/gcc/bin/gcc -O -Wall -Wextra -c zim.c the compiler output (error messages, warnings, etc.): stdout: nothing stderr: zim.c: In function 'ffff': zim.c:16: error: unrecognizable insn: (insn 20 19 21 2 (set (reg:SI 66) (const:SI (plus:SI (mem:SI (symbol_ref:SI ("#i.vvvv") <var_decl 0x194500b0 vvvv>) [0 S4 A8]) (const_int 4 [0x4])))) -1 (nil) (nil)) zim.c:16: internal compiler error: in extract_insn, at recog.c:2084 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. zim.o: not created the preprocessed file: see below additional remarks: 1) if "-O" is removed, all seems OK 2) if "__attribute__((dllimport))" is removed, all seems OK 3) if "-Wall" or "-Wextra" is removed, no change (still crash) ---zim.i----------------------------------------------------- # 1 "zim.c" # 1 "<built-in>" # 1 "<command line>" # 1 "zim.c" struct ssss { const char *xxxx1; const char *xxxx2; }; extern __attribute__((dllimport)) struct ssss vvvv[]; int zzzz(); int ffff() { int i; for (i = 0; i < 2; i++) { zzzz(vvvv[i].xxxx2); }; return(0); }; ------------------------------------------------------------- -- Summary: __attribute__ dllimport makes optimization crash on cygwin Product: gcc Version: 4.1.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: Denis dot Excoffier at airbus dot com GCC build triplet: i686-pc-cygwin GCC host triplet: i686-pc-cygwin GCC target triplet: i686-pc-cygwin http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29826
next reply other threads:[~2006-11-14 9:03 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-11-14 9:03 Denis dot Excoffier at airbus dot com [this message] 2006-11-14 11:39 ` [Bug c/29826] " Denis dot Excoffier at airbus dot com 2006-11-25 2:33 ` [Bug target/29826] " pinskia at gcc dot gnu dot org 2006-11-25 2:37 ` pinskia at gcc dot gnu dot org 2006-11-25 3:08 ` pinskia at gcc dot gnu dot org 2006-11-25 4:14 ` pinskia at gcc dot gnu dot org 2007-02-22 1:32 ` dannysmith at users dot sourceforge dot net 2007-03-20 15:20 ` pinskia at gcc dot gnu dot org 2007-03-20 15:21 ` pinskia at gcc dot gnu dot org 2007-03-25 17:20 ` pinskia at gcc dot gnu dot org 2007-04-03 8:54 ` dannysmith at users dot sourceforge dot net 2007-04-05 12:21 ` arcangelpip at hotmail dot com 2007-04-17 15:03 ` pinskia at gcc dot gnu dot org 2007-04-18 13:34 ` arcangelpip at hotmail dot com 2007-04-20 6:49 ` dannysmith at users dot sourceforge dot net 2007-04-20 16:06 ` arcangelpip at hotmail dot com 2007-04-22 1:01 ` dannysmith at users dot sourceforge dot net 2007-04-23 19:51 ` arcangelpip at hotmail dot com
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-29826-12787@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).