public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "slyfox at inbox dot ru" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/95224] New: -flto -save-temps uses very unusual name for resolution file, looks arbitrary Date: Tue, 19 May 2020 21:54:44 +0000 [thread overview] Message-ID: <bug-95224-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95224 Bug ID: 95224 Summary: -flto -save-temps uses very unusual name for resolution file, looks arbitrary Product: gcc Version: 10.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: lto Assignee: unassigned at gcc dot gnu.org Reporter: slyfox at inbox dot ru CC: hubicka at gcc dot gnu.org, marxin at gcc dot gnu.org, rguenth at gcc dot gnu.org Target Milestone: --- Encountered when was debugging lto/95194. Reproducer: # good $ rm -- *; echo 'int main(){}' | gcc -c -x c -flto - -o main.o; gcc main.o -o main -flto -save-temps; ls -- *.res main.res # unexpected $ rm -- *; echo 'int main(){}' | gcc -c -x c -flto - -o main.o; gcc main.o -o main -flto -save-temps -lm; ls -- *.res -lm.res Expected behaviour: always get 'main.res' resolution file. In real scenario I was building 'genmatch' and got '-lm.res'. It confused me quite a bit: I explored very strange possibilities: driver did not recognize -lm as a library, '-lm.res' is not the only response file out there, etc. Would it be reasonable for response file to always use the same basename as '-o' paramemter?
next reply other threads:[~2020-05-19 21:54 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-19 21:54 slyfox at inbox dot ru [this message] 2020-05-20 6:48 ` [Bug lto/95224] " rguenth at gcc dot gnu.org 2020-06-08 21:17 ` aoliva at gcc dot gnu.org 2020-06-08 21:49 ` aoliva 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-95224-4@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).