public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Henderson <rth@redhat.com>
To: Uros Bizjak <ubizjak@gmail.com>
Cc: "H.J. Lu" <hjl.tools@gmail.com>,
	       "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] PR rtl-optimization/32219: optimizer causees wrong code in pic/hidden/weak symbol checking
Date: Thu, 19 Feb 2015 21:35:00 -0000	[thread overview]
Message-ID: <54E652B9.7080008@redhat.com> (raw)
In-Reply-To: <CAFULd4bsDPrsv+SObbmYDU-a8piwxcZ5LMqYfPrXQBMnQ95jzw@mail.gmail.com>

On 02/19/2015 01:04 PM, Uros Bizjak wrote:
> 2015-02-19  Uros Bizjak  <ubizjak@gmail.com>
> 
>     * config/alpha/alpha.c (alpha_in_small_data_p): Reject common symbols.

Ok.  Thanks.


r~

  parent reply	other threads:[~2015-02-19 21:16 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-16 13:25 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         ` H.J. Lu
2015-02-19 21:16         ` Richard Henderson
2015-02-19 21:35       ` Richard Henderson [this message]
2015-02-19 21:43         ` H.J. Lu
2015-02-19 23:39           ` Uros Bizjak
  -- strict thread matches above, loose matches on Subject: below --
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-07  1:51     ` Jack Howarth
2015-02-07  1:55       ` H.J. Lu
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:56               ` H.J. Lu
2015-02-07 16:45                 ` H.J. Lu
2015-02-10 21:19                   ` Richard Henderson
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
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

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=54E652B9.7080008@redhat.com \
    --to=rth@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hjl.tools@gmail.com \
    --cc=ubizjak@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).