public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gaius Mulley <gaius.mulley@southwales.ac.uk>
To: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Cc: <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH, Modula-2 (C/C++/D/F/Go/Jit)] (Register spec fn) (v2)
Date: Tue, 09 Jul 2019 11:41:00 -0000	[thread overview]
Message-ID: <87imsbcvw9.fsf@j228-gm.comp.glam.ac.uk> (raw)
In-Reply-To: <yddef2zr34w.fsf@CeBiTec.Uni-Bielefeld.DE> (Rainer Orth's message	of "Tue, 9 Jul 2019 11:03:27 +0200")

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

> here are some initial issues.  I'll reply to Matthias' mail to expand on
> other problems he's raised.
>
> * First, the build broke like this:
>
> /vol/gcc/src/hg/trunk/solaris/gcc/gm2/mc-boot/GRTint.c:57:30: error: 'time' redeclared as different kind of symbol
>    57 | typedef enum {input, output, time} VectorType;
>       |                              ^~~~
> In file included from /usr/include/time.h:12,
>                  from /usr/include/sys/time.h:448,
>                  from /usr/include/sys/select.h:27,
>                  from /usr/include/sys/types.h:665,
>                  from /usr/include/stdlib.h:22,
>                  from /vol/gcc/src/hg/trunk/solaris/gcc/gm2/mc-boot/Glibc.h:15,
>                  from /vol/gcc/src/hg/trunk/solaris/gcc/gm2/mc-boot/GRTint.c:42:
> /usr/include/iso/time_iso.h:96:15: note: previous declaration of 'time' was here
>    96 | extern time_t time(time_t *);
>       |               ^~~~

Hi Rainer,

thanks for the bug report.  Now fixed in the git repro -
the mc bootstrap tool now avoids 'time'.  Also fixed Make-lang.in
to allow parallel builds.

>   I've worked around this by renaming the enum value to vtime.  This
>   problem is likely to occur on other targets as well.
>
> * Building gm2.info failed with the makeinfo I happened to have
>   installed:
>
> makeinfo --split-size=5000000 --split-size=5000000 -I/var/gcc/gcc-10.0.0-20190708/11.5-gcc-gas-gm2-no-bootstrap-j1/gcc/gm2 -o /var/gcc/gcc-10.0.0-20190708/11.5-gcc-gas-gm2-no-bootstrap-j1/gcc/gm2/gm2.info /vol/gcc/src/hg/trunk/solaris/gcc/gm2/gm2.texi
> /vol/gcc/src/hg/trunk/solaris/gcc/gm2/gm2.texi:3070: `Prerequisites' has no Up field (perhaps incorrect sectioning?).
> makeinfo: Removing output file `/var/gcc/gcc-10.0.0-20190708/11.5-gcc-gas-gm2-no-bootstrap-j1/gcc/gm2/gm2.info' due to errors; use --force to preserve.
> make[2]: *** [/vol/gcc/src/hg/trunk/solaris/gcc/gm2/Make-lang.in:234: /var/gcc/gcc-10.0.0-20190708/11.5-gcc-gas-gm2-no-bootstrap-j1/gcc/gm2/gm2.info] Error 1
>
>   This is from texinfo 4.13, newer than the required minimum of 4.7.
>   Even with makeinfo 6.1, there are a couple of warnings:
>
> /vol/gcc/src/hg/trunk/solaris/gcc/gm2/gm2.texi:82: warning: multiple @menu
> /vol/gcc/src/hg/trunk/solaris/gcc/gm2/gm2.texi:581: warning: multiple @menu
> /var/gcc/gcc-10.0.0-20190708/11.5-gcc-gas-gm2-no-bootstrap-j1/gcc/gm2/gm2-libs.texi:6043: warning: multiple @menu
> /vol/gcc/src/hg/trunk/solaris/gcc/gm2/gm2.texi:3070: warning:
> unreferenced node `Prerequisites'

will look into gm2.texi

> Other than that, a sequential (only!) multilibbed build succeeded, and I
> even managed to get some testsuite results which aren't too bad, again
> for both multilibs:
>
>                 === gm2 Summary for unix ===
>
> # of expected passes            7800
> # of unexpected failures        1729
> # of unresolved testcases       1705
>
>                 === gm2 Summary for unix/-m64 ===
>
> # of expected passes            7800
> # of unexpected failures        1729
> # of unresolved testcases       1705
>
>                 === gm2 Summary ===
>
> # of expected passes            15600
> # of unexpected failures        3458
> # of unresolved testcases       3410
>
> 	Rainer


regards,
Gaius

  reply	other threads:[~2019-07-09 11:03 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 [this message]
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
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=87imsbcvw9.fsf@j228-gm.comp.glam.ac.uk \
    --to=gaius.mulley@southwales.ac.uk \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=ro@CeBiTec.Uni-Bielefeld.DE \
    /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).