From: Segher Boessenkool <segher@kernel.crashing.org>
To: Gaius Mulley <gaius.mulley@southwales.ac.uk>
Cc: Matthias Klose <doko@ubuntu.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH, Modula-2 (C/C++/D/F/Go/Jit)] (Register spec fn) (v2)
Date: Fri, 12 Jul 2019 15:41:00 -0000 [thread overview]
Message-ID: <20190712154016.GQ14074@gate.crashing.org> (raw)
In-Reply-To: <87ftnch51l.fsf@j228-gm.comp.glam.ac.uk>
On Thu, Jul 11, 2019 at 06:09:10PM +0100, Gaius Mulley wrote:
> Segher Boessenkool <segher@kernel.crashing.org> writes:
>
> > On Thu, Jul 11, 2019 at 12:49:44PM +0100, Gaius Mulley wrote:
> >> Matthias Klose <doko@ubuntu.com> writes:
> >> > powerpc64le-linux-gnu fails to build (search for "unfinished" in the build log)
> >> >
> >> > during RTL pass: final
> >> > ../../src/gcc/gm2/gm2-libs-coroutines/SYSTEM.def: In function '_M2_SYSTEM_init':
> >> > ../../src/gcc/gm2/gm2-libs-coroutines/SYSTEM.def:20: internal compiler error: in
> >> > rs6000_output_function_epilogue, at conf
> >> > ig/rs6000/rs6000.c:29169
> >
> > We don't yet support Modula2 in the traceback tables. I'll add it.
> > What is the exact spelling in lang_hooks.name? "GNU Modula 2"? Or
> > "GNU Modula2"? Or what else :-)
>
> Hi Segher,
>
> very close !
>
> #define LANG_HOOKS_NAME "GNU Modula-2"
>
> >> Hi Matthias,
> >>
> >> many thanks for the build results. There is a newer version of
> >> gm2/Make-lang.in on the 9.1.0 branch which (quietens the output for mc)
> >> and fixes the gm2l execvp (on other platforms).
> >>
> >> The ICE is very interesting!
> >
> > Should I add this to the GCC 9 branch as well? Does that help testing,
> > I mean?
>
> yes please - all that helps is good,
I committed support for this to both trunk and 9 yesterday, fwiw.
Segher
next prev parent reply other threads:[~2019-07-12 15:40 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-14 13:10 Gaius Mulley
2019-06-29 10:15 ` Richard Sandiford
2019-06-29 12:52 ` Richard Biener
2019-06-29 20:29 ` Gaius Mulley
2019-06-29 18:08 ` Segher Boessenkool
2019-07-02 0:18 ` Gaius Mulley
2019-07-03 8:41 ` Rainer Orth
2019-07-08 15:20 ` Gaius Mulley
2019-07-08 15:31 ` Rainer Orth
2019-07-09 9:25 ` Rainer Orth
2019-07-09 11:41 ` Gaius Mulley
2019-07-10 11:50 ` Rainer Orth
2019-07-08 15:41 ` Gaius Mulley
2019-07-08 21:21 ` Matthias Klose
2019-07-09 6:37 ` Matthias Klose
2019-07-09 19:50 ` Gaius Mulley
2019-07-09 21:35 ` Matthias Klose
2019-07-10 17:56 ` Matthias Klose
2019-07-10 20:18 ` Gaius Mulley
2019-07-10 20:38 ` Matthias Klose
2019-07-10 21:16 ` Gaius Mulley
2019-07-09 9:56 ` Matthias Klose
2019-07-09 12:14 ` Gaius Mulley
2019-07-09 13:24 ` Matthias Klose
2019-07-09 13:49 ` Gaius Mulley
2019-07-09 16:23 ` Matthias Klose
2019-07-09 17:22 ` Gaius Mulley
2019-07-09 12:31 ` Rainer Orth
2019-07-09 15:57 ` Gaius Mulley
2019-07-09 17:32 ` Matthias Klose
2019-07-10 20:45 ` Gaius Mulley
2019-07-10 12:11 ` Rainer Orth
2019-07-09 21:36 ` Matthias Klose
2019-07-10 17:11 ` Matthias Klose
2019-07-10 20:49 ` Gaius Mulley
2019-07-11 7:57 ` Matthias Klose
2019-07-11 12:12 ` Gaius Mulley
2019-07-11 16:40 ` Segher Boessenkool
2019-07-11 17:26 ` Gaius Mulley
2019-07-12 15:41 ` Segher Boessenkool [this message]
2019-07-12 18:35 ` Gaius Mulley
2019-07-18 20:15 ` Matthias Klose
2019-11-20 10:10 ` Gaius Mulley
2019-07-19 14:22 ` Matthias Klose
2019-07-20 21:41 ` Matthias Klose
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190712154016.GQ14074@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=doko@ubuntu.com \
--cc=gaius.mulley@southwales.ac.uk \
--cc=gcc-patches@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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).