public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Bernd Schmidt <bschmidt@redhat.com>
To: Szabolcs Nagy <szabolcs.nagy@arm.com>,
	       "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: Marcus Shawcroft <Marcus.Shawcroft@arm.com>,
	       Ramana Radhakrishnan <Ramana.Radhakrishnan@arm.com>,
	       Andreas Krebbel <krebbel@linux.vnet.ibm.com>,
	       "H.J. Lu" <hjl.tools@gmail.com>,
	Jakub Jelinek <jakub@redhat.com>,
	       Richard Henderson <rth@redhat.com>
Subject: Re: [PATCH] Fix default_binds_local_p_2 for extern protected data
Date: Wed, 30 Sep 2015 15:02:00 -0000	[thread overview]
Message-ID: <560BE7F9.1010708@redhat.com> (raw)
In-Reply-To: <55FA84C1.6010603@arm.com>

On 09/17/2015 11:15 AM, Szabolcs Nagy wrote:
> ping 2.
>
> this patch is needed for working visibility ("protected")
> attribute for extern data on targets using default_binds_local_p_2.
> https://gcc.gnu.org/ml/gcc-patches/2015-07/msg01871.html

I hesitate to review this one since I don't think I understand the 
issues on the various affected arches well enough. It looks like Jakub 
had some input on the earlier changes, maybe he could take a look? Or 
maybe rth knows best. Adding Ccs.

It would help to have examples of code generation demonstrating the 
problem and how you would solve it. Input from the s390 maintainers 
whether this is correct for their port would also be appreciated.

>>> Needs a further binutils patch too to emit R_*_GLOB_DAT
>>> instead of R_*_RELATIVE relocs for protected data.
>>> The glibc elf/tst-protected1a and elf/tst-protected1b
>>> tests depend on this.

What is the consequence of not having this binutils patch? Is the gcc 
patch and improvement, a null, or are there situations where it causes 
regressions without the binutils patch?

>>> Tested ARM and AArch64 targets.

Tested how, with or without this binutils patch?


Bernd

  reply	other threads:[~2015-09-30 13:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-22 17:06 Szabolcs Nagy
2015-08-10 11:04 ` Szabolcs Nagy
2015-09-17  9:32   ` Szabolcs Nagy
2015-09-30 15:02     ` Bernd Schmidt [this message]
2015-09-30 16:43       ` Szabolcs Nagy
2015-09-30 20:28         ` Andreas Krebbel
2015-10-14  9:56           ` Szabolcs Nagy
2015-10-19 10:12             ` Szabolcs Nagy
2015-10-19 18:53 ` Richard Henderson

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=560BE7F9.1010708@redhat.com \
    --to=bschmidt@redhat.com \
    --cc=Marcus.Shawcroft@arm.com \
    --cc=Ramana.Radhakrishnan@arm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hjl.tools@gmail.com \
    --cc=jakub@redhat.com \
    --cc=krebbel@linux.vnet.ibm.com \
    --cc=rth@redhat.com \
    --cc=szabolcs.nagy@arm.com \
    /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).