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 target/8795] [PPC] Altivec related bugs concerning gcc3.2.1 and gcc3.3
Date: Mon, 02 Jun 2003 04:58:00 -0000	[thread overview]
Message-ID: <20030602045823.21636.qmail@sources.redhat.com> (raw)
In-Reply-To: <20021203065606.8795.kostadindabov@terascale-euro.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=8795


dhazeghi@yahoo.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |aldyh@redhat.com
             Status|WAITING                     |NEW
     Ever Confirmed|                            |1
  GCC build triplet|                            |powerpc-yellowdog-linux-gnu
   GCC host triplet|                            |powerpc-yellowdog-linux-gnu
 GCC target triplet|                            |powerpc-yellowdog-linux-gnu
   Last reconfirmed|0000-00-00 00:00:00         |2003-06-02 04:58:23
               date|                            |


------- Additional Comments From dhazeghi@yahoo.com  2003-06-02 04:58 -------
Thanks for the testcases. Aldy, would you mind taking a look at this and commenting? Thanks,

Dara 



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


  parent reply	other threads:[~2003-06-02  4:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20021203065606.8795.kostadindabov@terascale-euro.com>
2003-05-26  5:37 ` dhazeghi@yahoo.com
2003-05-26 14:04 ` pinskia@physics.uc.edu
2003-06-02  4:58 ` dhazeghi@yahoo.com [this message]
2003-07-12  6:25 ` [Bug target/8795] [PPC] Altivec related bugs concerning gcc 3.3 and mainline dhazeghi at yahoo dot com
2003-08-06  0:44 ` pinskia at physics dot uc dot edu
2003-08-14  1:30 ` pinskia at gcc dot gnu dot org
2003-08-23 15:36 ` pinskia at gcc dot gnu dot org
2003-08-25 15:47 ` cvs-commit at gcc dot gnu dot org
2003-08-25 15:49 ` mmitchel at gcc dot gnu dot org
2003-08-25 16:58 ` cvs-commit at gcc dot gnu dot org
2003-12-09 17:38 ` dhazeghi at yahoo dot com
2004-05-12 11:00 ` cvs-commit at gcc dot gnu dot org
2004-05-12 11:38 ` cvs-commit at gcc dot gnu dot org
2004-05-12 11:54 ` cvs-commit at gcc dot gnu dot org
2004-05-12 11:57 ` cvs-commit 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=20030602045823.21636.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).