public inbox for
 help / color / mirror / Atom feed
From: Gaius Mulley <>
To: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Cc: Gaius Mulley via Gcc-patches <>
Subject: Re: [PATCH] 0/19 modula-2 front end patches overview
Date: Wed, 12 Oct 2022 14:06:04 +0100	[thread overview]
Message-ID: <87edvdqjib.fsf@debian> (raw)
In-Reply-To: <ydd7d15b4v8.fsf@CeBiTec.Uni-Bielefeld.DE> (Rainer Orth's message of "Wed, 12 Oct 2022 14:31:23 +0200")

Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE> writes:

> Hi Gaius,
>> Testing
>> =======
> [...]
>> The devel/modula-2 branch has been bootstrapped on:
> [...]
>>    sparc64 solaris
>>    sparc32 solaris
> which versions exactly did you run those bootstraps on?  I'm asking
> because for Solaris 11.4/SPARCV9 (sparcv9-sun-solaris2.11) was fine,
> while Solaris 11.4/SPARC (sparc-sun-solaris2.11) still runs into PR
> modula2/101392 (cc1gm2 -fdump-system-exports SEGV on Solaris/SPARC).

Hi Rainer,

ah very sorry - I thought I was relaying a summary of your findings.
Thanks for the clarification and detailed correction.

> For good measure, I also tried Solaris 11.3/SPARC (matching gcc211 in
> the cfarm), but that only revealed a couple of additional issues not
> seen on 11.4:
> modula2/107233	gm2 build hardcodes python3
> modula2/107234	Format error in (m2pp_integer_cst)
> modula2/107235	m2/boot-bin/mc leaks file descriptors
> before running into the same SEGV in the end.

thanks for the PRs above - will apply fixes to the first two and
examine the 3rd (again).

> Just for the record, both Solaris 11.4/amd64 (amd64-pc-solaris2.11) and
> Solaris 11.4/i386 (i386-pc-solaris2.11) are fine.

great news and thanks for this report,


  reply	other threads:[~2022-10-12 13:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-10 15:31 Gaius Mulley
2022-10-12 12:31 ` Rainer Orth
2022-10-12 13:06   ` Gaius Mulley [this message]
2022-11-11 14:02 ` Richard Biener
2022-11-14 13:57   ` Gaius Mulley
2022-11-30 13:29   ` Richard Biener
2022-12-05 13:33     ` Gaius Mulley

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87edvdqjib.fsf@debian \ \ \
    --cc=ro@CeBiTec.Uni-Bielefeld.DE \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).