public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: ciceron@gcc.gnu.org To: SSchober@web.de, ciceron@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org Subject: Re: c/3680: gcc 3.0 for mc68hc12 crashes when compiling libgcc2.c(__muldi3) Date: Mon, 16 Jul 2001 11:57:00 -0000 [thread overview] Message-ID: <20010716185748.4753.qmail@sourceware.cygnus.com> (raw) Synopsis: gcc 3.0 for mc68hc12 crashes when compiling libgcc2.c(__muldi3) Responsible-Changed-From-To: unassigned->ciceron Responsible-Changed-By: ciceron Responsible-Changed-When: Mon Jul 16 11:57:47 2001 Responsible-Changed-Why: maintainer of hc11/hc12 port State-Changed-From-To: open->analyzed State-Changed-By: ciceron State-Changed-When: Mon Jul 16 11:57:47 2001 State-Changed-Why: Problem known, fixed by http://gcc.gnu.org/ml/gcc-patches/2000-12/msg00324.html [RFA]: Don't abort in gen_highpart() http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=3680&database=gcc
next reply other threads:[~2001-07-16 11:57 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-07-16 11:57 ciceron [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-10-01 4:59 ciceron 2001-07-13 10:46 SSchober
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=20010716185748.4753.qmail@sourceware.cygnus.com \ --to=ciceron@gcc.gnu.org \ --cc=SSchober@web.de \ --cc=gcc-bugs@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).