public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rainer@emrich-ebersheim.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/65582] [5 Regression] testsuite lto issue: xgcc.exe: warning: '-x lto' after last input file has no effect, fatal error: no input files
Date: Thu, 26 Mar 2015 14:21:00 -0000 [thread overview]
Message-ID: <bug-65582-4-KH59N0XrpU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65582-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65582
--- Comment #3 from Rainer Emrich <rainer@emrich-ebersheim.de> ---
(In reply to Richard Biener from comment #2)
> Huh, can you reproduce that with an installed compiler? It seems to simply
> build a single source file with -flto. Maybe it's some issue with dir
> separators
> in lto-wrapper or the linker plugin? Does it reproduce with
> -f[no-]linker-plugin
> or without -flto-partition=none?
I guess it's related to PR65582. So we first have to sort out the mingw-w64
issue.
next prev parent reply other threads:[~2015-03-26 13:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-26 12:28 [Bug target/65582] New: " rainer@emrich-ebersheim.de
2015-03-26 12:30 ` [Bug target/65582] [5 Regression] " rainer@emrich-ebersheim.de
2015-03-26 12:41 ` rguenth at gcc dot gnu.org
2015-03-26 14:21 ` rainer@emrich-ebersheim.de [this message]
2015-03-26 14:23 ` rainer@emrich-ebersheim.de
2015-03-31 13:16 ` rguenth at gcc dot gnu.org
2015-04-06 19:34 ` rainer@emrich-ebersheim.de
2015-04-22 11:57 ` [Bug target/65582] [5/6 " jakub at gcc dot gnu.org
2015-04-30 13:45 ` rainer@emrich-ebersheim.de
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-65582-4-KH59N0XrpU@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: link
Be 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).