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/114655] [12 Regression] -flto=4 at link time does not override -flto=auto from compile time Date: Thu, 16 May 2024 09:56:07 +0000 [thread overview] Message-ID: <bug-114655-4-QafKh84DjU@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114655-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114655 --- Comment #5 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-12 branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:42a0393655d8e4662ba001c3759cf00b639eddb9 commit r12-10446-g42a0393655d8e4662ba001c3759cf00b639eddb9 Author: Richard Biener <rguenther@suse.de> Date: Tue Apr 9 14:25:57 2024 +0200 lto/114655 - -flto=4 at link time doesn't override -flto=auto at compile time The following adjusts -flto option processing in lto-wrapper to have link-time -flto override any compile time setting. PR lto/114655 * lto-wrapper.cc (merge_flto_options): Add force argument. (merge_and_complain): Do not force here. (run_gcc): But here to make the link-time -flto option override any compile-time one. (cherry picked from commit 32fb04adae90a0ea68e64e8fc3cb04b613b2e9f3)
next prev parent reply other threads:[~2024-05-16 9:56 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-09 12:24 [Bug lto/114655] New: " rguenth at gcc dot gnu.org 2024-04-09 12:24 ` [Bug lto/114655] " rguenth at gcc dot gnu.org 2024-04-09 12:52 ` rguenth at gcc dot gnu.org 2024-04-09 13:30 ` cvs-commit at gcc dot gnu.org 2024-04-09 13:31 ` [Bug lto/114655] [12/13 Regression] " rguenth at gcc dot gnu.org 2024-05-03 13:55 ` cvs-commit at gcc dot gnu.org 2024-05-16 9:56 ` cvs-commit at gcc dot gnu.org [this message] 2024-05-16 10:40 ` [Bug lto/114655] [12 " rguenth 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-114655-4-QafKh84DjU@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).