public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Martin Sebor <msebor@gmail.com>
To: David Edelsohn <dje.gcc@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>, Jeffrey Law <law@redhat.com>
Subject: Re: [PATCH] add support for strnlen (PR 81384)
Date: Tue, 19 Jun 2018 20:10:00 -0000	[thread overview]
Message-ID: <e604ef7f-a602-1c21-6ab2-8afe06779b12@gmail.com> (raw)
In-Reply-To: <CAGWvny=NXqyu=XQehQZ_-S-Jo=DK1PTNifSnkzSht8dEDHpMkg@mail.gmail.com>

On 06/19/2018 01:33 PM, David Edelsohn wrote:
> Martin,
>
> Does attr-nonstring-3.c assume a 64 bit environment?

I don't think so.  The error below suggests a problem during
the expansion of the strncmp built-in.  The patch didn't
change that.  I see GCC 8 ICE on the test as well so it must
be a latent bug that the test somehow manages to tickle.  Let
me try to reduce it to a small test case and open a bug.

Martin

> I'm seeing new errors on the rs6000 port
>
> FAIL: gcc.dg/attr-nonstring-3.c (internal compiler error)
> /nasfarm/edelsohn/src/src/gcc/testsuite/gcc.dg/attr-nonstring-3.c:73:1:
> error: could not split insn
> (insn 3244 3245 3246 (set (reg:SI 5 5)
>         (const_int -2147483680 [0xffffffff7fffffe0]))
> "/nasfarm/edelsohn/src/src/gcc/testsuite/gcc.dg/attr-nonstring-3.c":72
> 446 {*movsi_internal1}
>      (nil))
> during RTL pass: final
> /nasfarm/edelsohn/src/src/gcc/testsuite/gcc.dg/attr-nonstring-3.c:73:1:
> internal compiler error: in final_scan_insn_1, at final.c:3140
> ranges offset out of range
>
> Something is assuming that a 64 bit value can fit in a 32 bit register.
>
> Thanks, David
>

  reply	other threads:[~2018-06-19 20:10 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-19 19:33 David Edelsohn
2018-06-19 20:10 ` Martin Sebor [this message]
2018-06-19 20:25   ` Martin Sebor
2018-06-20  5:24   ` Jeff Law
  -- strict thread matches above, loose matches on Subject: below --
2018-06-05 21:43 Martin Sebor
2018-06-05 22:20 ` Jakub Jelinek
2018-06-06 15:14   ` Martin Sebor
2018-06-06 15:49     ` Jakub Jelinek
2018-06-06  0:39 ` Eric Gallager
2018-06-06 14:44   ` Martin Sebor
2018-06-12 21:11 ` Jeff Law
2018-06-18 16:35   ` Martin Sebor
2018-07-09 14:36     ` Aldy Hernandez
2018-07-09 19:51       ` Jeff Law
2018-07-09 20:51         ` Martin Sebor
2018-07-09 21:26       ` Martin Sebor
2018-07-10  7:13         ` Richard Biener
2018-07-10 14:10           ` Martin Sebor
2018-07-10 14:25             ` Richard Biener
2018-07-10 14:34               ` Jeff Law
2018-07-10 14:57                 ` Martin Sebor

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=e604ef7f-a602-1c21-6ab2-8afe06779b12@gmail.com \
    --to=msebor@gmail.com \
    --cc=dje.gcc@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=law@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).