public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "amonakov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/115170] __cxa_atexit@plt even if -fno-plt
Date: Fri, 24 May 2024 11:41:56 +0000	[thread overview]
Message-ID: <bug-115170-4-minEgc5nom@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-115170-4@http.gcc.gnu.org/bugzilla/>

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

Alexander Monakov <amonakov at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |amonakov at gcc dot gnu.org

--- Comment #9 from Alexander Monakov <amonakov at gcc dot gnu.org> ---
(In reply to Cristian Rodríguez from comment #8)
> SO shall I flile a bug report to the linker instead? if -znow is used I
> would expect no plt used in the whole executable..

That is not a reasonable expectation. Direct calls use 5-byte encoding on x86,
the linker has no way to replace them with GOT-indirect calls (6 bytes).

In any case, '-z now' does not mean 'no PLT'. It means 'no lazy binding', and
PLT is still used where necessary.

Maybe you can explain why you expect that or what you seek to solve in the
first place?

      parent reply	other threads:[~2024-05-24 11:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-21  2:57 [Bug c/115170] New: " crrodriguez at opensuse dot org
2024-05-21  3:09 ` [Bug middle-end/115170] " pinskia at gcc dot gnu.org
2024-05-21  3:11 ` pinskia at gcc dot gnu.org
2024-05-21  3:13 ` pinskia at gcc dot gnu.org
2024-05-21  4:18 ` pinskia at gcc dot gnu.org
2024-05-21  4:23 ` pinskia at gcc dot gnu.org
2024-05-21 15:43 ` crrodriguez at opensuse dot org
2024-05-21 16:00 ` pinskia at gcc dot gnu.org
2024-05-23 20:08 ` crrodriguez at opensuse dot org
2024-05-24 11:41 ` amonakov at gcc dot gnu.org [this message]

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-115170-4-minEgc5nom@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).