public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/100559] Solaris SPARC GCC 11.1 Ada build: i-cexten.ads:278:28: modulus exceeds limit (2 ** 64)
Date: Wed, 12 May 2021 11:38:09 +0000 [thread overview]
Message-ID: <bug-100559-4-PTjO4VtHKO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100559-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100559
--- Comment #8 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> No local changes.
>
> I wonder where i-cexten.ads is being modified...
Unlikely I'd say. Could you go into the $(buildir]/gcc/ada directory and do:
ls -l rts/i-cexten.ads
ls -l rts_32/i-cexten.ads
They should not point to the same source file.
next prev parent reply other threads:[~2021-05-12 11:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-12 7:07 [Bug ada/100559] New: " sumbera at volny dot cz
2021-05-12 7:35 ` [Bug ada/100559] " sumbera at volny dot cz
2021-05-12 10:14 ` ebotcazou at gcc dot gnu.org
2021-05-12 10:17 ` sumbera at volny dot cz
2021-05-12 10:33 ` ebotcazou at gcc dot gnu.org
2021-05-12 10:45 ` sumbera at volny dot cz
2021-05-12 11:08 ` ebotcazou at gcc dot gnu.org
2021-05-12 11:18 ` sumbera at volny dot cz
2021-05-12 11:38 ` ebotcazou at gcc dot gnu.org [this message]
2021-05-12 12:33 ` sumbera at volny dot cz
2021-05-12 14:19 ` ebotcazou at gcc dot gnu.org
2021-05-13 7:45 ` ebotcazou at gcc dot gnu.org
2021-05-13 8:10 ` sumbera at volny dot cz
2021-05-13 8:26 ` [Bug ada/100559] build failure of 32-bit Ada runtime after local modification ebotcazou at gcc dot gnu.org
2021-05-13 8:47 ` sumbera at volny dot cz
2021-05-13 8:50 ` ro at CeBiTec dot Uni-Bielefeld.DE
2021-05-13 8:53 ` sumbera at volny dot cz
2021-05-13 15:43 ` sumbera at volny dot cz
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=bug-100559-4-PTjO4VtHKO@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).