public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: falk.hueffner@student.uni-tuebingen.de To: gcc-gnats@gcc.gnu.org Subject: target/7021: __builtin_alpha_zapnot gives ICE Date: Thu, 13 Jun 2002 11:16:00 -0000 [thread overview] Message-ID: <20020613180606.11531.qmail@sources.redhat.com> (raw) >Number: 7021 >Category: target >Synopsis: __builtin_alpha_zapnot gives ICE >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: ice-on-legal-code >Submitter-Id: net >Arrival-Date: Thu Jun 13 11:16:02 PDT 2002 >Closed-Date: >Last-Modified: >Originator: falk.hueffner@student.uni-tuebingen.de >Release: CVS 2002-06-13 >Organization: >Environment: Alpha PCA56, Debian GNU/Linux >Description: __builtin_alpha_zapnot with a non-constant second argument gives an ICE. It seems the problem is that in the machine description, the second parameter is declared to be in QI mode, while copy_to_mode_reg (called from alpha_expand_builtin) expects DI. >How-To-Repeat: % cat zapnot.c unsigned long f(unsigned long x, unsigned long y) { return __builtin_alpha_zapnot(x, y); } % gcc -c zapnot.c zapnot.c: In function `f': zapnot.c:2: Internal compiler error: Internal compiler error in copy_to_mode_reg, at explow.c:711 >Fix: Using DI mode everywhere in builtin_zapnot* helps, but the QI was supposedly there to tell the compiler that only the low byte matters, which would get lost then. >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-06-13 18:16 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-06-13 11:16 falk.hueffner [this message] 2002-06-14 16:36 rth
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=20020613180606.11531.qmail@sources.redhat.com \ --to=falk.hueffner@student.uni-tuebingen.de \ --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: 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).