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 target/104871] macosx-version-min wrong for macOS >= Big Sur (darwin20)
Date: Wed, 15 Jun 2022 19:17:51 +0000	[thread overview]
Message-ID: <bug-104871-4-nCkl55M0i2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104871-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Iain D Sandoe
<iains@gcc.gnu.org>:

https://gcc.gnu.org/g:82b771fd6cab421d92cc074a79f98389ac8569c3

commit r10-10848-g82b771fd6cab421d92cc074a79f98389ac8569c3
Author: Simon Wright <simon@pushface.org>
Date:   Sun Jun 12 17:01:22 2022 +0100

    Darwin: Truncate kernel-provided version to OS major for Darwin >= 20.

    In common with system tools, GCC uses a version obtained from the kernel as
    the prevailing macOS target, when that is not overridden by command line or
    environment versions (i.e. mmacosx-version-min=, MACOSX_DEPLOYMENT_TARGET).

    Presently, GCC assumes that if the OS version is >= 20, the value used
should
    include both major and minium version identifiers.  However the system
tools
    (for those versions) truncate the value to the major version - this leads
to
    link errors when combining objects built with clang and GCC for example:

    ld: warning: object file (null.o) was built for newer macOS version (12.2)
    than being linked (12.0)

    The change here truncates the values GCC uses to the major version.

    gcc/ChangeLog:

            PR target/104871
            * config/darwin-driver.c (darwin_find_version_from_kernel): If the
OS
            version is darwin20 (macOS 11) or greater, truncate the version to
the
            major number.

    (cherry picked from commit add1adaa17a294ea25918ffb4fdd40f115362632)

  parent reply	other threads:[~2022-06-15 19:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-10 19:36 [Bug c/104871] New: " simon at pushface dot org
2022-06-12 22:23 ` [Bug target/104871] " cvs-commit at gcc dot gnu.org
2022-06-15 19:08 ` cvs-commit at gcc dot gnu.org
2022-06-15 19:17 ` cvs-commit at gcc dot gnu.org [this message]
2023-05-16 19:04 ` cvs-commit at gcc dot gnu.org
2023-07-16 17:19 ` fxcoudert 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-104871-4-nCkl55M0i2@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).