RE: other/7254: GCC Error target = MN10200

RE: other/7254: GCC Error target = MN10200

[Chilung Wang]

The following reply was made to PR other/7254; it has been noted by GNATS.

From: "Chilung Wang" <chilung@itri.org.tw>
To: <law@redhat.com>
Cc: <gcc-gnats@gcc.gnu.org>, =?big5?B?vbKp+q31?= <paulie@itri.org.tw>
Subject: RE: other/7254: GCC Error target = MN10200 
Date: Thu, 11 Jul 2002 08:19:30 +0800

 Jeff,
 
 Yes, we plan to use MN10200 parts as the Compiler based for our
 propriety CPU. The CPU is 16 bit data registers and has 20 bit address
 registers. The architecture is very similar to MN10200. We just verify
 our compiler based on GCC 2.95.1 and pass the Testing Suite. We plan to
 upgrade to GCC 3.0 and meet the problem. We want to solve the MN10200
 void problem in order to smooth the upgrade from 2.95.1 to 3.0. Could
 you tell us how to solve the problem we can do it by ourselves.
 
 Chilung
 
 -----Original Message-----
 From: Jeff Law [mailto:law@porcupine.slc.redhat.com] 
 Sent: Thursday, July 11, 2002 2:08 AM
 To: chilung@itri.org.tw
 Cc: gcc-gnats@gcc.gnu.org
 Subject: Re: other/7254: GCC Error target = MN10200 
 
 
 In message <20020710061853.13108.qmail@sources.redhat.com>,
 chilung@itri.org.tw
  writes:
  >
  >>Number:         7254
  >>Category:       other
  >>Synopsis:       GCC Error target = MN10200
  >>Confidential:   no
  >>Severity:       serious
  >>Priority:       medium
  >>Responsible:    unassigned
  >>State:          open
  >>Class:          sw-bug
  >>Submitter-Id:   net
  >>Arrival-Date:   Tue Jul 09 23:26:00 PDT 2002
  >>Closed-Date:
  >>Last-Modified:
  >>Originator:     chilung@itri.org.tw
  >>Release:        GCC 3.1
  >>Organization:
  >>Environment:
  >Linux
  >>Description:
  >The GCC 3.1 Target = MN10200. Compiler the following 
  >
  >====================
  >void f()
  >{
  >}
  >====================
  >
  >A Compiler exception occcurs.
 Note that the mn102 port is currently scheduled to be removed in the
 next major release of GCC as it's currently unmaintained and believed to
 be unused.
 
 Are you planning to use the mn102 port for anything?  If so, what?
 
 jeff
 

Re: other/7254: GCC Error target = MN10200

[giovannibajo]

Synopsis: GCC Error target = MN10200

State-Changed-From-To: feedback->suspended
State-Changed-By: bajo
State-Changed-When: Sat May 10 07:43:42 2003
State-Changed-Why:
    MN10200 is now obsolete, so it's unlikely somebody will
    look at it again.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7254

Re: other/7254: GCC Error target = MN10200

[bangerth]

Synopsis: GCC Error target = MN10200

State-Changed-From-To: open->feedback
State-Changed-By: bangerth
State-Changed-When: Wed Feb 19 14:24:27 2003
State-Changed-Why:
    Steven already explained why.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7254

Re: other/7254: GCC Error target = MN10200

[Steven Bosscher]

The following reply was made to PR other/7254; it has been noted by GNATS.

From: Steven Bosscher <s.bosscher@student.tudelft.nl>
To: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org,
	gcc-prs@gcc.gnu.org, chilung@itri.org.tw
Cc:  
Subject: Re: other/7254: GCC Error target = MN10200
Date: Wed, 19 Feb 2003 14:44:08 +0100

 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7254
 
 This target has been declared obsolete (ref. 
 gcc.gnu.org/gcc-3.3/changes.html):
 
     * Matsushita MN10200, |mn10200-*-*|
 
 The PR hasn't been touched for over half a year now and should be in 
 feedback state.
 
 Greetz
 Steven
 

Re: other/7254: GCC Error target = MN10200

[Jeff Law]

The following reply was made to PR other/7254; it has been noted by GNATS.

From: Jeff Law <law@porcupine.slc.redhat.com>
To: chilung@itri.org.tw
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: other/7254: GCC Error target = MN10200 
Date: Wed, 10 Jul 2002 12:08:20 -0600

 In message <20020710061853.13108.qmail@sources.redhat.com>, chilung@itri.org.tw
  writes:
  >
  >>Number:         7254
  >>Category:       other
  >>Synopsis:       GCC Error target = MN10200
  >>Confidential:   no
  >>Severity:       serious
  >>Priority:       medium
  >>Responsible:    unassigned
  >>State:          open
  >>Class:          sw-bug
  >>Submitter-Id:   net
  >>Arrival-Date:   Tue Jul 09 23:26:00 PDT 2002
  >>Closed-Date:
  >>Last-Modified:
  >>Originator:     chilung@itri.org.tw
  >>Release:        GCC 3.1
  >>Organization:
  >>Environment:
  >Linux
  >>Description:
  >The GCC 3.1 Target = MN10200. Compiler the following 
  >
  >====================
  >void f()
  >{
  >}
  >====================
  >
  >A Compiler exception occcurs.
 Note that the mn102 port is currently scheduled to be removed in the
 next major release of GCC as it's currently unmaintained and believed
 to be unused.
 
 Are you planning to use the mn102 port for anything?  If so, what?
 
 jeff
 

other/7254: GCC Error target = MN10200

[chilung]

>Number:         7254
>Category:       other
>Synopsis:       GCC Error target = MN10200
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Jul 09 23:26:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     chilung@itri.org.tw
>Release:        GCC 3.1
>Organization:
>Environment:
Linux
>Description:
The GCC 3.1 Target = MN10200. Compiler the following 

====================
void f()
{
}
====================

A Compiler exception occcurs.
>How-To-Repeat:
as above
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted: