public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: hiten@uk.FreeBSD.org
To: gcc-gnats@gcc.gnu.org
Subject: c/8282: GCC 3.1 crashes under bitshift operations
Date: Fri, 18 Oct 2002 19:26:00 -0000	[thread overview]
Message-ID: <20021019021946.23554.qmail@sources.redhat.com> (raw)


>Number:         8282
>Category:       c
>Synopsis:       GCC 3.1 crashes under bitshift operations
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Oct 18 19:26:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Hiten Pandya
>Release:        prerelease
>Organization:
>Environment:
Using built-in specs.
Configured with: FreeBSD/i386 system compiler
Thread model: posix
gcc version 3.1 [FreeBSD] 20020509 (prerelease)

FreeBSD 5.0-CURRENT #1: Mon Jul 15 22:43:48 BST 2002
>Description:
NB: I am not an expert in compilers whatsoever.

When compiling the native version of the uuid library on FreeBSD 5.0, gcc crashes, and produces the following error:

hpdi:~/work/uuid%> gcc -otest1 -luuid tst_uuid.c
tst_uuid.c: In function `uuid_variant':
tst_uuid.c:125: unrecognizable insn:
(insn 14 12 16 (set (reg:QI 62)
        (const_int 32768 [0x8000])) -1 (nil)
    (nil))
tst_uuid.c:128: Internal compiler error in extract_insn, at recog.c:2132
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.

uuid_variant():
---------------
static __inline int
uuid_variant(struct uuid u)
{
   uint16_t seq = u.clock_seq_low +
     u.clock_seq_hi_and_reserved;

        if ((seq << 0x8000) == 0)
                return UUID_TYPE_NCS;
        if ((seq << 0x4000) == 0)
                return UUID_TYPE_DCE;
        if ((seq << 0x2000) == 0)
                return UUID_TYPE_MS;

        return UUID_TYPE_OTHER;
}

tst_uuid.c:125, is just the end of the file.

If this information is vague, and little, please, do not
hesitate to contact me for more information.  I am
submitting a GCC related PR for the first time.  Please
accept my apologies for any errors.

Cheers.

  -- Hiten Pandya
  -- hiten@uk.FreeBSD.org
>How-To-Repeat:

>Fix:
Not applicable.
>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2002-10-19  2:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-18 19:26 hiten [this message]
2002-10-19  2:49 paolo
2003-01-06 19:17 ebotcazou

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=20021019021946.23554.qmail@sources.redhat.com \
    --to=hiten@uk.freebsd.org \
    --cc=gcc-gnats@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: 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).