public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Christophe Lyon <clyon@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r12-2954] Do not enable DT_INIT_ARRAY/DT_FINI_ARRAY on uclinuxfdpiceabi
Date: Tue, 17 Aug 2021 13:00:33 +0000 (GMT)	[thread overview]
Message-ID: <20210817130033.9157A388A421@sourceware.org> (raw)

https://gcc.gnu.org/g:9c560cf23996271ee26dfc4a1d8484b85173cd12

commit r12-2954-g9c560cf23996271ee26dfc4a1d8484b85173cd12
Author: Christophe Lyon <christophe.lyon@foss.st.com>
Date:   Tue Aug 17 12:59:26 2021 +0000

    Do not enable DT_INIT_ARRAY/DT_FINI_ARRAY on uclinuxfdpiceabi
    
    Commit r12-1328 enabled DT_INIT_ARRAY/DT_FINI_ARRAY for all Linux
    targets, but this does not work for arm-none-uclinuxfdpiceabi: it
    makes all the execution tests fail.
    
    This patch restores the original behavior for uclinuxfdpiceabi.
    
    2021-08-12  Christophe Lyon  <christophe.lyon@foss.st.com>
    
            gcc/
            PR target/100896
            * config.gcc (gcc_cv_initfini_array): Leave undefined for
            uclinuxfdpiceabi targets.

Diff:
---
 gcc/config.gcc | 10 ++++++++--
 1 file changed, 8 insertions(+), 2 deletions(-)

diff --git a/gcc/config.gcc b/gcc/config.gcc
index 7001a79b823..d9bfbfdc0d2 100644
--- a/gcc/config.gcc
+++ b/gcc/config.gcc
@@ -851,8 +851,14 @@ case ${target} in
   tmake_file="${tmake_file} t-glibc"
   target_has_targetcm=yes
   target_has_targetdm=yes
-  # Linux targets always support .init_array.
-  gcc_cv_initfini_array=yes
+  case $target in
+    *-*-*uclibc* | *-*-uclinuxfdpiceabi)
+      ;;
+    *)
+      # Linux targets always support .init_array.
+      gcc_cv_initfini_array=yes
+      ;;
+  esac
   ;;
 *-*-netbsd*)
   tm_p_file="${tm_p_file} netbsd-protos.h"


                 reply	other threads:[~2021-08-17 13:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20210817130033.9157A388A421@sourceware.org \
    --to=clyon@gcc.gnu.org \
    --cc=gcc-cvs@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).