public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ices.utexas.edu> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: RE: c++/10366: Unable to apply __attribute__ ((packed)) to an enu m (fwd) Date: Wed, 09 Apr 2003 22:06:00 -0000 [thread overview] Message-ID: <20030409220601.10993.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/10366; it has been noted by GNATS. From: Wolfgang Bangerth <bangerth@ices.utexas.edu> To: gcc-gnats@gcc.gnu.org Cc: Subject: RE: c++/10366: Unable to apply __attribute__ ((packed)) to an enu m (fwd) Date: Wed, 9 Apr 2003 17:04:54 -0500 (CDT) ---------- Forwarded message ---------- Date: Wed, 9 Apr 2003 15:02:18 -0700 From: Berger David-MGI2063 <dberger@motorola.com> To: 'Wolfgang Bangerth' <bangerth@ices.utexas.edu> Subject: RE: c++/10366: Unable to apply __attribute__ ((packed)) to an enu m Compile the attachment as follows: gcc -o junk.s -O2 -S junk.c Look at the resulting assembly output in junk.s and it should be relatively easy to stop. So far I've seen the bug on x86, Sparc, and MIPS. It's definitely a front end optimizer problem. David -----Original Message----- From: Wolfgang Bangerth [mailto:bangerth@ices.utexas.edu] Sent: Wednesday, April 09, 2003 2:58 PM To: Berger David-MGI2063 Cc: gcc-bugs@gcc.gnu.org; gcc-gnats@gcc.gnu.org Subject: RE: c++/10366: Unable to apply __attribute__ ((packed)) to an enu m > Any idea when that will be released? That's an FAQ, and the answer is "when it's ready". I don't think this is going to happen this yeat, before 3.4 there will be 3.3, but there the bug still persists. > How about the optimizer bug? It exists in 2.95 as well. Which one? You don't say anything about it in the text of this report? W. ------------------------------------------------------------------------- Wolfgang Bangerth email: bangerth@ices.utexas.edu www: http://www.ices.utexas.edu/~bangerth/
reply other threads:[~2003-04-09 22:06 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=20030409220601.10993.qmail@sources.redhat.com \ --to=bangerth@ices.utexas.edu \ --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).