From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: "Roger Sayle" <roger@nextmovesoftware.com>, <gcc-patches@gcc.gnu.org>
Subject: Re: [PING] PR middle-end/95126: Expand small const structs as immediate constants
Date: Mon, 06 Jun 2022 14:01:43 +0200 [thread overview]
Message-ID: <yddmteqyp94.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <874k0yhwjq.fsf@igel.home> (Andreas Schwab's message of "Mon, 06 Jun 2022 13:16:09 +0200")
Andreas Schwab <schwab@linux-m68k.org> writes:
> On Jun 06 2022, Roger Sayle wrote:
>
>> gcc -std=gnu99 -c -g -gnatpg -gnatwns -gnata -W -Wall -I- -I.
>> -Iada/generated -Iada -I../../gcc/gcc/ada ../../gcc/gcc/ada/osint.adb -o
>> ada/osint.o
>> osint.adb:438:31: "strlen" not declared in "CRTL"
>> osint.adb:441:14: "strncpy" not declared in "CRTL"
>> osint.adb:675:21: "strlen" not declared in "CRTL"
>> osint.adb:728:16: "Open_Append" is undefined
>> osint.adb:1108:41: "int64" not declared in "CRTL"
>> osint.adb:3144:28: "strlen" not declared in "CRTL"
>> osint.adb:3147:11: "strncpy" not declared in "CRTL"
>
> What's your bootstrap compiler?
FWIW, I'm using GCC 9 (9.4.0 on Solaris/x86, 9.3.0 on Linux/x86_64) as
bootstrap compiler.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
next prev parent reply other threads:[~2022-06-06 12:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-21 10:49 Roger Sayle
2022-06-05 17:53 ` Andreas Schwab
2022-06-05 20:31 ` Rainer Orth
2022-06-06 8:43 ` Roger Sayle
2022-06-06 11:16 ` Andreas Schwab
2022-06-06 11:23 ` Roger Sayle
2022-06-06 11:44 ` Andreas Schwab
2022-06-06 12:01 ` Rainer Orth [this message]
2022-06-06 12:00 ` Rainer Orth
2022-06-06 12:29 ` Roger Sayle
2022-06-06 15:52 ` Rainer Orth
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=yddmteqyp94.fsf@CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=roger@nextmovesoftware.com \
--cc=schwab@linux-m68k.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).