public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: neil@gcc.gnu.org To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org Subject: Re: c/1811 Date: Sun, 01 Apr 2001 00:00:00 -0000 [thread overview] Message-ID: <20010130164601.1639.qmail@sourceware.cygnus.com> (raw) The following reply was made to PR c/1811; it has been noted by GNATS. From: neil@gcc.gnu.org To: david.osborne@nottingham.ac.uk, gcc-gnats@gcc.gnu.org, nobody@gcc.gnu.org Cc: Subject: Re: c/1811 Date: 30 Jan 2001 16:42:06 -0000 Synopsis: gcc (cpp0) fails when compiling BIND 8.2.3 State-Changed-From-To: open->feedback State-Changed-By: neil State-Changed-When: Tue Jan 30 08:42:05 2001 State-Changed-Why: Would you please check if this happens with CVS GCC, or a recent snapshot? That version of CPP was quite buggy and I doubt CVS CPP will segfault. It is hard for me to check your report, since you cannot provide preprocessed source (obviously), and I cannot easily reproduce your setup. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=1811&database=gcc >From stewart@lab43.org Sun Apr 01 00:00:00 2001 From: Rod Stewart <stewart@lab43.org> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org Subject: Re: libstdc++/1608: Problem with TREE_PARMLIST Date: Sun, 01 Apr 2001 00:00:00 -0000 Message-id: <20010125055601.32611.qmail@sourceware.cygnus.com> X-SW-Source: 2001-q1/msg00702.html Content-length: 1909 The following reply was made to PR libstdc++/1608; it has been noted by GNATS. From: Rod Stewart <stewart@lab43.org> To: stewart@netwinder.org Cc: gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, gcc-bugs@gcc.gnu.org Subject: Re: libstdc++/1608: Problem with TREE_PARMLIST Date: Wed, 24 Jan 2001 14:36:37 -0500 (EST) On 10 Jan 2001 stewart@netwinder.org wrote: > >Release: gcc version 2.97 20010109 (experimental) > >Organization: > >Environment: > Shows up in armv4l-unknown-linux-gnu. Actually should show up in any ARM build. > >Description: > I'm entering this so it does not get lost. See the discussion on gcc-bugs for complete analysis of the problem and what the recommened solution is. I don't really understand the problem all that well, so most of this bug report is bringing the urls together of where the discussion took place. > > For now Richard Earnshaw entered a work around to allow builds to occur on ARM again. This problem has been around for over a month. The result of this path is that the Xscale builtins will most likely not work with newlib. See Richard's work around for details on this. > > Original report: > http://gcc.gnu.org/ml/libstdc++/2000-12/msg00098.html > > Start of what the problem is: > http://gcc.gnu.org/ml/libstdc++/2000-12/msg00208.html > > More details: > http://gcc.gnu.org/ml/libstdc++/2000-12/msg00239.html > > >How-To-Repeat: > Revert Richard's patch and do a bootstrap on for an ARM target. > >Fix: > Implement the proper fix from: > http://gcc.gnu.org/ml/libstdc++/2000-12/msg00301.html This was fixed by: http://gcc.gnu.org/ml/gcc-bugs/2001-01/msg00287.html http://gcc.gnu.org/ml/gcc-bugs/2001-01/msg00286.html And the built-ins for ARM/Xscale were re-enabled with: http://gcc.gnu.org/ml/gcc-patches/2001-01/msg01558.html This bug is no longer present, so someone could close it. Thanks, -Rms >From lerdsuwa@gcc.gnu.org Sun Apr 01 00:00:00 2001 From: lerdsuwa@gcc.gnu.org To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org Subject: Re: c++/1637 Date: Sun, 01 Apr 2001 00:00:00 -0000 Message-id: <20010212065601.14819.qmail@sourceware.cygnus.com> X-SW-Source: 2001-q1/msg01161.html Content-length: 534 The following reply was made to PR c++/1637; it has been noted by GNATS. From: lerdsuwa@gcc.gnu.org To: gcc-gnats@gcc.gnu.org, nobody@gcc.gnu.org, wanderer@rsu.ru Cc: Subject: Re: c++/1637 Date: 12 Feb 2001 06:52:23 -0000 Synopsis: compiler internal error on unknown exception name in catch() clause State-Changed-From-To: open->closed State-Changed-By: lerdsuwa State-Changed-When: Sun Feb 11 22:52:23 2001 State-Changed-Why: Fixed in the CVS. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=1637&database=gcc
reply other threads:[~2001-04-01 0:00 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20010130164601.1639.qmail@sourceware.cygnus.com \ --to=neil@gcc.gnu.org \ --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).