public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dhazeghi@yahoo.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug optimization/6860] [3.3/3.4 regression] [arm-thumb] pre_insert_copy_insn
Date: Wed, 04 Jun 2003 00:48:00 -0000	[thread overview]
Message-ID: <20030604004843.29040.qmail@sources.redhat.com> (raw)
In-Reply-To: <20020529124601.6860.dwelch@zianet.com>

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

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


dhazeghi@yahoo.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  GCC build triplet|                            |i686-pc-linux-gnu
   GCC host triplet|                            |i686-pc-linux-gnu
 GCC target triplet|                            |arm-thumb-elf
   Last reconfirmed|0000-00-00 00:00:00         |2003-06-04 00:48:43
               date|                            |


------- Additional Comments From dhazeghi@yahoo.com  2003-06-04 00:48 -------
Confirmed still present with gcc 3.2.3, 3.3 branch and mainline (20030602).



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


       reply	other threads:[~2003-06-04  0:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20020529124601.6860.dwelch@zianet.com>
2003-06-04  0:48 ` dhazeghi@yahoo.com [this message]
2003-06-08 18:47 ` [Bug optimization/6860] [3.3/3.4 regression] [arm-thumb] ICE in pre_insert_copy_insn pinskia@physics.uc.edu
2003-07-09 21:47 ` dhazeghi at yahoo dot com

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=20030604004843.29040.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).