public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Alex Velenko <Alex.Velenko@arm.com>
To: Richard Henderson <rth@redhat.com>
Cc: "H.J. Lu" <hjl.tools@gmail.com>,
	 Jack Howarth <howarth.at.gcc@gmail.com>,
	GCC Patches <gcc-patches@gcc.gnu.org>,
	 Ramana Radhakrishnan <Ramana.Radhakrishnan@arm.com>,
	Jan Hubicka <hubicka@ucw.cz>
Subject: Re: [PATCH] PR rtl-optimization/32219: optimizer causees wrong code in pic/hidden/weak symbol checking
Date: Tue, 03 Mar 2015 15:58:00 -0000	[thread overview]
Message-ID: <54F5DA29.70004@arm.com> (raw)
In-Reply-To: <54E61CAE.30804@redhat.com>

On 19/02/15 17:26, Richard Henderson wrote:
> On 02/19/2015 09:08 AM, Alex Velenko wrote:
>> Your suggestion seem to fix gcc.target/arm/long-calls-1.c, but has to be
>> thoroughly tested.
>
> Before you do complete testing, please also delete the TREE_STATIC test.
> That bit should never be relevant to functions, as it indicates not that
> it is in the compilation unit, but that it has static (as opposed to
> automatic) storage duration.  Thus it is only relevant to variables.
>
>
> r~
>
>
>
> diff --git a/gcc/config/arm/arm.c b/gcc/config/arm/arm.c
> index 7bf5b4d..777230e 100644
> --- a/gcc/config/arm/arm.c
> +++ b/gcc/config/arm/arm.c
> @@ -6392,14 +6392,8 @@ arm_set_default_type_attributes (tree type)
>   static bool
>   arm_function_in_section_p (tree decl, section *section)
>   {
> -  /* We can only be certain about functions defined in the same
> -     compilation unit.  */
> -  if (!TREE_STATIC (decl))
> -    return false;
> -
> -  /* Make sure that SYMBOL always binds to the definition in this
> -     compilation unit.  */
> -  if (!targetm.binds_local_p (decl))
> +  /* We can only be certain about the prevailing symbol definition.  */
> +  if (!decl_binds_to_current_def_p (decl))
>       return false;
>
>     /* If DECL_SECTION_NAME is set, assume it is trustworthy.  */
>
>

Hi,

Did a bootstrap and a full regression run on arm-none-linux-gnueabihf,
No new regressions found. Some previously failing tests in libstdc++ 
started to fail differently, for example:

< ERROR: 22_locale/num_get/get/wchar_t/2.cc: can't read 
"additional_sources": no such variable for " dg-do 22 run { xfail 
lax_strtof\
p } "
< UNRESOLVED: 22_locale/num_get/get/wchar_t/2.cc: can't read 
"additional_sources": no such variable for " dg-do 22 run { xfail lax_s\
trtofp } "
---
 > ERROR: 22_locale/num_get/get/wchar_t/2.cc: can't read 
"et_cache(uclibc,value)": no such element in array for " dg-do 22 run { 
xfai\
l lax_strtofp } "
 > UNRESOLVED: 22_locale/num_get/get/wchar_t/2.cc: can't read 
"et_cache(uclibc,value)": no such element in array for " dg-do 22 run {\
  xfail lax_strtofp } "


But I think it is okay.

Kind regards,
Alex

  reply	other threads:[~2015-03-03 15:58 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-06 16:23 [PATCH] PR rtl-optimization/32219: optimizer causes " H.J. Lu
2015-02-06 21:31 ` Jack Howarth
2015-02-06 21:41   ` H.J. Lu
2015-02-06 21:51     ` Jack Howarth
2015-02-07  1:50       ` H.J. Lu
2015-02-07  1:51     ` Jack Howarth
2015-02-07  1:55       ` H.J. Lu
2015-02-07  2:25         ` Jack Howarth
2015-02-07  8:28         ` Jack Howarth
2015-02-07 12:27           ` H.J. Lu
2015-02-07 15:11             ` Jack Howarth
2015-02-07 15:25               ` Jack Howarth
2015-02-07 15:56               ` H.J. Lu
2015-02-07 16:45                 ` H.J. Lu
2015-02-08 18:24                   ` Jack Howarth
2015-02-09 17:26                     ` Mike Stump
2015-02-10 18:33                       ` Jack Howarth
2015-02-10 21:19                   ` Richard Henderson
2015-02-10 21:25                     ` H.J. Lu
2015-02-11 14:35                     ` Jack Howarth
2015-02-12  6:23                     ` [PATCH] PR rtl-optimization/32219: optimizer causees " Richard Henderson
2015-02-12 18:16                       ` H.J. Lu
2015-02-12 18:58                         ` H.J. Lu
2015-02-12 19:25                           ` Richard Henderson
2015-02-12 23:04                             ` H.J. Lu
2015-02-12 23:05                               ` H.J. Lu
2015-02-13  0:05                                 ` Richard Henderson
2015-02-13  4:14                                   ` H.J. Lu
2015-02-13  5:11                                     ` Richard Henderson
2015-02-18 14:17                                       ` Alex Velenko
2015-02-19 13:12                                         ` H.J. Lu
2015-02-19 15:02                                         ` Richard Henderson
2015-02-19 17:25                                           ` Alex Velenko
2015-02-19 17:27                                             ` Richard Henderson
2015-03-03 15:58                                               ` Alex Velenko [this message]
2015-03-05 14:55                                                 ` Alex Velenko
2015-03-05 15:31                                                   ` Ramana Radhakrishnan
2015-03-06 11:14                                                     ` Alex Velenko
2015-02-12 19:16                         ` Jack Howarth
2015-02-12 19:18                           ` H.J. Lu
2015-02-12 19:39                             ` Jack Howarth
2015-02-07 19:37                 ` [PATCH] PR rtl-optimization/32219: optimizer causes " Jack Howarth
2015-02-16 13:25 [PATCH] PR rtl-optimization/32219: optimizer causees " Uros Bizjak
2015-02-16 14:01 ` H.J. Lu
2015-02-16 16:30   ` Richard Henderson
2015-02-16 16:38     ` H.J. Lu
2015-02-19 21:07     ` Uros Bizjak
2015-02-19 21:08       ` H.J. Lu
2015-02-19 21:16         ` Richard Henderson
2015-02-19 21:16         ` H.J. Lu
2015-02-19 21:35       ` Richard Henderson
2015-02-19 21:43         ` H.J. Lu
2015-02-19 23:39           ` Uros Bizjak

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=54F5DA29.70004@arm.com \
    --to=alex.velenko@arm.com \
    --cc=Ramana.Radhakrishnan@arm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hjl.tools@gmail.com \
    --cc=howarth.at.gcc@gmail.com \
    --cc=hubicka@ucw.cz \
    --cc=rth@redhat.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).