public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "css20 at mail dot ru" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/39738] GCC cannot build itself for win64 platform Date: Sun, 12 Apr 2009 08:50:00 -0000 [thread overview] Message-ID: <20090412085028.24782.qmail@sourceware.org> (raw) In-Reply-To: <bug-39738-17562@http.gcc.gnu.org/bugzilla/> ------- Comment #4 from css20 at mail dot ru 2009-04-12 08:50 ------- First tests of Win64 compiler.. simple source file test.c was created: #include "windows.h" int main(int argc, char **argv) { MessageBox(NULL, "test", "test", MB_OK); } E:\temp\test>gcc test.c gcc: CreateProcess: No such file or directory E:\temp\test>gcc -### test.c Using built-in specs. Target: x86_64-pc-mingw32 Configured with: ../src/configure --prefix=/usr/win64 --with-sysroot=/usr/win64 --host=x86_64-pc-mingw32 --target=x86_64-pc-mingw32 --enable-languages=c,c++ --d isable-win32-registry --disable-nls --disable-shared --disable-sjlj-exceptions - -with-dwarf2 --disable-libssp --enable-libgomp Thread model: win32 gcc version 4.4.0 20090407 (prerelease) (GCC) COLLECT_GCC_OPTIONS='-mtune=generic' "e:/mingw64/bin/../libexec/gcc/x86_64-pc-mingw32/4.4.0/cc1.exe" "-quiet" "-ipre fix" "e:\\mingw64\\bin\\../lib/gcc/x86_64-pc-mingw32/4.4.0/" "test.c" "-quiet" " -dumpbase" "test.c" "-mtune=generic" "-auxbase" "test" "-o" "C:\\Users\\X\\AppDa ta\\Local\\Temp\\cciH4k6g.s" COLLECT_GCC_OPTIONS='-mtune=generic' " \"" ------> <Here must be assembler path and arguments> then compiler drivers segfaults.. gdb output: Program received signal SIGSEGV, Segmentation fault. main (argc=3, argv=0x72120) at ../../src/gcc/gcc.c:6848 6848 in ../../src/gcc/gcc.c code from gcc.c(6848): /* Determine if there are any linker input files. */ num_linker_inputs = 0; for (i = 0; (int) i < n_infiles; i++) if (explicit_link_files[i] || outfiles[i] != NULL) num_linker_inputs++; (gdb) p outfiles[i] $12 = 0x72200 "test.c" (gdb) p explicit_link_files[i] No symbol "explicit_link_files" in current context - ??? disassembly listing: 000000000040DB7B cmp byte ptr [rbx+rcx],0 <--- rbx & rcx = 0 000000000040DB7F jne 000000000040DB88 000000000040DB81 cmp qword ptr [rdi+rcx*8],0 000000000040DB86 je 000000000040DB8B What is it, incorrect build or compiler driver bug ? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39738
next prev parent reply other threads:[~2009-04-12 8:50 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-04-11 15:00 [Bug libstdc++/39738] New: " css20 at mail dot ru 2009-04-11 18:47 ` [Bug libstdc++/39738] " paolo dot carlini at oracle dot com 2009-04-11 19:33 ` [Bug target/39738] " ktietz at gcc dot gnu dot org 2009-04-11 21:09 ` css20 at mail dot ru 2009-04-12 8:50 ` css20 at mail dot ru [this message] 2009-04-12 19:36 ` css20 at mail dot ru 2009-04-12 19:49 ` ktietz at gcc dot gnu dot org 2009-04-13 8:12 ` css20 at mail dot ru 2009-04-13 8:34 ` ktietz at gcc dot gnu dot org 2009-04-13 15:48 ` css20 at mail dot ru 2009-04-13 18:06 ` css20 at mail dot ru 2009-04-13 19:25 ` ktietz at gcc dot gnu dot org 2009-05-23 9:47 ` loaden at gmail dot com 2009-05-24 4:34 ` paolo dot carlini at oracle 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=20090412085028.24782.qmail@sourceware.org \ --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).