public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Klaus Pedersen <klaus.k.pedersen@nokia.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: target/5107: ICE when building an ARM/Thumb cross compiler for/on HP-UX. Date: Mon, 17 Dec 2001 06:36:00 -0000 [thread overview] Message-ID: <20011217143600.8964.qmail@sources.redhat.com> (raw) The following reply was made to PR target/5107; it has been noted by GNATS. From: Klaus Pedersen <klaus.k.pedersen@nokia.com> To: Richard.Earnshaw@arm.com Cc: gcc-gnats@gcc.gnu.org Subject: Re: target/5107: ICE when building an ARM/Thumb cross compiler for/on HP-UX. Date: Mon, 17 Dec 2001 15:25:54 +0100 Looking at the code again. I think that there is a bug. > for (i = 0; i < 25; i++) > if ((val & (mask << i)) == val) > break; > > if (i == 0) > FAIL; Consider "val = 0x55", which can be represented as 0x55 << 0, but calling the function with this value causes the function FAIL to be called. On the other hand, FAIL isn't called when passing the constant 0x101, which can't be represented, therefor I think that: > if (i == 0) > FAIL; should read: > if (i == 25) > FAIL; BR, Klaus Pedersen ext Richard Earnshaw wrote: > > Right, I've tracked this down to what I believe is the mis-compiled > function. > > The arm.md file defines the split pattern > > (define_split > [(set (match_operand:SI 0 "register_operand" "") > (match_operand:SI 1 "const_int_operand" ""))] > "TARGET_THUMB && CONST_OK_FOR_THUMB_LETTER (INTVAL (operands[1]), > 'K')" > [(set (match_dup 0) (match_dup 1)) > (set (match_dup 0) (ashift:SI (match_dup 0) (match_dup 2)))] > " > { > unsigned HOST_WIDE_INT val = INTVAL (operands[1]); > unsigned HOST_WIDE_INT mask = 0xff; > int i; > > for (i = 0; i < 25; i++) > if ((val & (mask << i)) == val) > break; > > if (i == 0) > FAIL; > > operands[1] = GEN_INT (val >> i); > operands[2] = GEN_INT (i); > }" > ... > > With the current sources (as of 15/12/2001) this is gen_split_415(). > > The body of the for() loop in this pattern is never executing. > Consequently the "if (i == 0)" clause is true and the pattern fails. > Clearly this is incorrect behaviour when val is 65536. > > You might be able to work around this problem by building the compiler > with a lower optimization level. Try > make all CFLAGS="-g". > > So over the the pa maintainers. Sorry, I don't know pa code well enough > > to even begin to work out why this is failing. > > R.
next reply other threads:[~2001-12-17 14:36 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-12-17 6:36 Klaus Pedersen [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-03-15 3:14 rearnsha 2002-03-04 17:36 Craig Rodrigues 2001-12-17 2:36 Klaus Pedersen 2001-12-15 8:46 Richard Earnshaw 2001-12-14 10:16 Richard Earnshaw 2001-12-14 9:56 Klaus Pedersen 2001-12-14 2:56 Richard Earnshaw 2001-12-13 14:46 Klaus.k.pedersen
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=20011217143600.8964.qmail@sources.redhat.com \ --to=klaus.k.pedersen@nokia.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ /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: linkBe 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).