public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/104333] [11/12 Regression] ICE with -flto -Wl,-plugin-opt=debug
Date: Wed, 02 Feb 2022 15:06:10 +0000 [thread overview]
Message-ID: <bug-104333-4-FeuQM2ae3u@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104333-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104333
--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Martin Liska <marxin@gcc.gnu.org>:
https://gcc.gnu.org/g:9a92e46c0e9a75cd14125493b8826d3e33dd0f67
commit r12-7002-g9a92e46c0e9a75cd14125493b8826d3e33dd0f67
Author: Martin Liska <mliska@suse.cz>
Date: Wed Feb 2 14:21:51 2022 +0100
lto: fix error handling for -Wl,-plugin-opt=debug
When one uses something like: -Wl,-plugin-opt=debug,
we end up with lto1 WPA invocation that has 'debug'
on command line. We interpret that as input filename.
The patch moves resolution checking later so that we end up with
a reasonable error message:
lto1: fatal error: open debug failed: No such file or directory
compilation terminated.
PR lto/104333
gcc/lto/ChangeLog:
* lto-common.cc (read_cgraph_and_symbols): Move resolution
checking for number of files later and report a reasonable
error message.
* lto-object.cc (lto_obj_file_open): Make error fatal.
next prev parent reply other threads:[~2022-02-02 15:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-01 18:28 [Bug lto/104333] New: " jakub at gcc dot gnu.org
2022-02-01 18:28 ` [Bug lto/104333] " jakub at gcc dot gnu.org
2022-02-02 9:41 ` marxin at gcc dot gnu.org
2022-02-02 10:01 ` marxin at gcc dot gnu.org
2022-02-02 10:01 ` marxin at gcc dot gnu.org
2022-02-02 13:11 ` marxin at gcc dot gnu.org
2022-02-02 15:06 ` cvs-commit at gcc dot gnu.org [this message]
2022-02-02 15:10 ` cvs-commit at gcc dot gnu.org
2022-02-02 15:10 ` marxin at gcc dot gnu.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-104333-4-FeuQM2ae3u@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).