public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Pete Gonzalez <gonz@ratloop.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/10776: [3.3 regression] Large aggregate initializers cause GCC to fail
Date: Wed, 14 May 2003 14:46:00 -0000	[thread overview]
Message-ID: <20030514144600.3244.qmail@sources.redhat.com> (raw)

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

From: Pete Gonzalez <gonz@ratloop.com>
To: gcc-prs@gcc.gnu.org,gcc-bugs@gcc.gnu.org,gcc-gnats@gcc.gnu.org,
 Dara Hazeghi <dhazeghi@yahoo.com>
Cc:  
Subject: Re: c++/10776: [3.3 regression] Large aggregate initializers
  cause GCC to fail
Date: Wed, 14 May 2003 10:40:59 -0400

 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10776 
 
 
 The problem seems to be the "&data::tex::tackytexture" expression
 inside the array, i.e. if I replace all instances with "0", the
 code compiles successfully:
 
 >static const TOutdoorMapData::TTriangleItem data_triangleItems[2382] = {
 >   {
 >     0, // &data::tex::tackytexture,
 >     0,
 >     { { 87, 104, 0, -778 },
 >       { 95, 106, 21, -799 },
 >       { 89, 109, 0, -799 } }
 >   },
 
 However, this crashes:
 
 >const TBitmap *nullBmp = 0;
 >
 >static const TOutdoorMapData::TTriangleItem data_triangleItems[2382] = {
 >   {
 >     nullBmp,
 >     0,
 >     { { 87, 104, 0, -778 },
 >       { 95, 106, 21, -799 },
 >       { 89, 109, 0, -799 } }
 >   },
 
 I'll let you know if I find anything else.  Thanks for the quick response.
 
 -Pete
 


             reply	other threads:[~2003-05-14 14:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-14 14:46 Pete Gonzalez [this message]
2003-05-14 21:36 Pete Gonzalez
2003-05-14 22:06 Dara Hazeghi

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=20030514144600.3244.qmail@sources.redhat.com \
    --to=gonz@ratloop.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).