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/99094] [AIX] Thread local uninitialized data allocated in .comm
Date: Thu, 11 Mar 2021 21:56:25 +0000 [thread overview]
Message-ID: <bug-99094-4-ZJBBq5U3ij@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99094-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99094
--- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by David Edelsohn <dje@gcc.gnu.org>:
https://gcc.gnu.org/g:26ed5a28b18ad080e51e6b61f5f60d67b66fd5f3
commit r11-7633-g26ed5a28b18ad080e51e6b61f5f60d67b66fd5f3
Author: David Edelsohn <dje.gcc@gmail.com>
Date: Thu Mar 11 11:41:24 2021 -0500
aix: Use lcomm for TLS static data.
GCC on AIX generates thread local uninitialized data in the common section,
which could conflict with another module.
This patch changes the code generation to place static uninitialized
thread local data into the local common section specified with .lcomm.
This change also removes the need to create a file-local name for the TBSS
data.
gcc/ChangeLog:
2021-03-11 David Edelsohn <dje.gcc@gmail.com>
PR target/99094
* config/rs6000/rs6000.c (rs6000_xcoff_file_start): Don't create
xcoff_tbss_section_name.
* config/rs6000/xcoff.h (ASM_OUTPUT_TLS_COMMON): Use .lcomm.
* xcoffout.c (xcoff_tbss_section_name): Delete.
* xcoffout.h (xcoff_tbss_section_name): Delete.
next prev parent reply other threads:[~2021-03-11 21:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-14 2:01 [Bug target/99094] New: " dje at gcc dot gnu.org
2021-02-14 2:01 ` [Bug target/99094] " dje at gcc dot gnu.org
2021-03-09 20:50 ` dje at gcc dot gnu.org
2021-03-11 21:56 ` cvs-commit at gcc dot gnu.org [this message]
2021-03-12 3:24 ` dje 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-99094-4-ZJBBq5U3ij@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).