public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "giovannibajo at libero dot it" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/12573] [3.4 Regression ] ICE (segfault) with Boost.Python
Date: Sat, 22 Nov 2003 13:52:00 -0000 [thread overview]
Message-ID: <20031122135223.18535.qmail@sources.redhat.com> (raw)
In-Reply-To: <20031011014942.12573.jbrandmeyer@users.sourceforge.net>
------- Additional Comments From giovannibajo at libero dot it 2003-11-22 13:52 -------
Subject: Re: [3.4 Regression ] ICE (segfault) with Boost.Python
On Saturday, November 22, 2003 6:50 AM [GMT+1=CET],
gdr at integrable-solutions dot net <gcc-bugzilla@gcc.gnu.org> wrote:
>> + if (TREE_CODE (expression) == COMPONENT_REF)
>> + return value_dependent_expression_p (TREE_OPERAND (expression, 0));
>
> Don't you want to test both arms of COMPONENT_REF?
Yup, I was misguided by the internal documentation, which (wrongly) says that
COMPONENT_REF is supposed to always have a FIELD_DECL as second operand. Of
course, it could easily be a SCOPE_REF. I'll update the patch and try to prepare
a testcase, thanks for the quick comment.
Giovanni Bajo
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12573
next prev parent reply other threads:[~2003-11-22 13:52 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-11 1:49 [Bug c++/12573] New: [ regression from 3.3.1 " jbrandmeyer at users dot sourceforge dot net
2003-10-11 1:54 ` [Bug c++/12573] " jbrandmeyer at users dot sourceforge dot net
2003-10-11 2:21 ` pinskia at gcc dot gnu dot org
2003-10-11 2:30 ` [Bug c++/12573] [3.4 Regression " pinskia at gcc dot gnu dot org
2003-10-11 2:33 ` pinskia at gcc dot gnu dot org
2003-10-11 8:10 ` pinskia at gcc dot gnu dot org
2003-10-16 19:19 ` bangerth at dealii dot org
2003-11-22 0:37 ` giovannibajo at libero dot it
2003-11-22 5:50 ` gdr at integrable-solutions dot net
2003-11-22 13:52 ` giovannibajo at libero dot it [this message]
2003-11-22 13:54 ` paolo at gcc dot gnu dot org
2003-11-25 17:41 ` giovannibajo at libero dot it
2003-12-02 12:02 ` cvs-commit at gcc dot gnu dot org
2003-12-02 12:10 ` cvs-commit at gcc dot gnu dot org
2003-12-02 12:12 ` giovannibajo at libero dot it
2003-12-15 17:00 ` cvs-commit at gcc dot gnu dot org
2003-12-31 18:12 ` pinskia at gcc dot gnu dot org
2003-12-31 18:19 ` pinskia at gcc dot gnu dot org
2004-01-01 8:35 ` pinskia at gcc dot gnu dot org
2004-01-01 18:17 ` [Bug c++/12573] [3.4 Regression] " giovannibajo at libero dot it
2004-01-05 14:12 ` pinskia at gcc dot gnu dot org
2004-01-08 4:24 ` giovannibajo at libero dot it
2004-01-08 11:52 ` cvs-commit at gcc dot gnu dot org
2004-01-08 11:58 ` cvs-commit at gcc dot gnu dot org
2004-01-08 11:58 ` giovannibajo at libero dot it
2004-01-08 11:59 ` giovannibajo at libero dot it
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=20031122135223.18535.qmail@sources.redhat.com \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).