public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug target/7831] [mips] GCC 3.2 MIPS64 endian issues
       [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
                   ` (4 subsequent siblings)
  5 siblings, 0 replies; 6+ messages in thread
From: dhazeghi@yahoo.com @ 2003-05-26  4:25 UTC (permalink / raw)
  To: gcc-bugs

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 dhazeghi@yahoo.com  2003-05-26 04:16 -------
Hello,

would it be possible for you to check whether this problem is still present in gcc 3.3? Also, a 
testcase of pre-processed source would be very much appreciated (makes it possible to reproduce 
bugs on cross compilers without target headers). Thanks,

Dara



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


^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug target/7831] [mips] GCC 3.2 MIPS64 endian issues
       [not found] <20020904185600.7831.cvansch@cse.unsw.edu.au>
  2003-05-26  4:25 ` [Bug target/7831] [mips] GCC 3.2 MIPS64 endian issues dhazeghi@yahoo.com
@ 2003-05-26  4:29 ` pinskia@physics.uc.edu
  2003-06-02  4:12 ` dhazeghi@yahoo.com
                   ` (3 subsequent siblings)
  5 siblings, 0 replies; 6+ messages in thread
From: pinskia@physics.uc.edu @ 2003-05-26  4:29 UTC (permalink / raw)
  To: gcc-bugs

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


pinskia@physics.uc.edu changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |WAITING


------- Additional Comments From pinskia@physics.uc.edu  2003-05-26 04:17 -------
See Dara's question.



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


^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug target/7831] [mips] GCC 3.2 MIPS64 endian issues
       [not found] <20020904185600.7831.cvansch@cse.unsw.edu.au>
  2003-05-26  4:25 ` [Bug target/7831] [mips] GCC 3.2 MIPS64 endian issues 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
                   ` (2 subsequent siblings)
  5 siblings, 0 replies; 6+ messages in thread
From: dhazeghi@yahoo.com @ 2003-06-02  4:12 UTC (permalink / raw)
  To: gcc-bugs

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


dhazeghi@yahoo.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |echristo@redhat.com
  GCC build triplet|                            |i686-pc-linux-gnu
   GCC host triplet|                            |i686-pc-linux-gnu
 GCC target triplet|                            |mips64el-elf


------- Additional Comments From dhazeghi@yahoo.com  2003-06-02 04:12 -------
Eric,

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

Dara



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


^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug target/7831] [mips] GCC 3.2 MIPS64 endian issues
       [not found] <20020904185600.7831.cvansch@cse.unsw.edu.au>
                   ` (2 preceding siblings ...)
  2003-06-02  4:12 ` dhazeghi@yahoo.com
@ 2003-06-02 22:38 ` echristo@redhat.com
  2003-06-03 10:25 ` dhazeghi@yahoo.com
  2003-08-22  9:27 ` rsandifo at gcc dot gnu dot org
  5 siblings, 0 replies; 6+ messages in thread
From: echristo@redhat.com @ 2003-06-02 22:38 UTC (permalink / raw)
  To: gcc-bugs

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.


^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug target/7831] [mips] GCC 3.2 MIPS64 endian issues
       [not found] <20020904185600.7831.cvansch@cse.unsw.edu.au>
                   ` (3 preceding siblings ...)
  2003-06-02 22:38 ` echristo@redhat.com
@ 2003-06-03 10:25 ` dhazeghi@yahoo.com
  2003-08-22  9:27 ` rsandifo at gcc dot gnu dot org
  5 siblings, 0 replies; 6+ messages in thread
From: dhazeghi@yahoo.com @ 2003-06-03 10:25 UTC (permalink / raw)
  To: gcc-bugs

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 dhazeghi@yahoo.com  2003-06-03 10:25 -------
Still waiting for confirmation. Could the original submitter please try to 
reproduce this with gcc 3.3, and if that fails, send a testcase?

Dara

(I think waiting is more appropriate than suspended, since that's what this 
bug's doing right now...)



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


^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug target/7831] [mips] GCC 3.2 MIPS64 endian issues
       [not found] <20020904185600.7831.cvansch@cse.unsw.edu.au>
                   ` (4 preceding siblings ...)
  2003-06-03 10:25 ` dhazeghi@yahoo.com
@ 2003-08-22  9:27 ` rsandifo at gcc dot gnu dot org
  5 siblings, 0 replies; 6+ messages in thread
From: rsandifo at gcc dot gnu dot org @ 2003-08-22  9:27 UTC (permalink / raw)
  To: gcc-bugs

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


rsandifo at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |RESOLVED
         Resolution|                            |FIXED


------- Additional Comments From rsandifo at gcc dot gnu dot org  2003-08-22 09:27 -------
No feedback in three months.  Test case seems to be compiled correctly
by CVS head.


^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2003-08-22  9:27 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <20020904185600.7831.cvansch@cse.unsw.edu.au>
2003-05-26  4:25 ` [Bug target/7831] [mips] GCC 3.2 MIPS64 endian issues 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
2003-06-03 10:25 ` dhazeghi@yahoo.com
2003-08-22  9:27 ` rsandifo at gcc dot gnu dot org

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