This is the mail archive of the
mailing list for the GCC project.
Re: gcc 3.4.6 asm charset error
- From: "Paul Edwards" <mutazilah at gmail dot com>
- To: "Segher Boessenkool" <segher at kernel dot crashing dot org>
- Cc: <gcc at gcc dot gnu dot org>
- Date: Fri, 23 Sep 2016 14:34:11 +1000
- Subject: Re: gcc 3.4.6 asm charset error
- Authentication-results: sourceware.org; auth=none
- References: <CFC5C6349D344D5798D28DFA7917F754@PaulDell> <20160922202130.GA6021@gate.crashing.org>
GCC 3.4.6 is the last version of GCC that
supports the i370 target that I use.
Last time I tried adding the i370 target
from GCC 3.4.6 to GCC 4.x I got errors
that I don't know how to fix.
Actually GCC 3.4.6 also has errors which
I don't know how to fix, so I normally
use GCC 3.2.3.
I hope one day someone with the
required technical skills will volunteer
to fix the remaining problems with
GCC on MVS, and i370 will be a target
once again in the latest GCC, but
no-one has volunteered to clean it
up for more than a decade.
From: Segher Boessenkool
Sent: Friday, September 23, 2016 6:21 AM
To: Paul Edwards
Subject: Re: gcc 3.4.6 asm charset error
On Thu, Sep 22, 2016 at 05:35:22PM +1000, Paul Edwards wrote:
GCC 3.4.6 natively handles different character
sets for source and target. It actually works
fine, writing source code in ASCII targeting
an EBCDIC destination.
However, __asm() doesn't seem to be working.
As seen below, it is generating EBCDIC data
in the ASCII assembler output. Those funny
characters are in fact the EBCDIC code for
"ABC" and "DEF".
Anyone know how to fix this?
Does it work better with a GCC version that is less than ten years old?