On Mär 17 2025, Robert Dubner wrote:
>> -Original Message-
>> From: Andreas Schwab
>> Sent: Monday, March 17, 2025 04:13
>> To: James K. Lowden
>> Cc: gcc-patches@gcc.gnu.org
>> Subject: Re: [PATCH] COBOL v3: 3/14 80K bld: config and build machinery
&
> -Original Message-
> From: Andreas Schwab
> Sent: Monday, March 17, 2025 04:13
> To: James K. Lowden
> Cc: gcc-patches@gcc.gnu.org
> Subject: Re: [PATCH] COBOL v3: 3/14 80K bld: config and build machinery
>
> On Mär 13 2025, James K. Lowden wrote:
>
>
> -Original Message-
> From: Andreas Schwab
> Sent: Monday, March 17, 2025 04:13
> To: James K. Lowden
> Cc: gcc-patches@gcc.gnu.org
> Subject: Re: [PATCH] COBOL v3: 3/14 80K bld: config and build machinery
>
> On Mär 13 2025, James K. Lowden wrote:
>
>
On Mon, Mar 17, 2025 at 9:14 AM Andreas Schwab wrote:
>
> On Mär 13 2025, James K. Lowden wrote:
>
> > On Tue, 11 Mar 2025 11:18:22 +0100
> > Andreas Schwab wrote:
> >
> >> libgcobol/configure.tgt says it's supported on powerpc64le.
> >
> > Our intention, tell me if you disagree, is that cobol is
Andreas Schwab writes:
> On Mär 13 2025, James K. Lowden wrote:
>
>> On Tue, 11 Mar 2025 11:18:22 +0100
>> Andreas Schwab wrote:
>>
>>> libgcobol/configure.tgt says it's supported on powerpc64le.
>>
>> Our intention, tell me if you disagree, is that cobol is enabled if
>>
>> 1. --enable-languag
On Mär 13 2025, James K. Lowden wrote:
> On Tue, 11 Mar 2025 11:18:22 +0100
> Andreas Schwab wrote:
>
>> libgcobol/configure.tgt says it's supported on powerpc64le.
>
> Our intention, tell me if you disagree, is that cobol is enabled if
>
> 1. --enable-languages=all, and
> 2. the host and targe
> -Original Message-
> From: Rainer Orth
> Sent: Thursday, March 13, 2025 15:07
> To: James K. Lowden
> Cc: Andreas Schwab ; gcc-patches@gcc.gnu.org
> Subject: Re: [PATCH] COBOL v3: 3/14 80K bld: config and build machinery
>
> Hi James,
>
> > Our i
On Thu, 13 Mar 2025 20:06:58 +0100
Rainer Orth wrote:
> Hi James,
>
> > Our intention, tell me if you disagree, is that cobol is enabled if
> >
> > 1. --enable-languages=all, and
> > 2. the host and target are "known good", x86_64 or aarch64
>
> you tend to forget there's a world outside of L
On Thu, 13 Mar 2025 14:45:23 -0400
Paul Koning wrote:
> > 3. --enable-languages=cobol, and
> > 4. the host and target are "plausible", 64-bit LE.
>
> Why does it need LE? I understand 64 bits. I might try it on my
> PowerPC based Mac. :-)
That's a good point. "Need" I don't know. I'm not
On Thu, Mar 13, 2025 at 06:33:08PM -0400, James K. Lowden wrote:
> I guess the most controversial engineering choice was to rely on
> __int128 and _Float128. Those gave us native processing and binary <->
> string conversion. Having been advised of real.cc, we're taking a
> look. If we can get 1
On Tue, 11 Mar 2025 11:18:22 +0100
Andreas Schwab wrote:
> > +
> > +# It's early days for COBOL, and it is known to compile on only
> > some host and +# target systems. We remove COBOL from other builds
> > with a warning. +
> > +cobol_is_okay_host="no"
> > +cobol_is_okay_target="no"
> > +
> >
Hi James,
> Our intention, tell me if you disagree, is that cobol is enabled if
>
> 1. --enable-languages=all, and
> 2. the host and target are "known good", x86_64 or aarch64
you tend to forget there's a world outside of Linux, actually: as you
can see at least in PRs cobol/119217 and cobol/11
> On Mar 13, 2025, at 2:33 PM, James K. Lowden wrote:
>
> ...
> 3. --enable-languages=cobol, and
> 4. the host and target are "plausible", 64-bit LE.
Why does it need LE? I understand 64 bits. I might try it on my PowerPC based
Mac. :-)
paul
On Feb 18 2025, James K. Lowden wrote:
> @@ -2525,6 +2543,36 @@ directories, to avoid imposing the performance cost of
>missing_languages=`echo "$missing_languages" | sed -e "s/^,//" -e "s/,$//"`
>stage1_languages=`echo "$stage1_languages" | sed -e "s/^,//" -e "s/,$//"`
>new_enable_lan
14 matches
Mail list logo