public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "echristo@redhat.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/7831] [mips] GCC 3.2 MIPS64 endian issues
Date: Mon, 02 Jun 2003 22:38:00 -0000	[thread overview]
Message-ID: <20030602223830.32130.qmail@sources.redhat.com> (raw)
In-Reply-To: <20020904185600.7831.cvansch@cse.unsw.edu.au>

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

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



------- Additional Comments From echristo@redhat.com  2003-06-02 22:38 -------
Subject: Re:  [mips] GCC 3.2 MIPS64 endian issues


> 
> sorry to bother you with yet another MIPS bug report. This one looks pretty straightforward 
> though. Any insights? Thanks,

I think we should suspend this one pending more info. There's nothing
that -EL should do that configuring for mipsel shouldn't. I think we
need the more information that was asked (a complete testcase would be
nice).

-eric





------- 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 22:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20020904185600.7831.cvansch@cse.unsw.edu.au>
2003-05-26  4:25 ` dhazeghi@yahoo.com
2003-05-26  4:29 ` pinskia@physics.uc.edu
2003-06-02  4:12 ` dhazeghi@yahoo.com
2003-06-02 22:38 ` echristo@redhat.com [this message]
2003-06-03 10:25 ` dhazeghi@yahoo.com
2003-08-22  9:27 ` rsandifo 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=20030602223830.32130.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).