public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Eric Botcazou <ebotcazou@libertysurf.fr> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: other/9219: [SunOS 5.5] gcc-3.2.1/binutils-2.13.1 problem with perl-5.8.0 Date: Fri, 11 Apr 2003 08:06:00 -0000 [thread overview] Message-ID: <20030411080601.14670.qmail@sources.redhat.com> (raw) The following reply was made to PR other/9219; it has been noted by GNATS. From: Eric Botcazou <ebotcazou@libertysurf.fr> To: warren.dodge@tektronix.com Cc: ebotcazou@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: other/9219: [SunOS 5.5] gcc-3.2.1/binutils-2.13.1 problem with perl-5.8.0 Date: Fri, 11 Apr 2003 10:01:37 +0200 > I guess my hope was that between gcc/binutils/perl people that the problem > could be found. Unfortunately, such a vague report is difficult to treat. But if there are no problems with the Sun compiler, we can probably eliminate Perl itself. > If there are problems with perl what other code will cause problems? We > use gcc/binutils for a wide range of code and it is unsettling to know > there is something possibly wrong. I don't know, but if this is a compiler bug, there are chances that it will resurface elsewhere. > I will try this again with gcc-3.2.2 which I have recently built. You might additionally want to try the current gcc-3_2-branch of the CVS repository, GCC 3.2.2 is known to miscompile Samba and Bind on Sparc for example. -- Eric Botcazou
next reply other threads:[~2003-04-11 8:06 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-04-11 8:06 Eric Botcazou [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-04-10 21:26 Warren L Dodge 2003-04-10 21:16 Warren L Dodge 2003-04-10 14:50 ebotcazou
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=20030411080601.14670.qmail@sources.redhat.com \ --to=ebotcazou@libertysurf.fr \ --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).