public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tprince at computer dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/23808] New: ICE in convert-move, building libgfortran with tree-vectorize
Date: Sat, 10 Sep 2005 16:28:00 -0000	[thread overview]
Message-ID: <20050910162828.23808.tprince@computer.org> (raw)

GNU C version 4.1.0 20050909 (experimental) (x86_64-unknown-linux-gnu)
        compiled by GNU C version 4.1.0 20050909 (experimental).
GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096
Compiler executable checksum: f9d7f64473108ed4ae233ca41e01773c
GNU assembler version 2.14.90.0.4 (x86_64-redhat-linux) using BFD version 2.14.9
0.0.4 20030523
../../../libgfortran/generated/maxloc0_4_i4.c: In function 'mmaxloc0_4_i4':
../../../libgfortran/generated/maxloc0_4_i4.c:231: internal compiler error: in c
onvert_move, at expr.c:390

-- 
           Summary: ICE in convert-move, building libgfortran with tree-
                    vectorize
           Product: gcc
           Version: 4.1.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: c
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: tprince at computer dot org
                CC: gcc-bugs at gcc dot gnu dot org
 GCC build triplet: x86_64-unknown-linux-gnu
  GCC host triplet: x86_64-unknown-linux-gnu
GCC target triplet: x86_64-unknown-linux-gnu


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23808


             reply	other threads:[~2005-09-10 16:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-10 16:28 tprince at computer dot org [this message]
2005-09-10 16:29 ` [Bug tree-optimization/23808] " pinskia at gcc dot gnu dot org
2005-09-10 16:31 ` pinskia at gcc dot gnu dot org

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=20050910162828.23808.tprince@computer.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).