Release: gcc version 3.0.4 Environment: ia64
State-Changed-From-To: open->analyzed State-Changed-Why: This was fixed in gcc 3.1 by http://gcc.gnu.org/ml/gcc-patches/2001-08/msg01072.html
From: Jakub Jelinek <jakub@redhat.com> To: Richard Hirst <rhirst@linuxcare.com> Cc: jakub@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: c/5974: gcc 3.0.4 generates bad code to reference ((packed)) struct Date: Mon, 18 Mar 2002 05:17:49 -0500 On Mon, Mar 18, 2002 at 09:32:44AM +0000, Richard Hirst wrote: > 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? Fixed 2.96-RH version is going to appear fairly soon, the rest (GNUPro 2.96 and 3.0 I have no control about). Jakub
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
State-Changed-From-To: analyzed->feedback State-Changed-Why: According to the audit trail this has been fixed long ago. Can someone with an ia64 confirm this, please?
Reminder that this bug is still in wiating. Can someone please confirm whether this problem is still present in gcc 3.3?
Since this has been in waiting almost 3 months (T-1 day) and it references a patch which fixed it in 2001, I am going to close it as fixed.