public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "Billinghurst, David \(CRTS\)" <David.Billinghurst@riotinto.com> To: billingd@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: fortran/3392: ICE in function_arg, at config/mips/mips.c:4007 Date: Tue, 22 Jan 2002 15:36:00 -0000 [thread overview] Message-ID: <20020122233601.13206.qmail@sources.redhat.com> (raw) The following reply was made to PR fortran/3392; it has been noted by GNATS. From: "Billinghurst, David (CRTS)" <David.Billinghurst@riotinto.com> To: <gcc-gnats@gcc.gnu.org>, <reichelt@igpm.rwth-aachen.de>, <toon@moene.indiv.nluug.nl> Cc: Subject: Re: fortran/3392: ICE in function_arg, at config/mips/mips.c:4007 Date: Wed, 23 Jan 2002 07:29:04 +0800 I some more information on this. I strongly suspect that the patch that = causes the problem is: 2001-05-03 Alexandre Oliva <aoliva@redhat.com> Re-installed 2001-01-09's patch: * hwint.h (HOST_BITS_PER_WIDE_INT, HOST_WIDE_INT): Use long long if it's wider than long and the target's long is wider than the host's.=20 See http://gcc.gnu.org/ml/gcc-bugs/2001-05/msg00112.html, which suggests = that may expose latent bugs for 32-bit > 64-bit cross-compilation - = exactly the problem we are seeing - and suggests some fixes. The patch = went in at 2001-05-03 11:58:43 UTC, and broke irix bootstrap. A gcc = from just prior does not fail the tests. =20
next reply other threads:[~2002-01-22 23:36 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-01-22 15:36 Billinghurst, David (CRTS) [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-02-05 15:28 billingd 2002-02-05 1:29 rth 2002-01-22 15:16 Billinghurst, David (CRTS) 2002-01-22 15:01 billingd 2001-06-24 19:56 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=20020122233601.13206.qmail@sources.redhat.com \ --to=david.billinghurst@riotinto.com \ --cc=billingd@gcc.gnu.org \ --cc=gcc-prs@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).