public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Rainer Orth <ro@TechFak.Uni-Bielefeld.DE> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: ada/6669: Irix6.5 ada bootstrap fail in ada/targparm.adb Date: Mon, 12 May 2003 16:06:00 -0000 [thread overview] Message-ID: <20030512160601.5234.qmail@sources.redhat.com> (raw) The following reply was made to PR ada/6669; it has been noted by GNATS. From: Rainer Orth <ro@TechFak.Uni-Bielefeld.DE> To: Dara Hazeghi <dhazeghi@yahoo.com> Cc: gcc-gnats@gcc.gnu.org, David.Billinghurst@riotinto.com Subject: Re: ada/6669: Irix6.5 ada bootstrap fail in ada/targparm.adb Date: Mon, 12 May 2003 17:58:59 +0200 (MEST) Dara Hazeghi writes: > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit- > trail&database=gcc&pr=6669 > > Hello, > > would it be possible for the submitter to test whether this problem is > still present in current gcc sources (ie 3.2.3 or 3.3 branch)? Thanks, Since the problem lies with the bootstrap compiler (GNAT 3.13p, based on gcc 2.95), it persists. I'm just trying if libgnat on the 3.3 branch can be built (cf. PR ada/6552) so there's no need for a GNAT 3 based bootstrap compiler. Maybe the latest publicly available GNAT 3.15p doesn't have this problem as well; I may check this later. For the time being, my described workaround holds: --- gcc/Makefile.save Mon May 12 17:02:09 2003 +++ gcc/Makefile Mon May 12 17:02:09 2003 @@ -70 +70 @@ -STAGE1_CFLAGS = -g +STAGE1_CFLAGS = Rainer
next reply other threads:[~2003-05-12 16:06 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-05-12 16:06 Rainer Orth [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-14 10:31 giovannibajo 2003-05-12 11:15 giovannibajo 2003-05-10 21:46 Dara Hazeghi 2002-05-15 20:06 Billinghurst, David (CRTS) 2002-05-15 19:36 Rainer Orth 2002-05-15 19:06 David.Billinghurst
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=20030512160601.5234.qmail@sources.redhat.com \ --to=ro@techfak.uni-bielefeld.de \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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: linkBe 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).