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/94177] TLS global-dynamic model clobbers function parameter on AIX
Date: Fri, 28 May 2021 20:49:24 +0000	[thread overview]
Message-ID: <bug-94177-4-fFzJuJaisD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94177-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-11 branch has been updated by David Edelsohn
<dje@gcc.gnu.org>:

https://gcc.gnu.org/g:0be51abf080f1d7515e3777dd5e5a983b47573a8

commit r11-8481-g0be51abf080f1d7515e3777dd5e5a983b47573a8
Author: David Edelsohn <dje.gcc@gmail.com>
Date:   Fri Apr 30 14:27:46 2021 -0400

    aix: TLS precompute register parameters (PR 94177)

    AIX uses a compiler-managed TOC for global data, including TLS symbols.
    The GCC TOC implementation manages the TOC entries through the constant
pool.

    TLS symbols sometimes require a function call to obtain the TLS base
    pointer.  The arguments to the TLS call can conflict with arguments to
    a normal function call if the TLS symbol is an argument in the normal call.
    GCC specifically checks for this situation and precomputes the TLS
    arguments, but the mechanism to check for this requirement utilizes
    legitimate_constant_p().  The necessary result of legitimate_constant_p()
    for correct TOC behavior and for correct TLS argument behavior is in
    conflict.

    This patch adds a new target hook precompute_tls_p() to decide if an
    argument should be precomputed regardless of the result from
    legitmate_constant_p().

    gcc/ChangeLog:

            PR target/94177
            * calls.c (precompute_register_parameters): Additionally test
            targetm.precompute_tls_p to pre-compute argument.
            * config/rs6000/aix.h (TARGET_PRECOMPUTE_TLS_P): Define.
            * config/rs6000/rs6000.c (rs6000_aix_precompute_tls_p): New.
            * target.def (precompute_tls_p): New.
            * doc/tm.texi.in (TARGET_PRECOMPUTE_TLS_P): Add hook documentation.
            * doc/tm.texi: Regenerated.

            (cherry-picked from commit
a21b399708175f6fc0ac723a0cebc127da421c60)

      parent reply	other threads:[~2021-05-28 20:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-14 22:59 [Bug target/94177] New: " dje at gcc dot gnu.org
2021-03-09 18:11 ` [Bug target/94177] " dje at gcc dot gnu.org
2021-04-27 16:32 ` cvs-commit at gcc dot gnu.org
2021-04-27 19:01 ` dje at gcc dot gnu.org
2021-05-28 20:49 ` cvs-commit 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-94177-4-fFzJuJaisD@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).