public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dongsheng.song at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/47241] lto not work on mingw32, reporting 'ld.exe: could not unlink output file' Date: Tue, 15 Feb 2011 01:30:00 -0000 [thread overview] Message-ID: <bug-47241-4-aIrjGnS8F2@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-47241-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47241 --- Comment #15 from Dongsheng Song <dongsheng.song at gmail dot com> 2011-02-15 01:25:18 UTC --- Created attachment 23345 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=23345 Hello.c.exe running with NULL pointer error
next prev parent reply other threads:[~2011-02-15 1:25 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-01-10 11:52 [Bug lto/47241] New: " coolypf at qq dot com 2011-01-10 14:37 ` [Bug lto/47241] " coolypf at qq dot com 2011-02-08 15:41 ` ktietz at gcc dot gnu.org 2011-02-09 3:57 ` coolypf at qq dot com 2011-02-09 8:16 ` ktietz at gcc dot gnu.org 2011-02-09 9:56 ` ktietz at gcc dot gnu.org 2011-02-09 13:10 ` coolypf at qq dot com 2011-02-09 13:50 ` ktietz at gcc dot gnu.org 2011-02-09 13:53 ` coolypf at qq dot com 2011-02-09 13:59 ` coolypf at qq dot com 2011-02-10 9:34 ` ktietz at gcc dot gnu.org 2011-02-11 3:01 ` dongsheng.song at gmail dot com 2011-02-11 10:01 ` ktietz at gcc dot gnu.org 2011-02-14 10:32 ` ktietz at gcc dot gnu.org 2011-02-15 1:25 ` dongsheng.song at gmail dot com 2011-02-15 1:30 ` dongsheng.song at gmail dot com [this message] 2011-02-15 2:46 ` dongsheng.song at gmail dot com 2011-02-15 4:55 ` dongsheng.song at gmail dot com 2011-02-15 8:15 ` ktietz at gcc dot gnu.org 2011-02-15 8:33 ` dongsheng.song at gmail 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-47241-4-aIrjGnS8F2@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).