public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Bruno Haible <haible@ilog.fr>
To: gcc-gnats@gcc.gnu.org
Cc: "Jim Gifford" <jim@jg555.com>
Subject: c/7695: i686/athlon specific ICE
Date: Fri, 23 Aug 2002 04:56:00 -0000	[thread overview]
Message-ID: <15718.4131.509884.714017@honolulu.ilog.fr> (raw)


>Number:         7695
>Category:       c
>Synopsis:       i686/athlon specific ICE on simple arithmetic function
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          ice-on-legal-code
>Submitter-Id:   net
>Arrival-Date:   Fri Aug 23 03:36:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Bruno Haible
>Release:        3.2
>Organization:
GNU hackers
>Environment:
System: Linux linuix 2.4.18-4GB #1 Wed Mar 27 13:57:05 UTC 2002 i686 unknown
Architecture: i686

        
host: i686-pc-linux-gnu
build: i686-pc-linux-gnu
target: i686-pc-linux-gnu
configured with: ../gcc-3.2/configure --prefix=/packages/gnu-inst-gcc/3.2 --enable-shared --enable-version-specific-runtime-libs --enable-nls --enable-threads=posix
>Description:

$ LC_ALL=C gcc -march=i686 -O2 -S j.c
j.c: In function `gbkext1_mbtowc':
j.c:28: unrecognizable insn:
(insn 163 161 165 (set (reg:QI 82)
        (const_int 128 [0x80])) -1 (nil)
    (nil))
j.c:28: Internal compiler error in extract_insn, at recog.c:2148
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
$ LC_ALL=C gcc -march=athlon -O2 -S j.c
j.c: In function `gbkext1_mbtowc':
j.c:28: unrecognizable insn:
(insn 161 159 163 (set (reg:QI 82)
        (const_int 128 [0x80])) -1 (nil)
    (nil))
j.c:28: Internal compiler error in extract_insn, at recog.c:2148
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.

Without -march=i686 or -march=athlon there is no problem.

>How-To-Repeat:

See above. Here is j.c:

=============================== j.c ======================================
extern const unsigned short gbkext1_2uni_page81[6080];
int gbkext1_mbtowc (unsigned int *pwc, const unsigned char *s, int n)
{
  unsigned char c1 = s[0];
  if (c1 >= 0x81 && c1 <= 0xa0)
    {
      if (n >= 2)
        {
          unsigned char c2 = s[1];
          if ((c2 >= 0x40 && c2 < 0x7f) || (c2 >= 0x80 && c2 < 0xff))
            {
              unsigned int i =
                190 * (c1 - 0x81) + (c2 - (c2 >= 0x80 ? 0x41 : 0x40));
              unsigned short wc = 0xfffd;
              if (i < 6080)
                wc = gbkext1_2uni_page81[i];
              if (wc != 0xfffd)
                {
                  *pwc = (unsigned int) wc;
                  return 2;
                }
            }
          return -1;
        }
      return -2;
    }
  return -1;
}
==========================================================================

And here is a minimal j.c:

==========================================================================
int gbkext1_mbtowc (unsigned char c1, unsigned char c2)
{
  return c1 + (c2 - (c2 >= 0x80 ? 0x41 : 0x40));
}
==========================================================================

>Fix:

unknown
>Release-Note:
>Audit-Trail:
>Unformatted:


                 reply	other threads:[~2002-08-23 10:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=15718.4131.509884.714017@honolulu.ilog.fr \
    --to=haible@ilog.fr \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=jim@jg555.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).