public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Richard Hirst <rhirst@linuxcare.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c/5974: gcc 3.0.4 generates bad code to reference ((packed)) struct
Date: Mon, 18 Mar 2002 01:56:00 -0000	[thread overview]
Message-ID: <20020318095600.3729.qmail@sources.redhat.com> (raw)

The following reply was made to PR c/5974; it has been noted by GNATS.

From: Richard Hirst <rhirst@linuxcare.com>
To: jakub@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: c/5974: gcc 3.0.4 generates bad code to reference ((packed)) struct
Date: Mon, 18 Mar 2002 09:32:44 +0000

 Hi,
   Are fixed versions of 2.96 and 3.0 likely to appear, or do I have to
 code round the problem until 3.1+ becomes the standard compiler?
 
 Thanks,
   Richard
 
 On Fri, Mar 15, 2002 at 02:10:20PM -0000, jakub@gcc.gnu.org wrote:
 > Synopsis: gcc 3.0.4 generates bad code to reference ((packed)) struct
 > 
 > State-Changed-From-To: open->analyzed
 > State-Changed-By: jakub
 > State-Changed-When: Fri Mar 15 06:10:20 2002
 > State-Changed-Why:
 >     This was fixed in gcc 3.1 by
 >     http://gcc.gnu.org/ml/gcc-patches/2001-08/msg01072.html
 > 
 > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5974


             reply	other threads:[~2002-03-18  9:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-18  1:56 Richard Hirst [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-16 14:32 ehrhardt
2002-03-18  2:26 Jakub Jelinek
2002-03-15  6:10 jakub
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=20020318095600.3729.qmail@sources.redhat.com \
    --to=rhirst@linuxcare.com \
    --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: 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).