public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "Pop Sébastian" <pop@gauvain.u-strasbg.fr> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/7788: g++-3.2 internal error: Segmentation fault Date: Sun, 29 Sep 2002 02:16:00 -0000 [thread overview] Message-ID: <20020929091602.21020.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/7788; it has been noted by GNATS. From: =?iso-8859-1?Q?Pop_S=E9bastian?= <pop@gauvain.u-strasbg.fr> To: nathan@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, jerrysiebe@mindspring.com, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Cc: nathan@codesourcery.com Subject: Re: c++/7788: g++-3.2 internal error: Segmentation fault Date: Sun, 29 Sep 2002 11:08:53 +0200 On Fri, Sep 13, 2002 at 08:39:32PM -0000, nathan@gcc.gnu.org wrote: > Synopsis: g++-3.2 internal error: Segmentation fault > > State-Changed-From-To: open->analyzed > State-Changed-By: nathan > State-Changed-When: Fri Sep 13 13:39:32 2002 > State-Changed-Why: > confirmed as a regression > > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7788 The problem comes from cp/rtti.c in unemitted_tinfo_decl_p (). Associated patch with these changes is: Date: Fri, 21 Jun 2002 12:20:51 +0100 From: Nathan Sidwell <nathan@codesourcery.com> Organization: Codesourcery LLC X-Accept-Language: en To: jason@redhat.com Cc: gcc-patches@gcc.org Subject: [C++ PATCH]: Rework typeinfo objects 2002-06-20 Nathan Sidwell <nathan@codesourcery.com> int ! tinfo_decl_p (t, data) tree t; void *data ATTRIBUTE_UNUSED; { ! return TREE_CODE (t) == VAR_DECL ! && IDENTIFIER_GLOBAL_VALUE (DECL_NAME (t)) == (t) ! && TREE_TYPE (t) == tinfo_decl_type ! && TREE_TYPE (DECL_NAME (t)); } Changed into int ! unemitted_tinfo_decl_p (t, data) tree t; void *data ATTRIBUTE_UNUSED; { ! if (/* It's a var decl */ ! TREE_CODE (t) == VAR_DECL ! /* whos name points back to itself */ ! && IDENTIFIER_GLOBAL_VALUE (DECL_NAME (t)) == t ! /* whos name's type is non-null */ ! && TREE_TYPE (DECL_NAME (t)) ! /* and whos type is a struct */ ! && TREE_CODE (TREE_TYPE (t)) == RECORD_TYPE ! /* with a first field of our pseudo type info */ ! && TREE_TYPE (TYPE_FIELDS (TREE_TYPE (t))) == ti_desc_type_node) ! return 1; ! return 0; } I rewrote the condition as : int unemitted_tinfo_decl_p (t, data) tree t; void *data ATTRIBUTE_UNUSED; { /* It's a var decl */ if (TREE_CODE (t) == VAR_DECL) { tree dnt = DECL_NAME (t); /* whos name points back to itself */ if (IDENTIFIER_GLOBAL_VALUE (dnt) == t) /* whos name's type is non-null */ if (TREE_TYPE (dnt)) { tree ttt = TREE_TYPE (t); /* and whos type is a struct */ if (TREE_CODE (ttt) == RECORD_TYPE) { tree tfttt = TYPE_FIELDS (ttt); /* with a first field of our pseudo type info */ => if (TREE_TYPE (tfttt) == ti_desc_type_node) return 1; } } } return 0; } The problem is here => since tfttt is NULL in this bug-report example. Nathan could you review this patch and the associated bug-report please? Thanks, Sebastian
next reply other threads:[~2002-09-29 9:16 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-09-29 2:16 Pop Sébastian [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-09-29 11:56 Pop Sébastian 2002-09-29 11:28 nathan 2002-09-29 10:44 nathan 2002-09-13 13:39 nathan 2002-08-31 1:06 jerrysiebe
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=20020929091602.21020.qmail@sources.redhat.com \ --to=pop@gauvain.u-strasbg.fr \ --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).