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/105599] g++ by itself is not producing "fatal error: no input files" for darwin target
Date: Sun, 29 May 2022 18:27:36 +0000	[thread overview]
Message-ID: <bug-105599-4-dsRXLQYb6r@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105599-4@http.gcc.gnu.org/bugzilla/>

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

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

https://gcc.gnu.org/g:794737976b9a6418eab817f143bb4eb2d0c834d2

commit r13-818-g794737976b9a6418eab817f143bb4eb2d0c834d2
Author: Iain Sandoe <iain@sandoe.co.uk>
Date:   Sun May 29 16:14:32 2022 +0100

    Darwin: Fix empty g++ command lines [PR105599].

    An empty g++ command line should produce a diagnostic that there are no
    inputs.  The PR is that currently Darwin produces a dignostic about missing
    link items instead - this is because (errnoeously), for this driver, we are
    creating a link job for empty command lines.

    The problem occurs in four stages:

     The g++ driver appends -shared-libgcc to the command line.

     The Darwin driver_init code in the backend does not see this (it sees an
     empty command line).

     When the back end driver code driver sees an empty command line, it does
not
     add any supplementary flags (e.g. asm-macosx-version-min) - precisely to
     avoid anything being claimed as an input_file and therefore triggering a
link
     line.

     Since we do not have a value for asm-macosx-version-min when processing
the
     driver specs, we unconditionally inject 'multiply_defined suppress' which
is
     used with shared libgcc (but only intended on very old Darwin).  This then
     causes the generation of a link job.

    The solution, for the present, is to move version-specific link params to
the
    LINK_SPEC so that they are only processed when a link job has already been
    decided.

    Signed-off-by: Iain Sandoe <iain@sandoe.co.uk>

            PR target/105599

    gcc/ChangeLog:

            * config/darwin.h: Move versions-specific handling of
multiply_defined
            from SUBTARGET_DRIVER_SELF_SPECS to LINK_SPEC.

  parent reply	other threads:[~2022-05-29 18:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-13 21:06 [Bug c++/105599] New: g++ binary: undefined symbols _main referenced from __start in crt1.0 mario_grgic at hotmail dot com
2022-05-13 22:05 ` [Bug target/105599] g++ by itself is not producing "fatal error: no input files" for darwin target pinskia at gcc dot gnu.org
2022-05-13 22:21 ` iains at gcc dot gnu.org
2022-05-13 23:03 ` iains at gcc dot gnu.org
2022-05-29 18:27 ` cvs-commit at gcc dot gnu.org [this message]
2022-06-15 19:07 ` cvs-commit at gcc dot gnu.org
2022-06-15 19:09 ` iains at gcc dot gnu.org
2023-05-16 19:01 ` cvs-commit at gcc dot gnu.org
2023-05-16 19:10 ` iains at gcc dot gnu.org
2024-04-24 18:36 ` cvs-commit 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-105599-4-dsRXLQYb6r@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).