public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: rth@gcc.gnu.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, mmitchel@gcc.gnu.org, philb@gnu.org, rth@gcc.gnu.org Subject: Re: target/2828: arm-linux: cc1 consumes all memory [regression from 2.95] Date: Thu, 07 Jun 2001 16:11:00 -0000 [thread overview] Message-ID: <20010607231150.29291.qmail@sourceware.cygnus.com> (raw) Synopsis: arm-linux: cc1 consumes all memory [regression from 2.95] Responsible-Changed-From-To: mmitchel->rth Responsible-Changed-By: rth Responsible-Changed-When: Thu Jun 7 16:11:49 2001 Responsible-Changed-Why: Mine. State-Changed-From-To: analyzed->closed State-Changed-By: rth State-Changed-When: Thu Jun 7 16:11:49 2001 State-Changed-Why: http://gcc.gnu.org/ml/gcc-patches/2001-06/msg00271.html http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=2828&database=gcc
next reply other threads:[~2001-06-07 16:11 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-06-07 16:11 rth [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-05-15 10:16 philb
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=20010607231150.29291.qmail@sourceware.cygnus.com \ --to=rth@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=mmitchel@gcc.gnu.org \ --cc=philb@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).