public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: neil@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
	rhirst@linuxcare.com
Subject: Re: c/5973: gcc 2.96 generates bad code to reference ((packed)) struct
Date: Tue, 19 Mar 2002 01:02:00 -0000	[thread overview]
Message-ID: <20020319090204.31011.qmail@sources.redhat.com> (raw)

Synopsis: gcc 2.96 generates bad code to reference ((packed)) struct

State-Changed-From-To: open->closed
State-Changed-By: neil
State-Changed-When: Tue Mar 19 01:02:02 2002
State-Changed-Why:
    GCC 2.96 is not an FSF release, and you've filed a PR against the FSF release 3.0.4.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5973


             reply	other threads:[~2002-03-19  9:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-19  1:02 neil [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-03-15  4:36 rhirst

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=20020319090204.31011.qmail@sources.redhat.com \
    --to=neil@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=rhirst@linuxcare.com \
    /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: link
Be 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).