public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/101726] target_clone resolver does not generate PIC despite -fPIC
Date: Thu, 12 Aug 2021 15:33:55 +0000	[thread overview]
Message-ID: <bug-101726-4-773lF5ruYy@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101726-4@http.gcc.gnu.org/bugzilla/>

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

Martin Liška <marxin at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |patch

--- Comment #6 from Martin Liška <marxin at gcc dot gnu.org> ---
I've just sent a patch to ML:
https://gcc.gnu.org/pipermail/gcc-patches/2021-August/577287.html

  parent reply	other threads:[~2021-08-12 15:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-02 16:29 [Bug c/101726] New: " stefan.kneifel at bluewin dot ch
2021-08-03 11:54 ` [Bug target/101726] " marxin at gcc dot gnu.org
2021-08-03 16:42 ` stefan.kneifel at bluewin dot ch
2021-08-11 11:47 ` marxin at gcc dot gnu.org
2021-08-11 20:02 ` stefan.kneifel at bluewin dot ch
2021-08-12 13:53 ` marxin at gcc dot gnu.org
2021-08-12 15:33 ` marxin at gcc dot gnu.org [this message]
2021-08-13 14:10 ` [Bug ipa/101726] " stefan.kneifel at bluewin dot ch
2021-08-16  7:53 ` cvs-commit at gcc dot gnu.org
2021-08-16  7:55 ` marxin at gcc dot gnu.org
2021-08-16 11:14 ` cvs-commit at gcc dot gnu.org
2021-08-16 11:16 ` marxin 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-101726-4-773lF5ruYy@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).