public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ramana Radhakrishnan <ramana.gcc@googlemail.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] PR middle-end/67220: GCC fails to properly handle libcall symbol visibility of built functions
Date: Wed, 14 Oct 2015 17:17:00 -0000	[thread overview]
Message-ID: <CAJA7tRYvJLxU4Q=33FuN-fZnyvk28mVYEFitomPTvyQQfLbeOg@mail.gmail.com> (raw)
In-Reply-To: <CAMe9rOr=sgMc0FZjCXvhtZDSDYwMZggBNCKUCiTh8Kz7amFs5g@mail.gmail.com>

On Wed, Oct 14, 2015 at 5:51 PM, H.J. Lu <hjl.tools@gmail.com> wrote:
> On Wed, Oct 14, 2015 at 9:46 AM, Ramana Radhakrishnan
> <ramana.gcc@googlemail.com> wrote:
>> On Wed, Oct 14, 2015 at 5:21 PM, H.J. Lu <hongjiu.lu@intel.com> wrote:
>>
>>> ---
>>> gcc/c/
>>>
>>>         PR middle-end/67220
>>>         * c-decl.c (diagnose_mismatched_decls): Copy explicit visibility
>>>         to builtin function.
>>>
>>> gcc/
>>>
>>>         PR middle-end/67220
>>>         * expr.c (init_block_move_fn): Copy visibility from the builtin
>>>         memcpy.
>>>         (init_block_clear_fn): Copy visibility from the builtin memset.
>>>
>>> gcc/testsuite/
>>>
>>>         PR middle-end/67220
>>>         * gcc.target/i386/pr67220-1.c: New test.
>>>         * gcc.target/i386/pr67220-2.c: Likewise.
>>>         * gcc.target/i386/pr67220-3.c: Likewise.
>>>         * gcc.target/i386/pr67220-4.c: Likewise.
>>>         * gcc.target/i386/pr67220-5.c: Likewise.
>>>         * gcc.target/i386/pr67220-6.c: Likewise.
>>
>> Why aren't these tests in gcc.dg ?  The problem affects all targets
>> not just x86.
>>
>
> If I move tests to gcc.dg, would you mind updating them to verify
> that they pass on arm?


It's not just a question of ARM. This affects all targets that support
symbol visibility in shared libraries ... please do the math as to how
many targets are affected. Now reading the test even more, it appears
that you also need a dg-require-visibility so that this test is run on
all targets that support symbol visibility.

The test as written uses target_fpic - target-supports.exp does not
have anything ARM specific about handling this - there is some m68k ,
so it should just work on any target that supports symbol visibility.
If it doesn't, that target has an issue and then folks interested in
that target will do something about it. Even if you don't fix the
issue on every target, please have the courtesy of letting them find
it in some sort of automatic manner rather than auditing every single
commit in every gcc.target directory.


regards
Ramana


>
>
> --
> H.J.

  reply	other threads:[~2015-10-14 17:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-14 16:21 H.J. Lu
2015-10-14 16:46 ` Ramana Radhakrishnan
2015-10-14 16:51   ` H.J. Lu
2015-10-14 17:17     ` Ramana Radhakrishnan [this message]
2015-10-15  8:44 ` Richard Biener
2015-10-15 10:38   ` H.J. Lu
2015-10-20 23:43     ` Bernd Schmidt
2015-10-21  3:42       ` H.J. Lu
2016-01-15 18:44       ` H.J. Lu

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='CAJA7tRYvJLxU4Q=33FuN-fZnyvk28mVYEFitomPTvyQQfLbeOg@mail.gmail.com' \
    --to=ramana.gcc@googlemail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hjl.tools@gmail.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).