This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: It's target deprecation season again!
- From: "Unruh, Erwin" <Erwin dot Unruh at fujitsu-siemens dot com>
- To: GCC mailing list <gcc at gcc dot gnu dot org>
- Cc: "Unruh, Erwin" <Erwin dot Unruh at fujitsu-siemens dot com>
- Date: Wed, 23 Oct 2002 13:34:16 +0200
- Subject: Re: It's target deprecation season again!
> The i370 and s390 targets are for the same architecture. They are not
> entirely redundant; each supports operating environments that the
> other doesn't. However, the s390 target is actively maintained, the
> i370 isn't, and HOST_EBCDIC doesn't really work. I would like to
> suggest, therefore, that we drop (a) the i370, and (b) any pretense of
> supporting EBCDIC as the primary character encoding for the host. (It
> is much, much easier to support it in the target.)
I do not care about those two targets, but I do care for the EBCDIC support. We
(at FSC) are using GCC as an internal tool. It runs on a system with both host
and target being EBCDIC.
I have run into a few problems with the EBCDIC support (in GCC 3.0.4):
In cppinit.c the static function "opt_comp" needs the definiton of "p1" and "p2"
defined later in this file. The call to qsort needs the size of "struct
cl_option" defined later in this file. I could solve this problem by
re-ordering the function definitions in this file.
In libiberty/safe-ctype.c I added a complete case for EBCDIC, using a check like
#elif '\n' == 0x15 && ' ' == 0x40 && '0' == 0xF0 \
&& 'A' == 0xC1 && 'a' == 0x81 && '!' == 0x5A \
&& 'J' == 0xD1 && 'j' == 0x91 && EOF == -1
I had to re-create c-parse.c with an EBCDIC bison.
In tradcif.y use TARGET_ESC instead of hardcoded "033".
Please do not to drop the EBCDIC support.
Thanks
Erwin
Erwin Unruh, Fujitsu Siemens Computers, C/C++ compiler group