Bug 39346 - no mxp target port
Summary: no mxp target port
Status: RESOLVED WONTFIX
Alias: None
Product: gcc
Classification: Unclassified
Component: target (show other bugs)
Version: 4.4.0
: P3 enhancement
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on: 39347 39348 39349
Blocks:
  Show dependency treegraph
 
Reported: 2009-03-02 17:05 UTC by Jorn Wolfgang Rennecke
Modified: 2014-11-09 14:46 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:
Known to work:
Known to fail:
Last reconfirmed:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jorn Wolfgang Rennecke 2009-03-02 17:05:46 UTC
The official FSF gcc doesn't have a target port to ARC's MXP architecture.
Comment 1 Jorn Wolfgang Rennecke 2009-03-19 19:59:34 UTC
This port would be of rather limited use without an ARCompact port
(See PR39303).
It is doubtful that the mxp port will ever be properly finished.
Moreover, due to the lack of overall design and instability of the
instruction set, and a programming model that is different in a number
of aspects from every other GCC target, and in even more aspects different
from the majority of GCC targets, this is a high-maintenance port.
Adding this port to the trunk without a maintainer who is able and willing
to competently maintain this port on an on-going basis would only serve to
impede GCC development.
The port is available in branches/arc-20081210-branch.
Comment 2 Jorn Wolfgang Rennecke 2014-11-09 14:46:29 UTC
target/39346, other/39347 and other/39348 are no longer relevant to other/39363,
because the Successor of ARC International (UK) Ltd, Synopsys, does not offer
an mxp option in its DesignWare ARC Processor Cores lineup.