On Sun, 11 Aug 2024, Wilken Gottwalt wrote:
>> I noticed this has not been pushed yet and believe Wilken does not have
>> write/push access - so just pushed this on his behalf.
>>
>> Wilken, it may be good to note this as part of patch submission.
> Thank for pushing this. But now I'm a bit confu
Wilken Gottwalt writes:
> On Sat, 10 Aug 2024 13:43:33 +0200 (CEST)
> Gerald Pfeifer wrote:
>
>> On Tue, 23 Jul 2024, Gaius Mulley wrote:
>> >> gcc/gm2:
>> >> * gm2-libs-iso/MemStream.mod: Guard debug output.
>> > many thanks!
>>
>> I noticed this has not been pushed yet and believe Wilken do
On Sat, 10 Aug 2024 13:43:33 +0200 (CEST)
Gerald Pfeifer wrote:
> On Tue, 23 Jul 2024, Gaius Mulley wrote:
> >> gcc/gm2:
> >>* gm2-libs-iso/MemStream.mod: Guard debug output.
> > many thanks!
>
> I noticed this has not been pushed yet and believe Wilken does not have
> write/push access - s
On Tue, 23 Jul 2024, Gaius Mulley wrote:
>> gcc/gm2:
>> * gm2-libs-iso/MemStream.mod: Guard debug output.
> many thanks!
I noticed this has not been pushed yet and believe Wilken does not have
write/push access - so just pushed this on his behalf.
Wilken, it may be good to note this as part
Wilken Gottwalt writes:
> The Close() procedure in MemStream is missing a guard to prevent it from
> printing in non-debug mode.
>
> gcc/gm2:
> * gm2-libs-iso/MemStream.mod: Guard debug output.
>
> Signed-off-by: Wilken Gottwalt
> ---
> gcc/m2/gm2-libs-iso/MemStream.mod | 5 -
> 1 fil
The Close() procedure in MemStream is missing a guard to prevent it from
printing in non-debug mode.
gcc/gm2:
* gm2-libs-iso/MemStream.mod: Guard debug output.
Signed-off-by: Wilken Gottwalt
---
gcc/m2/gm2-libs-iso/MemStream.mod | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
