public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "linkw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/112980] 64-bit powerpc ELFv2 does not allow nops to be generated before function global entry point
Date: Fri, 19 Jan 2024 02:06:41 +0000	[thread overview]
Message-ID: <bug-112980-4-6bWtmXhdng@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112980-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Kewen Lin <linkw at gcc dot gnu.org> ---
(In reply to Naveen N Rao from comment #2)
> I don't really have a preference, though I tend to agree that nops before
> the local entry point aren't that useful. Even with the current approach,
> not all functions have instructions at the GEP and for those, the nops are
> being generated outside the function. We also won't have a separate GEP/LEP
> with pcrel, so we won't need a separate option eventually.

Thanks for the input! Looking forward to the comments from the others,
especially Segher, David and Peter.

(In reply to Michael Matz from comment #3)
> (In reply to Kewen Lin from comment #1)
> > 
> > As Segher's review comments in [2], to support "before NOPs" before global
> > entry and "after NOPs" after global entry,
> 
> Just to be perfectly clear here: the "after NOPs" need to come after local
> entry
> (which strictly speaking is of course after the global one as well, but I'm
> being anal :) ).

Oops, good catch, I meant to type "after local entry", thanks for the
correction making it perfectly clear. :)

  parent reply	other threads:[~2024-01-19  2:06 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-12  9:22 [Bug target/112980] New: " naveen at kernel dot org
2024-01-18  5:15 ` [Bug target/112980] " linkw at gcc dot gnu.org
2024-01-18  9:44 ` naveen at kernel dot org
2024-01-18 13:36 ` matz at gcc dot gnu.org
2024-01-19  2:06 ` linkw at gcc dot gnu.org [this message]
2024-03-19 16:27 ` jamborm at gcc dot gnu.org
2024-03-20  9:05 ` linkw at gcc dot gnu.org
2024-03-25 13:31 ` naveen at kernel dot org
2024-04-01  7:30 ` linkw at gcc dot gnu.org
2024-04-01 14:03 ` giuliano.belinassi at gmail dot com
2024-04-02  8:21 ` linkw at gcc dot gnu.org
2024-04-02  8:24 ` linkw at gcc dot gnu.org
2024-04-04 18:24 ` giuliano.belinassi at gmail dot com
2024-04-09  3:02 ` linkw at gcc dot gnu.org
2024-04-09 12:59 ` matz at gcc dot gnu.org
2024-04-10  2:14 ` linkw at gcc dot gnu.org
2024-04-11 12:37 ` matz at gcc dot gnu.org
2024-04-12  3:48 ` linkw at gcc dot gnu.org
2024-05-29  2:21 ` linkw 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-112980-4-6bWtmXhdng@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).