public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: sayle@gcc.gnu.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, woudshoo@xs4all.nl Subject: Re: objc/3822: gcc crashes when compiling class that contains bitfield with enums Date: Wed, 03 Jul 2002 06:13:00 -0000 [thread overview] Message-ID: <20020703131341.30622.qmail@sources.redhat.com> (raw) Synopsis: gcc crashes when compiling class that contains bitfield with enums State-Changed-From-To: open->closed State-Changed-By: sayle State-Changed-When: Wed Jul 3 06:13:40 2002 State-Changed-Why: This PR has been fixed by Nicola Pero's 12 Dec 2001 patch. I've confirmed that the ICE is no longer present on mainline. Wed Dec 12 08:35:33 2001 Nicola Pero <n.pero@mi.flashnet.it> * objc/objc-act.c (encode_complete_bitfield): Fixed encoding enumeral types - encode them using 'i'. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=3822
next reply other threads:[~2002-07-03 13:13 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-07-03 6:13 sayle [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-07-25 13:46 woudshoo
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=20020703131341.30622.qmail@sources.redhat.com \ --to=sayle@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ --cc=woudshoo@xs4all.nl \ /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).