public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/12085] [3.3/3.4 Regression] Internal compiler error in convert_move, at expr.c:504 with -O3 flag
Date: Thu, 28 Aug 2003 15:36:00 -0000	[thread overview]
Message-ID: <20030828153640.9929.qmail@sources.redhat.com> (raw)
In-Reply-To: <20030828011711.12085.dhollen@mosis.org>

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

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


pinskia at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |NEW
          Component|middle-end                  |c
     Ever Confirmed|                            |1
  GCC build triplet|sparc-sun-solaris2.8        |
   GCC host triplet|sparc-sun-solaris2.8        |
 GCC target triplet|sparc-sun-solaris2.8        |
   Last reconfirmed|0000-00-00 00:00:00         |2003-08-28 15:36:40
               date|                            |
            Summary|Internal compiler error in  |[3.3/3.4 Regression]
                   |convert_move, at expr.c:504 |Internal compiler error in
                   |with -O3 flag               |convert_move, at expr.c:504
                   |                            |with -O3 flag
   Target Milestone|---                         |3.3.2


------- Additional Comments From pinskia at gcc dot gnu dot org  2003-08-28 15:36 -------
I do not know if it is a middle-end problem or a c front-end problem
I can confirm this on the mainline (20030828).
>From Phil's regression hunter: Search converges between 2001-11-11-trunk (#45) and 2001-11-
18-trunk (#46).
I also want to say this is valid code as you almost can do any casting in C.
This is a regression from 2.95.3 where it worked.


  parent reply	other threads:[~2003-08-28 15:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-28  1:17 [Bug c/12085] New: " dhollen at mosis dot org
2003-08-28  1:21 ` [Bug middle-end/12085] " pinskia at gcc dot gnu dot org
2003-08-28  4:20 ` pinskia at gcc dot gnu dot org
2003-08-28 15:23 ` dhollen at mosis dot org
2003-08-28 15:36 ` pinskia at gcc dot gnu dot org [this message]
2003-08-29 16:35 ` [Bug optimization/12085] [3.3/3.4 Regression] " pinskia at gcc dot gnu dot org
2003-09-07 16:26 ` ebotcazou at gcc dot gnu dot org
2003-10-16  9:29 ` mmitchel at gcc dot gnu dot org
2003-12-05 20:33 ` ebotcazou at gcc dot gnu dot org
2003-12-20  7:40 ` [Bug c/12085] " cvs-commit at gcc dot gnu dot org
2003-12-20  7:41 ` ebotcazou at gcc dot gnu dot org
2004-10-15 12:51 ` 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=20030828153640.9929.qmail@sources.redhat.com \
    --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).