public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: fonseca@mip.sdu.dk
To: gcc-gnats@gcc.gnu.org
Subject: c++/9676: internal error in emit_move_insn for static cast of long double to unsigned long long
Date: Wed, 12 Feb 2003 19:46:00 -0000	[thread overview]
Message-ID: <20030212193709.19981.qmail@sources.redhat.com> (raw)


>Number:         9676
>Category:       c++
>Synopsis:       internal error in emit_move_insn for static cast of long double to unsigned long long
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Feb 12 19:46:01 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     fonseca@mip.sdu.dk
>Release:        Confirmed for GCC 3.1.1 and GCC 3.2
>Organization:
>Environment:
686 target.
>Description:
The program below fails to compile with GCC 3.2 (native compiler under x86 GNU/Linux) and GCC 3.1.1 (mingw32 cross compiler under SPARC Solaris).

Changes for GCC 3.2.2 does not seem to mention this problem.

Native GCC 3.2 compiler under x86 GNU/Linux yields:
g++ -O0 -march=i668 internal.cpp
internal.cpp: In function `int main()':
internal.cpp:6: Internal compiler error in emit_move_insn, at expr.c:2769


GCC 3.1.1 cross compiler for mingw32 target under SPARC Solaris yields:
i386-pc-mingw32-gcc -O0 -march=i686 internal.cpp
internal.cpp: In function `int main()':
internal.cpp:6: Internal compiler error in emit_move_insn, at expr.c:
   2769

The program only fails for GCC 3.1.1 if -march=i686 is set!



void myFunction(short) {
}

int main() {
  long double temp = 1;
  myFunction(static_cast<unsigned long long>(temp)); // ERR
  return 0;
}
>How-To-Repeat:

>Fix:

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


                 reply	other threads:[~2003-02-12 19:46 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=20030212193709.19981.qmail@sources.redhat.com \
    --to=fonseca@mip.sdu.dk \
    --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).