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/106129] [12 Regression] LTO option merging broken
Date: Wed, 27 Jul 2022 09:24:31 +0000	[thread overview]
Message-ID: <bug-106129-4-In05WBqDoH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106129-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106129

--- Comment #3 from CVS 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:d2892faac6d760ebc47f8f6ebee51e5cf6255cc8

commit r12-8628-gd2892faac6d760ebc47f8f6ebee51e5cf6255cc8
Author: Joseph Myers <joseph@codesourcery.com>
Date:   Thu Jun 30 16:41:40 2022 +0000

    lto: Fix option merging [PR106129]

    The LTO merging of options from different input files was broken by:

    commit 227a2ecf663d69972b851f51f1934d18927b62cd
    Author: Martin Liska <mliska@suse.cz>
    Date:   Fri Mar 12 11:53:47 2021 +0100

        lto-wrapper: Use vec<cl_decoded_option> data type.

    Previously, find_and_merge_options would merge options it read into
    those in *opts. After this commit, options in *opts on entry to
    find_and_merge_options are ignored; the only merging that takes place
    is between multiple sets of options in the same input file that are
    read in the same call to this function (not sure how that case can
    occur at all). The effects include, for example, that if some objects
    are built with PIC enabled and others with it disabled, and the last
    LTO object processed has PIC enabled, the choice of PIC for the last
    object will result in the whole program being built as PIC, when the
    merging logic is intended to ensure that a mixture of PIC and non-PIC
    objects results in the whole program being built as non-PIC.

    Fix this with an extra argument to find_and_merge_options to determine
    whether merging should take place.  This shows up a second issue with
    that commit (which I think wasn't actually intended to change code
    semantics at all): once merging is enabled again, the check for
    -Xassembler options became an infinite loop in the case where both
    inputs had -Xassembler options, with the same first option, so fix
    that loop to restore the previous semantics.

    Note that I'm not sure how LTO option merging might be tested in the
    testsuite (clearly there wasn't sufficient, if any, coverage to detect
    these bugs).

    Bootstrapped with no regressions for x86_64-pc-linux-gnu.

            PR lto/106129
            * lto-wrapper.cc (find_option): Add argument start.
            (merge_and_complain): Loop over existing_opt_index and
            existing_opt2_index for Xassembler check.  Update calls to
            find_option.
            (find_and_merge_options): Add argument first to determine whether
            to merge options with those passed in *opts.
            (run_gcc): Update calls to find_and_merge_options.

    (cherry picked from commit 8a8ee37a3325f1009034245676ef4e482c0444a2)

  parent reply	other threads:[~2022-07-27  9:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-28 22:42 [Bug lto/106129] New: [12/13 " jsm28 at gcc dot gnu.org
2022-06-29  9:51 ` [Bug lto/106129] " rguenth at gcc dot gnu.org
2022-06-30 16:42 ` cvs-commit at gcc dot gnu.org
2022-06-30 16:43 ` [Bug lto/106129] [12 " jsm28 at gcc dot gnu.org
2022-07-27  9:24 ` cvs-commit at gcc dot gnu.org [this message]
2022-07-27  9:25 ` 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-106129-4-In05WBqDoH@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).