public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Paul Hua <paul.hua.gm@gmail.com>
To: qing.zhao@oracle.com
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH][Middle-end]patch for fixing PR 86519
Date: Tue, 21 Aug 2018 13:07:00 -0000	[thread overview]
Message-ID: <CAKjxQHmTOLcDqBJUFPSMkYqnfArDH2Fj84o88C4DBvqD+zW9sw@mail.gmail.com> (raw)
In-Reply-To: <A42489F9-9919-46B9-86CA-05F1C6554A4D@oracle.com>

Hi, Qing,

The cfarm machine gcc23 can build mips64el successful, configure with
"../configure --prefix=/opt/gcc-9 MISSING=texinfo MAKEINFO=missing
--target=mips64el-linux-gnu --enable-languages=c,c++
On Tue, Aug 21, 2018 at 7:02 AM Qing Zhao <qing.zhao@oracle.com> wrote:
>
> Hi, Paul,
>
> I was trying to repeat this issue on a mips machine today, but failed…
>
> the only mips machines I can access are those in gcc compile farm, I chose gcc22, but failed to build GCC on this machine.
>
> do you know any other machine in gcc compile farm that can repeat this issue?
>
> thanks a lot.
>
> Qing
> > On Aug 17, 2018, at 10:43 PM, Paul Hua <paul.hua.gm@gmail.com> wrote:
> >
> > Hi Qing:
> >
> >>
> >> the change has been committed as:
> >> https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=263563 <https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=263563>
> >>
> >> Qing
> >>
> >
> > The strcmpopt_6.c test still fails on mips64el target.
> >
> > gcc.dg/strcmpopt_6.c: memcmp found 4 times
> > FAIL: gcc.dg/strcmpopt_6.c scan-assembler-times memcmp 2
> >
> >
> > The mips asm output have ".reloc" info.
> >
> > -------------------------------------------------------------------------
> >        ld      $5,%got_page(.LC0)($28)
> >        ld      $25,%call16(memcmp)($28)
> >        li      $6,3                    # 0x3
> >        sd      $31,8($sp)
> >        .reloc  1f,R_MIPS_JALR,memcmp
> > 1:      jalr    $25
> >        daddiu  $5,$5,%got_ofst(.LC0)
> > ----------------------------------------------------------------------------
> >
> > scan-assembler find "4" times.
> >
> > Thanks
> > Paul Hua
>

  reply	other threads:[~2018-08-21 13:07 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-14 14:57 Qing Zhao
2018-08-15  4:25 ` Jeff Law
2018-08-15 16:36   ` Qing Zhao
2018-08-18  3:43     ` Paul Hua
2018-08-18  3:50       ` Jeff Law
2018-08-20  8:57         ` Rainer Orth
2018-08-20 18:13           ` Qing Zhao
2018-08-22 15:10           ` Qing Zhao
2018-08-22 15:50             ` Rainer Orth
2018-08-22 17:05               ` Qing Zhao
2018-08-22 22:01                 ` Jeff Law
2018-08-23 16:13                   ` Qing Zhao
2018-08-24  2:55                     ` Jeff Law
2018-08-20 23:02       ` Qing Zhao
2018-08-21 13:07         ` Paul Hua [this message]
     [not found]           ` <2AC2B18F-9442-4C4A-A473-FA1759941220@oracle.com>
2018-08-22  0:25             ` Paul Hua
2018-08-22 14:04               ` Qing Zhao

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=CAKjxQHmTOLcDqBJUFPSMkYqnfArDH2Fj84o88C4DBvqD+zW9sw@mail.gmail.com \
    --to=paul.hua.gm@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=qing.zhao@oracle.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).